In case you don't have time to partake in the programming challenge right now, at least come take a really short - single page - survey on JavaPocket.net to help us figure out which Java Programming IDE best lends itself to learning Java Spring. Thanks!
Last edited by dav0; Jun 16th, 2009 at 01:48 PM.
I went to the programming on the web reading sections at both stores.
At Barnes and Nobles, I saw one Grails book in the web programming section. It was on the shelf closest to the floor. Again, ASP.NET, C#, Rails, Python, and Ruby books dominated the scene. This was the Sunset and Vine location in Los Angeles. I asked where all the Java books were. This location didn't carry that many because people don't buy the (Java)books and publishers don't write books for them.
Why in the world would someone want to learn any of the unproductive J2EE stacks in any IDE? They are all unproductive. Only maintenance for legacy J2EE apps is relevant anymore. The world has moved on. Let the J2EE dead horse turn into gasoline/fossil fuel for future generations. Just burn it all.
Ha! Good stuff! You're writing from Los Angeles eh? Halleluja! I spent nearly a year there in 1980-81 and still have some fond memories!
On the subject of Java books in book stores, I have purchased more Java books than will fit in my house anymore! Now I purchase Spring books with equal vigor, but I can't get them fast enough from local yokel books stores, so I buy them online and/or direct from the publisher and have them delivered. I also subscribe to Safari online books, so I rarely buy actual "fossil fuel" books anymore anyway.
That said, I think you do have a point because it used to be that the Java books took up several large sections at most bookstores, whereas now you are lucky to find very many books on Java.
I guess it is a sort of phenomenon that happens in the real world. You rarely ever see a book on Cobol anymore either, but you'd be surprised how many people still make a living writing Cobol programs! Of course, there will always be a dot Net type of language around for Microsoft die-hards too, but until C# decides to make inroads onto other platforms, it will always be limited to a slowly dying platform (Windows).
Chances are, the next programming language wave is coming and will make a huge splash soon, and when it does, you will once again see the bookshelves filled with books on the new language craze. My bet is that it will be Scala, but I am only basing this on what I am hearing about the language, and not on personal experience. Regardless of whether it becomes the new killer programming language or not, I do eventually plan to buy a Scala book, so that's the kind of programming language book that belongs on my local bookstore shelf to tempt me with!
In the meantime, I wouldn't be writing any obituaries on the Java language any time soon (unless you are a comedy writer).
-dav0 (happily employed writing Java programs for over 12 years now with no end it sight).
Hee hee. Java the new Cobol is quite appropriate hahahaha. But seriously, the age of Java is over. Sun selling out.. Spring selling out.. This doesn't help Java/J2EE as a technology stack at all. If you see the history of acquisitions of technology by bigger companies, you'll see a pattern of DEATH of an acquired product. Very few people try to do new development in J2EE these days. You may be making a living doing J2ee, but in reality, you are the underwhelming minority. Heck.. the whitehouse just went with Drupal for whitehouse.gov over any Java solution (funny thing about this lack of GOOD Java CMS's. If it was so great to develop one in java, we'd see more that can kick the asses of php ones, but that hasn't happened). Laugh it off as comedy if you wish, but truthfully, Java/J2EE is a dinosaur.
I would agree that PHP apps are still quite widespread as a result of the pleathora of extremely cheap LAMP web sites on the internet. LAMP based web sites, as you undoubtedly know, owe their ubiquitous success to the larger success of open source Linux, which is the "L" in the LAMP acronym (the other letters being Apache as the Web server, MySQL as the relational database management system and PHP (as well as Perl and Python - all conveniently starting with the letter "P").
Part of the reason for this is because Java was simply never bundled very well with these LAMP distributions in the past, many of which are configured with CPanel, with an assortment of "P" based web site management applications all cobbled around the various tiers of the CPanel business layers (from web site management, to domain name reseller, to VPS manager, etc.), all of which make running an older retro web v1.0 site relatively easy.
For many people, it is apparently enough to run a simple web site and maybe throw in a few "P" based web site gadgets here and there (many of which have security holes wide enough to drive a truck through and this makes them very popular among web site crackers as well).
Many of the people who contribute to the "A" in LAMP (Apache web server) now work for SpringSource (now a division of VMWare), and of course you realize that the "M" in LAMP (MySQL) on which many of the "P" based applications are all based now belongs to Sun Microsystems (soon to become Oracle or whatever). So yes, things are being sold out (or "Cobolized"), but this also includes much of what LAMP and the "P" based languages are all based on as well.
Keep in mind that Java has only actually been open sourced for a couple of years now, and for one reason or another (politics mostly) it is only now approaching a point where it can potentially become completely integrated into anything approaching the LAMP stack in terms of being an integrated component of a larger system - hinged on the success of Java v7 most likely.
So it's really not accurate to classify Java as a dinosaur. If anything, the dinosaurs are the "P" based languages which have, up until very recently, been the only viable web language options on Linux. Meanwhile, Java and the army of JVM based languages and toolkits which accompany it (Spring, etc.) are just now finally becoming poised to replace the LAMP stack on their way to internet unbiquity for the foreseeable future. This assumes that the JVM language crowd can retain their open source qualities enough to avoid vendor lock-out - which would simply spawn a whole new open source revolution in some other form most likely.
PHP is EASY to make secure. And so is C#. And so is Python. And so is "language of choice here". Really that argument about PHP's lack of security is a null pointer exception (an error that is). Sure anyone can write insecure php, c#, java or whatever other language there is. People using PHP the wrong way does not make PHP bad. Really the arguments you have presented are simply grasping at threads. "Poised to replace lamp" HAHAHAHHa (somehow this is more comedic than my earlier arguments about java being fossil fuel). Poised to replace lamp since the 90's (or at least that's what all the hype was implying)? I remember attending a sun advertisement session at my school and the representative was saying how they changed their business model (with regards to their Java product) to open source close to 3 years ago. They were hoping to make money that way but look at SUN now. Look where Java is. There are such things as failed open source initiatives. LAMP is not. Java as open source is. The two are incomparable in their respective successes. You absolutely cannot blame packaging or the fact that LTMJ (Linux, Java, Tomcat, MySQL) doesn't spell out to a real word in English. That is plain ridiculous. You think WAMP is a package in and of itself? Microsoft would NEVER agree to package something like that. You get everything separate. And yet, WAMP is still pretty popular....
Well. Keep hoping and hanging onto the hope that Java is cured of it's "unproductive" and "overlycomplex" disease. You may find yourself being the "Last Samurai" (yea terrible movie and reference but message is clear, change or die). 12 years of Java development is difficult to overturn. Good luck sir.
Last edited by springmvcsucks; Nov 6th, 2009 at 05:58 PM.
And Java is not just SE/EE it is the micro and real time now too. Yeah, it's dead honest just trust you. I would say it is mature. It is indeed bloated because of a lack of desire to remove support for older code. It has it's problems, so do all languages out there. It is NOT a silver bullet, it is NOT the only tool. It IS a valid and valuable tool today. Maybe even more so than in the original years. Maturity can bring that. Sure lots of sites won't use it. But a lot of industries do and will.
Java is far from a dinosaur and far from dying out IMHO.
Things like what Spring is doing are part of what is helping mature and lengthen that life I think.
Maturity my ass. Why, after 3 years from their announcement of open source, has Sun failed with Java? Please explain that. I don't care about these banks who have FAILED with java. Explain why spring source has sold out on the J2EE bandwagon. You can't fool people just because you are sold invested in some outdated technology. You have heard of this: "You can't even give it away".
Maturity is just semantics. My 80 year old landlord is "mature" right. She isn't "old" at all. She just needs help fetching medication, cooking her own food, taking out the trash, and carrying anything over five pounds, just like Java projects need help being uncomplicated, unbloated, undeliverable, and unobese. This is the technology world people. Wake up. WAKE UP. Heck even the hospital I work at is switching to C#/.net. We are talking about a HOSPITAL. A an institution where information is critical to saving the lives of humans. Spring selling out is a maintainability issue now down the road. We can't afford this.
What are you even doing here? Why don't you go troll the forums over at asp.net and spew your wonderful wisdom on them?