Jave does what it needs to, and does it well. So does JEE.
There isn't a lot of "innovation" in the stack because the stack serves it's primary purpose quite well, and is used by tens (if not hundreds) of thousands of websites to deliver business functionality.
And that is, of course, the crux of the matter: functionality. Business is not interested in jumping on the latest and greatest craze just for the sake of doing so. Business wants stability. It wants predictability. It wants reliability.
Automate it and find something else to work on. At no place I've ever been has there been a shortage of work.
Only the lazy and incompetent fear automating themselves out of a job. If worst comes to worst, you'll end up maintaining all those scripts you created, fighting fires, and dealing with the "one off" situations that the scripts can't handle.
Apple sells computing appliances, not computers, and that's an important difference. The batteries in iOS devices are not user replaceable, the computing appliances are often not user-upgradeable, and "expansion" of the devices is limited.
This is all intentional.
You're supposed to buy a new appliance every 3-5 years. And if you're not on the "buy the new iThingie, Ooo, Ooo, Ooo" bandwagon, they don't give a rat's fat ass about you, because you're not continuing to make them money.
If you want upgradeable, buy a bare bones box and install Linux. Old hardware and old devices are supported beyond any sane life span.
If you want to be locked in to a repurchase cycle, buy Apple.
I'm sure government purchases are a small fraction of the total purchased by the general public.
There are many government agencies around the world which haven't approved Apple, Microsoft, Blackberry, or other particular products for their purchase lists. Government purchases are just a nice feather in the cap for most companies. They really could care less, other than some people amongst the general public who think government purchase approval is some sort of "security approval" for a device.
They want the mass market. And that has not been cut off by China by any means.
I agree that it is up to the greybeards to teach the young 'uns, but a large part of that is corporate culture.
When I was fresh out of school, I worked at a place where cameraderie was paramount. We went for lunch. We went for coffee. We went for smokes.
And we talked about issues and the problems they'd encountered over the years, and how they'd approached them and solved them.
The last few jobs I had, if you spent any time on such "idle chit-chat", the management came down on you hard for "not doing your job." It's pretty damned hard to educate the younguns if there is no opportunity to talk with them.
But having a way to cheaply power and connect these devices to the Internet has kept this from taking off.
Of course it has nothing to do with cost, uselessness, or invasion of privacy. People are just waiting for this technology in Bumfuck Nowhere like they've been waiting for "home automation" all these years.
As an IT professional, you will have access to data that regular employees don't. You keep your mouth shut and you don't snoop. Period. You only look at as much as you have to diagnose and fix problems; the details are irrelevant.
It's called "being professional."
Think of it as the equivalent of lawyer-client or doctor-patient relationships.
Well, while he's busy sitting on his "proprietary" meta compiler, here's a tool that uses XML to define a business application model and which can be used to produce any text-based language code you might desire. I'm focusing on building Java applications with it.
Unlike some people, I have no where near enough ego to "sit on it" until I "retire." I'd rather people gain whatever use they can as early as they can. Sure it's not perfect and it's not what *everyone* needs, but it works for what it does so far: six database products, a Java ORM, XML parsers, XML messaging for RPC-type behaviour, and I'm working on a prototype/demo Swing GUI right now.
Until this nonsense about keyword TLDs, TLDs were just identifiers, not property as ICANN noted. But this custom TLD nonsense is going to throw a wrench into that.
I could see seizing the domain registrars, but as they say, how do you seize an identifier? That's like saying I "own" the variable "x", and that all graphics programmers now need to pay me to lease use of that variable name.
Last but not least, you might want to dig deep into the bowels of Erlangs runtime (which I've had to do for thornier debugs.) Lists upon lists upon lists -- with syntactic sugar at the language level so you can *pretend* you're not dealing with a list.
And tail recursion is an extremely restrictive programming model. If you break out of the tail recursion model with Erlang (resulting in more readable code and sometimes unavoidable if you want a specific behaviour from your code), be prepared to run out of stack space.
Not at all. At this point the Israelis have killed well over 1000 civilians (roughly 80% of the total dead.)
Even if they have hundreds of launchers, Israel has bombed well over 2000 sites. It does take some time to move a rocket launcher, so I'd have thought most of them to be destroyed by now if Israel were truly bombing launch sites.
Add in the fact that no independent observers of any kind have verified the presence of Hamas munitions or launches at any of the sites Israel has attacked, and it stinks as bad as the US claims of WMD against Iraq. (We have tubes! Aluminum tubes!)
I spent over two years working every day with Erlang on a project, and I still don't consider myself to be anywhere near an "expert" at the language. It's just too weird and special case for a lot of the functionality I was trying to code, so while certain tasks were easier than they would have been in Java or another procedural-object language, others were damned near impossible and took obscene amounts of time to get working at all -- never mind working efficiently.
Personally I'd avoid it like the plague unless you have some special case need for it's features. Even with regards to concurrency, it's not really any better than any other language's concurrency features. They aren't really baked into the language as the summary suggests, but provided by frameworks in the API libraries, much as they are by other languages.
The main difference with Erlang concurrency is that the concurrent models are the "normal" way to program Erlang, so you're likely to find a lot of good examples of how to do it. I've found the documentation for other language's concurrency features to be somewhat limited in comparison, and less "real world" in their examples.
The main thing that I found neat about the Erlang framework was the ability to specify auto-restarts of failed threads. It takes all of about 4 lines of configuration to get a thread to be persistent/self-starting. That's the densest code I've ever seen for achieving such a task.
The big downside to Erlang is that it's almost as bad as LISP -- everything is a list. Even "structures" are just lists of objects with tags that identify the list indices for accessing the members. Be prepared for a nightmare of tail recursion if you get into this field of programming.
That said, it can be a fun and entertaining language to work with. For the things it is good at, it can be a joy to use. Much as with any language.
I find it interesting that pretty much all posts in support of the Gazans have been moderated down, yet there seem to be an awful lot of such posts. There's nothing like censorship by the mods to ensure that all viewpoints aren't heard equally. So with the expectation of being moderated down...
Israel likes to claim they're targetting Hamas installations. Yet if that's the case, each of those installations they've targetted has only launched an average of less than two rockets at Israel, when you consider the number of rockets Israel claims have been launched vs. the number of sites they've targetted.
It seems to me rather highly unlikely that Hamas has actually got *that* many rocket launchers, considering they have to be smuggled in.
Another common thread is the "terror tunnels." Don't forget that Gaza is isolated and has to smuggle in supplies. There is no way to tell whether a tunnel was being used for smuggling goods in or attackers out, but given that there have only been *two* reports of Hamas sending attackers through the tunnels, I think it's safe to say that those tunnels were being used primarily to smuggle in goods.
Well over a 1000 Gazans have been killed, the vast majority civilians. In the meantime, only 3 Israeli civilians have been killed. As to the soldiers on both sides, I *expect* them to die -- they're in battle. I've no sympathy for dead soldiers on either side.
I don't see how anyone can take a "moderate" stance on the issue. Israel invaded Palestine. Israel destroys Gazan homes to make room for settlements in violation of the Geneva conventions. Israel targets civilian infrastructure. Israel has tanks, planes, missiles, and gun emplacements; the Gazans have some pretty-much-useless rocket launchers that don't do any damage to Israeli infrastructure.
The Gazans are walled in, have no where to escape to, and are, for the most part, just civilians trying to survive. Bleat as they will about "self defence", I don't buy the Israeli arguments for this violent and genocidal assault on the civilians of Gaza. Not one bit.
You've got to be kidding. My Palm III ate batteries like a fiend. I was lucky if they lasted a week, and I hardly used the thing. I'd guess I got about 6-7 hours of functionality out of a set of batteries. And I'm not talking rechargeables, but good quality alkalines.
Slashdot Mirror
Jave does what it needs to, and does it well. So does JEE.
There isn't a lot of "innovation" in the stack because the stack serves it's primary purpose quite well, and is used by tens (if not hundreds) of thousands of websites to deliver business functionality.
And that is, of course, the crux of the matter: functionality. Business is not interested in jumping on the latest and greatest craze just for the sake of doing so. Business wants stability. It wants predictability. It wants reliability.
Not "innovation" for the sake of being different.
Automate it and find something else to work on. At no place I've ever been has there been a shortage of work.
Only the lazy and incompetent fear automating themselves out of a job. If worst comes to worst, you'll end up maintaining all those scripts you created, fighting fires, and dealing with the "one off" situations that the scripts can't handle.
Apple sells computing appliances, not computers, and that's an important difference. The batteries in iOS devices are not user replaceable, the computing appliances are often not user-upgradeable, and "expansion" of the devices is limited.
This is all intentional.
You're supposed to buy a new appliance every 3-5 years. And if you're not on the "buy the new iThingie, Ooo, Ooo, Ooo" bandwagon, they don't give a rat's fat ass about you, because you're not continuing to make them money.
If you want upgradeable, buy a bare bones box and install Linux. Old hardware and old devices are supported beyond any sane life span.
If you want to be locked in to a repurchase cycle, buy Apple.
My seven year old computer which has been unsupported by the vendor for three years is now unsupported by third-party products.
I'm going to go cry into my iThingie.
*LMAO*
I'm sure government purchases are a small fraction of the total purchased by the general public.
There are many government agencies around the world which haven't approved Apple, Microsoft, Blackberry, or other particular products for their purchase lists. Government purchases are just a nice feather in the cap for most companies. They really could care less, other than some people amongst the general public who think government purchase approval is some sort of "security approval" for a device.
They want the mass market. And that has not been cut off by China by any means.
I agree that it is up to the greybeards to teach the young 'uns, but a large part of that is corporate culture.
When I was fresh out of school, I worked at a place where cameraderie was paramount. We went for lunch. We went for coffee. We went for smokes.
And we talked about issues and the problems they'd encountered over the years, and how they'd approached them and solved them.
The last few jobs I had, if you spent any time on such "idle chit-chat", the management came down on you hard for "not doing your job." It's pretty damned hard to educate the younguns if there is no opportunity to talk with them.
You gotta give the guy credit. He's taking every possible spin he can to get his guilty client off.
Of course it has nothing to do with cost, uselessness, or invasion of privacy. People are just waiting for this technology in Bumfuck Nowhere like they've been waiting for "home automation" all these years.
*LMAO*
Ooooh. Soylent News.
With less than a dozen posts per thread.
Yeah, that's just a raving success. Clearly the slashdot community has rebelled in droves and gone over to this "fork."
*ROTFLMAO*
As an IT professional, you will have access to data that regular employees don't. You keep your mouth shut and you don't snoop. Period. You only look at as much as you have to diagnose and fix problems; the details are irrelevant.
It's called "being professional."
Think of it as the equivalent of lawyer-client or doctor-patient relationships.
Were it "Netflix for games" you'd pay a flat monthly fee and be able to play whatever game(s) you want.
Well, while he's busy sitting on his "proprietary" meta compiler, here's a tool that uses XML to define a business application model and which can be used to produce any text-based language code you might desire. I'm focusing on building Java applications with it.
Unlike some people, I have no where near enough ego to "sit on it" until I "retire." I'd rather people gain whatever use they can as early as they can. Sure it's not perfect and it's not what *everyone* needs, but it works for what it does so far: six database products, a Java ORM, XML parsers, XML messaging for RPC-type behaviour, and I'm working on a prototype/demo Swing GUI right now.
So download http://msscodefactory.sourceforge.net, play, have fun, try it out. No charge, no strings, no bullshit.
But most of all, no ego. I know I'm not "brilliant" or "innovative", just stubborn and persistent.
Performance is comparable if we compare against Intel's lowest end CPU?
Until this nonsense about keyword TLDs, TLDs were just identifiers, not property as ICANN noted. But this custom TLD nonsense is going to throw a wrench into that.
I could see seizing the domain registrars, but as they say, how do you seize an identifier? That's like saying I "own" the variable "x", and that all graphics programmers now need to pay me to lease use of that variable name.
Last but not least, you might want to dig deep into the bowels of Erlangs runtime (which I've had to do for thornier debugs.) Lists upon lists upon lists -- with syntactic sugar at the language level so you can *pretend* you're not dealing with a list.
And tail recursion is an extremely restrictive programming model. If you break out of the tail recursion model with Erlang (resulting in more readable code and sometimes unavoidable if you want a specific behaviour from your code), be prepared to run out of stack space.
And what is a tuple other than a list of values?
Go back to university and study the basics.
Oh, yes, it would make perfect sense to smuggle rockets into Gaza through Israel. Grasping at straws much?
Not at all. At this point the Israelis have killed well over 1000 civilians (roughly 80% of the total dead.)
Even if they have hundreds of launchers, Israel has bombed well over 2000 sites. It does take some time to move a rocket launcher, so I'd have thought most of them to be destroyed by now if Israel were truly bombing launch sites.
Add in the fact that no independent observers of any kind have verified the presence of Hamas munitions or launches at any of the sites Israel has attacked, and it stinks as bad as the US claims of WMD against Iraq. (We have tubes! Aluminum tubes!)
If JIT compilation is your definition of "does not run in a virtual machine", then modern Java doesn't run in a VM, either.
I spent over two years working every day with Erlang on a project, and I still don't consider myself to be anywhere near an "expert" at the language. It's just too weird and special case for a lot of the functionality I was trying to code, so while certain tasks were easier than they would have been in Java or another procedural-object language, others were damned near impossible and took obscene amounts of time to get working at all -- never mind working efficiently.
Personally I'd avoid it like the plague unless you have some special case need for it's features. Even with regards to concurrency, it's not really any better than any other language's concurrency features. They aren't really baked into the language as the summary suggests, but provided by frameworks in the API libraries, much as they are by other languages.
The main difference with Erlang concurrency is that the concurrent models are the "normal" way to program Erlang, so you're likely to find a lot of good examples of how to do it. I've found the documentation for other language's concurrency features to be somewhat limited in comparison, and less "real world" in their examples.
The main thing that I found neat about the Erlang framework was the ability to specify auto-restarts of failed threads. It takes all of about 4 lines of configuration to get a thread to be persistent/self-starting. That's the densest code I've ever seen for achieving such a task.
The big downside to Erlang is that it's almost as bad as LISP -- everything is a list. Even "structures" are just lists of objects with tags that identify the list indices for accessing the members. Be prepared for a nightmare of tail recursion if you get into this field of programming.
That said, it can be a fun and entertaining language to work with. For the things it is good at, it can be a joy to use. Much as with any language.
Abusing the moderating system to *hide* viewpoints IS an issue, however.
I find it interesting that pretty much all posts in support of the Gazans have been moderated down, yet there seem to be an awful lot of such posts. There's nothing like censorship by the mods to ensure that all viewpoints aren't heard equally. So with the expectation of being moderated down...
Israel likes to claim they're targetting Hamas installations. Yet if that's the case, each of those installations they've targetted has only launched an average of less than two rockets at Israel, when you consider the number of rockets Israel claims have been launched vs. the number of sites they've targetted.
It seems to me rather highly unlikely that Hamas has actually got *that* many rocket launchers, considering they have to be smuggled in.
Another common thread is the "terror tunnels." Don't forget that Gaza is isolated and has to smuggle in supplies. There is no way to tell whether a tunnel was being used for smuggling goods in or attackers out, but given that there have only been *two* reports of Hamas sending attackers through the tunnels, I think it's safe to say that those tunnels were being used primarily to smuggle in goods.
Well over a 1000 Gazans have been killed, the vast majority civilians. In the meantime, only 3 Israeli civilians have been killed. As to the soldiers on both sides, I *expect* them to die -- they're in battle. I've no sympathy for dead soldiers on either side.
I don't see how anyone can take a "moderate" stance on the issue. Israel invaded Palestine. Israel destroys Gazan homes to make room for settlements in violation of the Geneva conventions. Israel targets civilian infrastructure. Israel has tanks, planes, missiles, and gun emplacements; the Gazans have some pretty-much-useless rocket launchers that don't do any damage to Israeli infrastructure.
The Gazans are walled in, have no where to escape to, and are, for the most part, just civilians trying to survive. Bleat as they will about "self defence", I don't buy the Israeli arguments for this violent and genocidal assault on the civilians of Gaza. Not one bit.
I would call the Israelis "animals" for what they're doing to the Gazans, except that I know of no species so cruel and vicious.
You've got to be kidding. My Palm III ate batteries like a fiend. I was lucky if they lasted a week, and I hardly used the thing. I'd guess I got about 6-7 hours of functionality out of a set of batteries. And I'm not talking rechargeables, but good quality alkalines.