Java Is So 90s
An anonymous reader writes "Some of you may recall last year's Java vs. LAMP Slashdot
flamewar. The fight has now "brewed" (couldn't resist) into the mainstream press at
BusinessWeek." From the article: "Yared says developers far and wide are creating a new generation of Internet-based applications with LAMP and related technologies rather than with Java. Can it possibly be that Java -- once the hippest of hip software -- has become a legacy technology, as old and out of style as IBM's (IBM) mainframe computers and SAP's corporate applications? Mounting evidence points to yes. Reports by Evans Data Corp., which does annual surveys of the activities of software developers, show Java use is slipping as LAMP and Microsoft's .NET technology gain traction."
Java is not obsolete...people with expertise in Java can and do get jobs in the tech sector. What is obsolete, at least from the point of getting a job, is C without any C++ classes. Perl is obsolete if it is "scripting Perl" (OO mod_perl is the only Perl that can get you a job these days); non-OO PHP is quickly becoming obsolete. .NET has plenty of job postings.
C++ job postings are still quite common; this will probably not change for a while.
Usenet and mailing lists as discussion mediums are very 1990s and obsolete; the new wave is PhpBB and related web discussion boards. PDAs are also 90s has-beens.
Email is almost always accessed with a web interface these days.
enough said. i have been a java dev for about 5 years now and i can't stand it. my testimonial should be worth something.
This article is complete hogwash. It's trying to put a spin on java like it's some kind of over-dressed scripting language for making web pages. The strongest advantage java has over all the others combined is in the 'portability'. You write the code once, and RUN IT ON ANY PLATFORM that has a byte-code interpreter for it. Is it perfectly done? -no. But writing an application on BSD and running the same class files on Windows is priceless in many circumstances. I've done enough socket programming in perl to say it's great for the platform you coding in but expect to be re-writing stuff if you move it to another platform. (Let alone the skull-fucked version of perl that ships with solaris 9) - And I *like* perl, and I also happen to like C, PHP, and assembler also. Each one has it's place where it's merits are unequalled. Each one has things that suck about it. You deal with them and move on because the next sexiest thing coming down the road is going to have it's same share of shortcomings, just like all the rest, be it .net, or mono, or AJAX or ruby or python. Try and focus on the best language for the task at hand instead of trying to make some kind of 'designer' statement to rule it out. Consider the source I guess.. another gaggle of fat-ass PHBs writing an article for a website for fat-ass PHBs..
Join the Slashcott! Feb 10 thru Feb 17!
If such an opportunity arose, I would go for it. Plus I'm excellent for such work. Since I suffer from severe impotency, I would not get the distracting erections that many younger men would get when subjected to hours of pornography viewing.
Cyric Zndovzny at your service.