Sun Microsystems is expected to announce at JavaOne the release of an update to its JXTA peer-to-peer protocol and framework for collaboration. Elsewhere, Sun Microsystems will spend tens of millions of dollars to emblazon all manner of computing products with a new Java logo, the company plans to unveil next week at its JavaOne conference.
I can’t wait tos ee waht tehy’ve come up with, I was impressed by the features planned for Java 1.5, it seems a lot ebtter than its clone C# which tries to lock you in to Windows.
Yes, tehre is Mono, but that is not endorsed by MS n anyway and for all we know MS can make significant changes and brea compatibility, but I expect they will want Mono to be very mature before they do that.
Go SUN!
Sun is scrambling to compete with .NET and Web Services, but they’re too late. Nobody is going to miss Sun.
RIP Sun.
I am sorry to be negative, but if these are the 2 headline news stories for JavaOne, then all of this is a real snoozer.
1. I don’t know of anyone who uses JXTA. An update to a technology that virtually nobody uses is hardly news. Maybe I am wrong on this, but I doubt it.
2. How much you wanna bet this (probably ugly) logo is much the same as Intel/AMD case badges? Nobody really notices them. People really don’t care if their cash register has “Java Inside” or some mantra like that.
What should be current announcements are news about drastic increases in performance, and *real* support of more platforms. Of course, this will never happen. It’s much more easy for them to parade a new logo, or hype a few extra JXTA classes than make real progress.
I use Java at work, and Java will be around with my employer for a long time. With all of this time that has passed since Java 2 came out, I have seen little improvement in the stuff that actually matters. Makes me wonder if things will be the same in 5 years.
Well, I am not too worried about the logo, that is more the matter of the marketing department. As for the features, they need to stop stuffing around and start working with other Java community members and get features into the standard as fast as possible. Just look at what is happening on the shared VM front. Why is SUN alone working on this? why don’t they colaborate with the likes of IBM? Oracle? BEA?
SUN needs to realise that to beat Microsoft they need to work AS A TEAM rather than bickering and whinging over whether or not the feature was produced by a SUN engineer. For example, what is taking SWT so long to be accepted as a good replacement for SWING? Swing is as slow as ####, yet, we still have SUN praise it to the roof tops as if it is mana from god.
all the smart execs and intelligent workers left long ago. sun is left with the corporate retards that wouldn’t get a job anywhere else.
trying to popularize a fringe-appeal technology (jxta) is just plain stupid. what compelling business problem does it solve?
trying to turn java into a brand will backfire on sun. as the world found out the hard way, java is a closed standard. for a company that beats the ‘open standards’ drum it is hyping their own hypocrisy.
furthermore, just what does ‘java’ mean to the average developer? write 2.4 times, test 87 times? hire 1000 sun/ibm/bea consultants to figure out all of sun’s hacked together java classes? spend tons of money on java app server software? go to finance and get the lease-line upped for all the new servers the java system is going to need? ask sun why they think all computing problems can be solved using one low power object language…
sun needs to solve real business problems. the dotcom age of marketing hype is over, at least for the time being. branding a dotcom technology is not a wise move, especially when you are losing giant chunks of marketshare.
oh well. at least sun’s stupidity is helping the shareholders of ibm, hp, fujitsu and dell.
In p2p research arena, lots of academic/research institute adopt JXTA as their platform for R&D.
(i think the main reason is, no need to make their hands dirty of “low-level” things. they can emphasize on inventing new things. — just a guess).
NASA (JPL) use it in its Object Oriented Data Technology. [ http://oodt.jpl.nasa.gov ]
Siemens ported JXTA to Win CE and Java Personal Edition (for their mobile device).
Japanese’s Digital Dream use JXTA in its groupware product.
Well, I still never heard of it in a real consumer product. But at least it already has its places
your letter is not only out of topic, it also shows your hatred of sun and lack of information on java.
please get a life. don’t forget that although you do not think in that way, java is a massively successful technology, being used in more than half of open source projects worldwide, and many commercial projects. so, java means much to the average developer. and project managers. such as me. for instance, i directed and initiated 18 java projects last year, all of them were all massively successful.
“ask sun why they think all computing problems can be solved using one low power object language…” who said they think in that way? please stop making up.
jxta is a very successfull project, and if you would like to learn about it, visit http://www.jxta.org and read about it. basicly, it is jini-like distributed systems project without relying on java as strong as jini.
there is even a great list of companies currently using it. here: http://www.jxta.org/companies/companyarchive.html
and yes, i am sure some idiots among you will still say it is useless. anyway. i’m going to skin up another joint. cheers. –; )
I agree, however, the rants about jxta is like someone crapping on about a certain feature in the win32 api and how many people use it.
jxta, IIRC, is a specification, and there is good reason why some have adopted and others haven’t. Whether or not it has been adopted it besides the point, the fact that it is there in the framework for anyone to use it a plus.
You generalize wildly without anything to backup your facts. Many of the CEO’s of today’s biggest companies came from SUN and SUN has a lot of intelligent people, in fact mst of the ones taht weren’t at their best or were working in an area which was not important for SUN do not work for it anymore.
Java is not a closed stadnard at all, in fact you can download it and it is a lot more open than .NOT, in addition Java is not a complicated language in tehw y you make it sound, i found it easier to pickup tahn C++.
You must really work for Microsft or anotehr company against SUN, becasue no sane human being with any information would make such outrageous claims without anything to back them up.
You obviously just want to hurt SUN and have no intention on even trying to defend your lies,.
1/ I think Java is a great language. For the server, it’s widely used, it’s great and portable.
For the client, I agree that at first Swing was a disappointment. Now however on today’s hardware you can create beautiful and fast apps (just take a look at http://www.jgoodies.com/).
If you don’t like Swing you can still use SWT (native widgets), or the wxWindows Java port (http://www.wx4j.org/).
2/ They gave us OpenOffice!
Go Sun !
I am using 1.4.2 beta and there is a noticeable speed improvement. I download Netbeans the other day (which used to be a poster child for slow Java apps) and for all that is included and it being in Java it opens rather spritely.
With Sun relaxing the JCR (2.6) a little, I think that they will be more responsive to the developers needs.
They should have had a shared VM for 1.5 though. That irks me a bit. But I do know it is coming.
Is that apps need to be designed well, to work well. If you just hacked something together it’s going to crawl, but design it well and the performance is decent.
The Java-lovers will not tell you these things, so listen up.
Because of Java’s design, the inherent complexity in building a large enterprise application is far greater than that in any language or system that had ever been used before. Java solutions requires more lines of code than any other language. Java solutions typically take longer to write as well.
Java has big problems because it doesn’t work the same on different VM’s or does it work the same on different “J2EE” platforms.
The bugs you find between platforms are insidious and hard to find. The amount of testing needed to find these bugs is insane and over the top. Many times, you have object life cycle bugs that take hours to develop. Most Java servers have to be restarted at least once a day to clear out memory because of the strange object life cycle bugs that Java has.
Sure, lots of people use Java in the market. In its day, lots of people used COBOL too. Does it mean, COBOL was the be-all end-all solution to all business problems? Nope.
The way Java is marketed is foolish. It is not the final solution to all business problems. It is a technology that rode the dotcom hypewave to popularity. It will be around a long time, like COBOL, but the more interesting business problems will likely be solved using other means.
For long term success, Java does have a good future in the areas it was designed to work in — closed environments like set-top boxes. So you find it works pretty well in cell phones and in PDA’s. However, it has serious failing when it comes to being some sort of enterprise server platform.
[quote]
Because of Java’s design, the inherent complexity in building a large enterprise application is far greater than that in any language or system that had ever been used before. Java solutions requires more lines of code than any other language. Java solutions typically take longer to write as well.
[end quote]
What nonesense! Wow all the programmer’s that use Java and say it is great for large business applications must not know what they are talking about.
The financial sector must not use large enterprise applications: http://theregister.com/content/53/31021.html
Lots of banks used COBOL too. It doesn’t mean anything. Java is today’s overhyped technology that consistently underdelivers. The language is rigid and bloated just like COBOL. And it will have its day and then go away, just like COBOL.
Even in your article, only 44% of the interviewees said they were going J2EE and that wasn’t even 100% J2EE, merely “primarily”.
For 44% of interviewees, this was “primarily J2EE”, while 17% answered “primarily .Net”.
[you said]
Because of Java’s design, the inherent complexity in building a large enterprise application is far greater than that in any language or system that had ever been used before. Java solutions requires more lines of code than any other language. Java solutions typically take longer to write as well.
[end quote]
I agree that very often a Java-based solution will be over-engineered. But thats not because of the language, but because of the people implementing it!
I’m not sure which languages you are comparing Java to when you are talking about lines of code. Certainly there are languages that are allow you to write a LOT less code, like Python, but for an enterprise type of application, Java and EJB gives you a lot of features for “free” (after you have read a few books and paid a consultants a lot of money…)
Unfortunately, the choice of the implementation language is always a political question. A long time ago I used to think that Java was wonderful… Now I’m just very happy that microsoft created c#, essentially an improved version of Java, so that SUN finally has had to improve the langauge a bit.. about time!
I am not even a Java *zealot* but his statements are incorrect about Java and large enterprise applications. Java is and will continue to get better.
“Because of Java’s design, the inherent complexity in building a large enterprise application is far greater than that in any language or system that had ever been used before. Java solutions requires more lines of code than any other language. Java solutions typically take longer to write as well.”
what a stupid remark. java is a language. you are complaining about the complexity of building enterprise applications in java. listen michael. if you find j2ee complex, then don’t use it. there are more than 20 web application frameworks for java. j2ee is one of them. even apache has three. for instance, echo is a great framework. besides, there are many rad tools being designed to cope with complexity of j2ee. for instance sun’s ace.
“Java has big problems because it doesn’t work the same on different VM’s or does it work the same on different “J2EE” platforms.”
the vm sharing will come soon. on the other hand, your remark on incompetibility between j2ee containers is simply wrong. i am quite experienced on the subject, and i can say, it takes maximum two days to migrate a large project from one implementation to another. you mainly deal with deployment descriptors, and you don’t have to rewrite code.
“The bugs you find between platforms are insidious and hard to find. The amount of testing needed to find these bugs is insane and over the top. Many times, you have object life cycle bugs that take hours to develop. Most Java servers have to be restarted at least once a day to clear out memory because of the strange object life cycle bugs that Java has.”
completely nonsense. there are many many j2ee based web applications running very successfully. for instance ebay, photosig etc.
“Sure, lots of people use Java in the market. In its day, lots of people used COBOL too. Does it mean, COBOL was the be-all end-all solution to all business problems? Nope.”
no-one is claming java is the holy grail of the it industry. but it currently works very well, and there is basically no other technology to replace it in the coming at least 5 years. .NET for instance, is not cross platform compatible. Mono is unreliable, amateurish attempt, i am very hopeful of python though. it is progressing very well.
“The way Java is marketed is foolish. It is not the final solution to all business problems. It is a technology that rode the dotcom hypewave to popularity. It will be around a long time, like COBOL, but the more interesting business problems will likely be solved using other means.”
by what means can i ask?
“For long term success, Java does have a good future in the areas it was designed to work in — closed environments like set-top boxes. So you find it works pretty well in cell phones and in PDA’s. However, it has serious failing when it comes to being some sort of enterprise server platform.”
enterprise server is the area java is the most successful. what are you talking about? –: )