Not true. Eclipse itself is a development tool platform, it just happens that Java is the first and most widely know language. There's a C/C++ toolkit now, though, see the CDT. There's also an effort to develop a COBOL IDE!
They need to launch 'm' and 's' into deep space permanently. For good measure, follow them up with 'f' and 't'. Hmm. That leaves us with "icroot". How odd.
Sun has been burned once when they introduced the assert keyword and broke thousands of programs that use the JUnit testing framework. The bustage occured because JUnit already used the keyword as an identifier, for the assert() methods. A token can't be an identifier, so everyone's tests broke with 1.4 I applaud Sun from learning from that fiasco and avoiding a repeat.
I guess you didn't RTFA. Introducing a new keyword breaks programs that happen to use that as an identifier. They broke JUnit when they introduced the assert keyword, and having been burned once, learned something.
Best quote on why Worse is Better and other things that plague Open Source programmers, "It would be pretty easy to write a better word processor than Microsoft Word, for example, but Microsoft, within the castle of their operating system monopoly, probably wouldn't even notice if you did."
Protocols are pluggable. It's easy to write a component that implements nsIProtocolHandler and define any URL format you want. So yeh, torrent://hostname/filename would work fine, and the torrent protocol handler would be written to do the magic right thing with hostname and filename. Isn't Mozilla c00l?
It's open source, for pity's sake. Get your lazy butt in gear and write it yourself, it's really not that hard. That is, if you know the first thing about writing code and aren't just a selfish immature punk who expects freebie handouts. Scratch your own damn itch.
Re:Not the longest running Internet cartoon.
on
Easter Humor
·
· Score: 1
Well then. Here we have a senior officer and founder of a dot-com that makes software to graphically analyze databases telling us how in the future information visualization will be the next hot thing. When google news does this, there is much wailing and gnashing of teeth on the net. Slashdot, Press Releases for Nerds?
I like the setup you have in mind now, but instead of remote desktops, consider buying high-end laptops and building a wireless network (they're going to have to re-jigger the network anyway, why spend money on copper?). You can move from your cubes to the work areas without missing a beat or losing the state of your desktop.
That's the optimistic answer. And now for something completely different.
Just shoot yourself and put yourself out of your misery now.
Or at least let them know that domain-component directory hierarchies are stupid++. And don't stop with LDAP, go with X.500 as your core directory service system and hang an LDAP front end on it for clients that need it. It's a damn shame MSFT embraced and extended directory services (along with Kerberos), having had no interest or input in to naming schema until it was time to extend their monopoly. Never mind years of work that was already in place, obviously MSFT ActiveDirectory was so important and ground-breaking it had to have it's own namespace.
NUMA == Non-Uniform Memory Access. From the NUMA FAQ: Non-Uniform Memory Access means that it will take longer to access some regions of memory than others. This is due to the fact that some regions of memory are on physically different busses from other regions.
I dunno, but I'll bet Malcom Gladwell's book, The Tipping Point, might have some insights. "a book that presents a new way of understanding why change so often happens as quickly and as unexpectedly as it does."
Excellent point. Hardware vendors have very slim margins because it is all largely commodity stuff that costs very little to produce and people know it. Software vendors can't keep pushing upgrades on new features when all the old features are, as they say, "mature". Together, however, if they can work out a way to obsolete what we have now, both the hardware and software folks see an opportunity for renewed growth and revenue.
Can't sell people your latest hyper-color O/S because they can install a free one that works fine on common hardware? Get in bed with the PC makers and build new systems that don't support old technology, lock up the specs with patents, NDAs, and huge licensing fees, and tie the O/S into the new hardware with DRM and the 21st-century equivalent of dongles, and suddenly the PC makers and the O/S vendors are rolling in the money again.
It appears you are hung up on the issue of having a degree or not. Don't feel bad, most folks who didn't get the paper have that same hang up. Anyway, if that's the only point of discussion you have, I'm happy to overlook the issue. I'm glad you fully agree with everything else I have to say.
What are your proposed solutions for ensuring that business managers are held to a decent level of responsibility if they either refuse to hire qualified experts, or overrule their professionals' knowledge and require them to abandon good software development practices and defer to marketing- or business-driven processes?
Slashdot Mirror
''Unfortunatly its (sic) for java development''.
Not true. Eclipse itself is a development tool platform, it just happens that Java is the first and most widely know language. There's a C/C++ toolkit now, though, see the CDT. There's also an effort to develop a COBOL IDE!
They need to launch 'm' and 's' into deep space permanently. For good measure, follow them up with 'f' and 't'. Hmm. That leaves us with "icroot". How odd.
Sun has been burned once when they introduced the assert keyword and broke thousands of programs that use the JUnit testing framework. The bustage occured because JUnit already used the keyword as an identifier, for the assert() methods. A token can't be an identifier, so everyone's tests broke with 1.4 I applaud Sun from learning from that fiasco and avoiding a repeat.
I guess you didn't RTFA. Introducing a new keyword breaks programs that happen to use that as an identifier. They broke JUnit when they introduced the assert keyword, and having been burned once, learned something.
Impossible, and it's been discussed over and over again in the various newsgroups whenever this week's "Shuttle To The Moon" thread starts up.
Best quote on why Worse is Better and other things that plague Open Source programmers, "It would be pretty easy to write a better word processor than Microsoft Word, for example, but Microsoft, within the castle of their operating system monopoly, probably wouldn't even notice if you did."
Protocols are pluggable. It's easy to write a component that implements nsIProtocolHandler and define any URL format you want. So yeh, torrent://hostname/filename would work fine, and the torrent protocol handler would be written to do the magic right thing with hostname and filename. Isn't Mozilla c00l?
It's open source, for pity's sake. Get your lazy butt in gear and write it yourself, it's really not that hard. That is, if you know the first thing about writing code and aren't just a selfish immature punk who expects freebie handouts. Scratch your own damn itch.
Ooops. My bad.
Well then. Here we have a senior officer and founder of a dot-com that makes software to graphically analyze databases telling us how in the future information visualization will be the next hot thing. When google news does this, there is much wailing and gnashing of teeth on the net. Slashdot, Press Releases for Nerds?
We've found the best way to get the team working as a well-oiled machine is to take a field trip to get know our dear friend Fred
I like the setup you have in mind now, but instead of remote desktops, consider buying high-end laptops and building a wireless network (they're going to have to re-jigger the network anyway, why spend money on copper?). You can move from your cubes to the work areas without missing a beat or losing the state of your desktop.
That's the optimistic answer. And now for something completely different.
Just shoot yourself and put yourself out of your misery now.
embiggens even the smallest screen.
"For those you who think it burns and/or requires oxygen, your wrong."
My wrong what? Oh you mean you're wrong. Well what's that O3 in the equation? Mud?
The whole paper can be essentially summed up so: "The language of the future will be pure LISP".
AKA Patch Pumpkin. Who has the pumpkin?
Please tell me what bank you are working at so I can be sure I never put my money in an account there.
Or at least let them know that domain-component directory hierarchies are stupid++. And don't stop with LDAP, go with X.500 as your core directory service system and hang an LDAP front end on it for clients that need it. It's a damn shame MSFT embraced and extended directory services (along with Kerberos), having had no interest or input in to naming schema until it was time to extend their monopoly. Never mind years of work that was already in place, obviously MSFT ActiveDirectory was so important and ground-breaking it had to have it's own namespace.
... because no one will ever need more than 64 bytes.
NUMA == Non-Uniform Memory Access. From the NUMA FAQ: Non-Uniform Memory Access means that it will take longer to access some regions of memory than others. This is due to the fact that some regions of memory are on physically different busses from other regions.
One tiny piece of Neodymium, Iron, and Boron alloy. Presto! No more computer problems!
I dunno, but I'll bet Malcom Gladwell's book, The Tipping Point, might have some insights. "a book that presents a new way of understanding why change so often happens as quickly and as unexpectedly as it does."
Excellent point. Hardware vendors have very slim margins because it is all largely commodity stuff that costs very little to produce and people know it. Software vendors can't keep pushing upgrades on new features when all the old features are, as they say, "mature". Together, however, if they can work out a way to obsolete what we have now, both the hardware and software folks see an opportunity for renewed growth and revenue.
Can't sell people your latest hyper-color O/S because they can install a free one that works fine on common hardware? Get in bed with the PC makers and build new systems that don't support old technology, lock up the specs with patents, NDAs, and huge licensing fees, and tie the O/S into the new hardware with DRM and the 21st-century equivalent of dongles, and suddenly the PC makers and the O/S vendors are rolling in the money again.
80%+ of the users/developers are on Wintel
Be careful lumping users and developers together so sloppily. It seems the latter at least have other plans, Linux developers are coming from Windows in large numbers. There are many things to love about Java programming on Linux.
It appears you are hung up on the issue of having a degree or not. Don't feel bad, most folks who didn't get the paper have that same hang up. Anyway, if that's the only point of discussion you have, I'm happy to overlook the issue. I'm glad you fully agree with everything else I have to say.
What are your proposed solutions for ensuring that business managers are held to a decent level of responsibility if they either refuse to hire qualified experts, or overrule their professionals' knowledge and require them to abandon good software development practices and defer to marketing- or business-driven processes?