The catch is that it requires so much damn memory to run that you have to shut down *every* application on the phone, and free up as much memory as possible.
As far as I can remember, that was pretty much what you had to do with all those old MS-DOS games as well. And around and around in circles we go...;-)
The little "RC" NASA sent to explore the surface of Mars had a nasty bug in its threading system (priority inversion problem in critical code section) that caused total system resets every 20 minutes or so.
The only point you have is the middle tier, and with mono [go-mono.com] and dotGNU [gnu.org], becoming more complete, this point crumbles away also.
pffft...
I need to build real solutions today, and I will not put my hopes on another "always-five-steps-behind" WINE-like project such as Mono or dotGNU. These two will never be able to compete.
Microsoft owns the library API's, plain and simple. And they are defining these by themselves, not through ECMA or ISO.
In short, you choose J2EE in order to have a choice of what software you want to use within your business and how much you are willing to pay for it, what hardware (Intel, Sun, IBM) and operating systems (Linux, Windows, Solaris, AIX, OS/400) requirements you have, and what requirements you have on the performance (single Intel box to 64 CPU Sun box to IBM mainframe) and scalability of your application.
You make J2EE match your requirements rather than force yourself to match.NET requirements.
Personally I'd rather see a good book on how to effectively set up a J2EE development environment using open source tools such as JBoss, Tomcat, Ant, XDoclet etc
You can find JBoss related documentation here, both for free and for pay docs.
Hmm, a lot of people seem to miss the fact that a) there's no certification required -- if you're good, you have your existing client base, they love you then by all means keep on doing what you are doing b) it is independent consultants who requested a certification program in the first place -- there's a lot of people out there that want to get certified in order to gain new customers, and certification is one way to enhance your skills (remember, the 4 day advanced training is included in the certification price).
If you don't like the current program, don't buy it. It's your choice.
Agreed. This article has nothing to do with Java -- it should not be presented as a Java article on Slashdot. Microsoft wants to confuse developers to think they are programming Java -- that has been their approach all along -- and I find it sad that Slashdot editors decide to help Microsoft in achieving this.
WirelessWeek: "Until recently, it seemed as if Verizon Wireless had turned up its nose at Java in favor of BREW. But the carrier has changed its attitude and recently confirmed it plans to offer Java-based applications, which it expects to hit the market in early 2003.
Ironically, the word comes as Verizon started giving its customers a sip of BREW, Qualcomm's binary runtime environment for wireless. The company began selling BREW applications to its 2G customers in San Diego in the first quarter as part of the first phase of a nationwide BREW deployment."
well you do have a point, I would have chosen Postgres for the database as well. But supposedly the latest mySQL also has those spanky transactions implemented.
JBoss implements the whole J2EE platform (including Enterprise JavaBeans, Messaging, Connector Architecture, Management Extensions, etc etc). Tomcat only implements the web layer (servlet & JSPs). JBoss can embed Tomcat as its web tier implementation, although I think using Jetty would have been more reliable and better performing choice as a servlet/JSP container.
The JBoss team can afford to get the certification (and have sponsors who were willing to pay for this, and told SUN about it). The problem is that to get certified you need to agree to Sun legal documents that disallows the distribution of source code for J2EE certified products. Hence no Open Source J2EE implementation can be certified. This is the reason Lutris for example chose to close the source for their J2EE implementation. For them it was more important to get certified than to support Open Source development. For the JBoss team the opposite is the case. We will not close the source base just so that we can get a "J2EE Certified" sticker for the product.
Another case in point, take a non-technical Mom. Explain Classpaths, src vrs class, and java vs javac to her to the point where she can understand it. Now repeat with VB. The knowledge required is just much less
Not sure why a non-technical mom would need to understand any of these... but let's play anyway..
Classpath vs DLL versions in VB
src vs executable vs form definition files in VB
compiler vs runtime in VB
I really fail to see the difference... these are basic elements in any development environment.... even in VB
the point is that if you are a new developer or program manager, working on a new project, and you see that the JDK tools already have an XML parser and a logging library, you're not going to even bother to look for alternatives.
And why should you, if the supplied tools work well enough for your needs? If they don't work, you'll find an alternative implementation.
its take developers of considerable experience, and influence over their manager / respect from their manager, to introduce tools to a development environment that on the surface seem redundant to the tools already at hand
Hmm, if something doesn't work right, and your managers won't let you replace it with something that does work......
I don't understand the point of view (that seems to be pretty common in Apache community) that there shouldn't be alternative options and that everything Apache does, and manages to create a reasonably active community of developers/users for, should be adopted as a de facto standard. This is similar to the attitude of people who argue that there should be, for example, only one open source J2EE implementation because having more "is a waste of resources". What does the Apache group have against having alternatives?
What you will discover in this process is that Global Warming is, in fact, very real.
yes, the average temperature has been increasing in the last 50 years, that much is true.
Frighteningly real.
Why is it frightening? You have no clue what the effects of this increase in temperature will be.
And human beings are the cause.
And this is the part where I'm inclined to dismiss you as a ranting troll. You have no evidence of this whatsoever. Humans might have a part in this play, or they may not. Their part may be significant or mostly insignifacnt. There is no solid data to show either way.
This is what pisses me off in the global warming discussion. You take one data (average increase in temperature) and use that to 'prove' that you know what is causing it or what the long term effects will be. That is just bullshit. In that sense you really aren't that much different from the creationist zealots.
I live in Finland. I remember 10-15 years ago I could go out in February and stand in knee deep snow. Today when I look out the window I can barely see any snow at all. This has been occuring alot in the last 5-10 years. The zealots scream and rant about the greenhouse effects. It has nothing to do with that or the global warming. Scientific minds can understand that weather patterns change and conditions vary (like in this case where the Gulf current hits the Norwegian coast).
It's also good to keep things in perspective and remember that we're currently living in a very very cold period in earth's history. We're still recovering from a series of ice ages that have plagued the earth for the past few hundred thousand years. In fact, we don't even know if that period is over yet.
Slashdot Mirror
As far as I can remember, that was pretty much what you had to do with all those old MS-DOS games as well. And around and around in circles we go... ;-)
You can read about it from James Gosling's home page (also has info on Arianne 5).
Luckily the engineers were able to upload a patch to Mars. That's remote debugging/patching for you :-)
pffft...
I need to build real solutions today, and I will not put my hopes on another "always-five-steps-behind" WINE-like project such as Mono or dotGNU. These two will never be able to compete.
Microsoft owns the library API's, plain and simple. And they are defining these by themselves, not through ECMA or ISO.
In short, you choose J2EE in order to have a choice of what software you want to use within your business and how much you are willing to pay for it, what hardware (Intel, Sun, IBM) and operating systems (Linux, Windows, Solaris, AIX, OS/400) requirements you have, and what requirements you have on the performance (single Intel box to 64 CPU Sun box to IBM mainframe) and scalability of your application.
You make J2EE match your requirements rather than force yourself to match .NET requirements.
You can find JBoss related documentation here, both for free and for pay docs.
If you don't like the current program, don't buy it. It's your choice.
-- Juha
JBoss is certainly not based on Tomcat. We allow any servlet container to be plugged in to the server. Currently we support Jetty and Tomcat. -- Juha
I don't care if they bullshit their own developer community. But I think they should stop there.
Agreed. This article has nothing to do with Java -- it should not be presented as a Java article on Slashdot. Microsoft wants to confuse developers to think they are programming Java -- that has been their approach all along -- and I find it sad that Slashdot editors decide to help Microsoft in achieving this.
They maybe able to speell though.
WirelessWeek: "Until recently, it seemed as if Verizon Wireless had turned up its nose at Java in favor of BREW. But the carrier has changed its attitude and recently confirmed it plans to offer Java-based applications, which it expects to hit the market in early 2003.
Ironically, the word comes as Verizon started giving its customers a sip of BREW, Qualcomm's binary runtime environment for wireless. The company began selling BREW applications to its 2G customers in San Diego in the first quarter as part of the first phase of a nationwide BREW deployment."
Read the rest here:
Verizon's Change of Heart
no clue about mySQL "compliance" wrt sql though
JBoss implements the whole J2EE platform (including Enterprise JavaBeans, Messaging, Connector Architecture, Management Extensions, etc etc). Tomcat only implements the web layer (servlet & JSPs). JBoss can embed Tomcat as its web tier implementation, although I think using Jetty would have been more reliable and better performing choice as a servlet/JSP container.
Perhaps because they want a reliable system. No need to reinvent the wheel here, the J2EE platform is available as Open Source.
'nuff said.
start with Neverwhere, its nice and dark
if you like it, read the "American Gods" which was excellent (and quite a bit longer)
I have already patented that idea.
So how much "open source" hardware is out there? I can't think of any.
The JBoss team can afford to get the certification (and have sponsors who were willing to pay for this, and told SUN about it). The problem is that to get certified you need to agree to Sun legal documents that disallows the distribution of source code for J2EE certified products. Hence no Open Source J2EE implementation can be certified. This is the reason Lutris for example chose to close the source for their J2EE implementation. For them it was more important to get certified than to support Open Source development. For the JBoss team the opposite is the case. We will not close the source base just so that we can get a "J2EE Certified" sticker for the product.
Not sure why a non-technical mom would need to understand any of these... but let's play anyway..
Classpath vs DLL versions in VB src vs executable vs form definition files in VB compiler vs runtime in VB
I really fail to see the difference... these are basic elements in any development environment.... even in VB
META-INF/manifest.mf
Funny, I'm a Java developer and I don't feel I'm suffering. I'm competent enough to pick the tools I need by myself.
And why should you, if the supplied tools work well enough for your needs? If they don't work, you'll find an alternative implementation.
its take developers of considerable experience, and influence over their manager / respect from their manager, to introduce tools to a development environment that on the surface seem redundant to the tools already at hand
Hmm, if something doesn't work right, and your managers won't let you replace it with something that does work... ...
I don't understand the point of view (that seems to be pretty common in Apache community) that there shouldn't be alternative options and that everything Apache does, and manages to create a reasonably active community of developers/users for, should be adopted as a de facto standard. This is similar to the attitude of people who argue that there should be, for example, only one open source J2EE implementation because having more "is a waste of resources". What does the Apache group have against having alternatives?
No.
yes, the average temperature has been increasing in the last 50 years, that much is true.
Frighteningly real.
Why is it frightening? You have no clue what the effects of this increase in temperature will be.
And human beings are the cause.
And this is the part where I'm inclined to dismiss you as a ranting troll. You have no evidence of this whatsoever. Humans might have a part in this play, or they may not. Their part may be significant or mostly insignifacnt. There is no solid data to show either way.
This is what pisses me off in the global warming discussion. You take one data (average increase in temperature) and use that to 'prove' that you know what is causing it or what the long term effects will be. That is just bullshit. In that sense you really aren't that much different from the creationist zealots.
I live in Finland. I remember 10-15 years ago I could go out in February and stand in knee deep snow. Today when I look out the window I can barely see any snow at all. This has been occuring alot in the last 5-10 years. The zealots scream and rant about the greenhouse effects. It has nothing to do with that or the global warming. Scientific minds can understand that weather patterns change and conditions vary (like in this case where the Gulf current hits the Norwegian coast).
It's also good to keep things in perspective and remember that we're currently living in a very very cold period in earth's history. We're still recovering from a series of ice ages that have plagued the earth for the past few hundred thousand years. In fact, we don't even know if that period is over yet.