A bowl of rice would contain far too many carbs to stay in ketosis. If you ate that, combined with all the recommended high fat foods for the Atkin's diet, then you'd end up fatter.
I'd also advise against for now...I've never seen so many bugs in a production application. Most of them are non-critical, but when you're annoyed by them constantly (copy and paste text bug anyone?) you feel like using switching to the latest release of Eclipse instead.
Hopefully things will be resolved in the next version.
True, the ENVY based repository of VA Java was a great thing, but having used both IDE's I'd be very reluctant to move back to Visual Age. It lacks many more features in *all* other areas compared to Eclipse.
Very long lines. I saw a few that were about 160 characters long, twice what they should be.
Not to nit-pick, but in this day and age I don't think we need to have the 80 char limit for a line of code anymore. I personally use a 120 char limit in Eclipse.
IDE support is not just setup wizards - it would include things like compile time validation (e.g. 'Error in adduser.jsp: Action mapping "/addUser" does not exist' and the like)
It would also include good support for refactoring - have you ever tried to rename a function in one of your Struts applications? You need to rename jsp filenames, Action mappings, ActionForms, class files, packages...it's a bloody nightmare having to restart the server and test everything just to find what you've forgotten to change!
While I'm not sure about other IDE's, Websphere Studio Application Developer 5 has some initial Struts support (1.1 beta 2 I think), but it has a long way to go to providing the full set of features a Struts developer would like to see. It does do the GUI presentation of struts-config.xml files you'd like to see though.
Closed source applications tend to follow the traditional model of aggressive release schedules. With coders struggling to hit these deadlines we see the quality of code going down because of the tendency to produce a quick fix for features.
Open source code tends to get released 'when it's ready', removing the deadline pressures from coders, leaving them to write more elegant, bug-free code.
It's more about quality in terms of the code being well-written, bug free, and maintainable. These are the things which create a lasting, reliable and hence popular product.
The problem isn't Eclipse, it's Websphere. WSAD is an absolute pig and the worst memory hog I've had the displeasure of having to work with. You need 1 GB to get it to run smoothly all day.
To be fair though, it does have a full J2EE Server/Test environment built in, and it is very useful when you get a chance to work with it between the 2 minute page swaps....
Yes it's easy to install, but Slackware never strived to have that illusion of simplicity that other distros tried and (IMO) have failed at. This scares some newbies, but teaches you Linux in the most straightforward way.
It's not better in all ways than all other languages. I don't think anyone would argue that point (ok, maybe Scott McNeilly..but not James Gosling).
The great thing about it is its extensive library, which alongside things like garbage collection and exception handling make it relatively simple to build a complex enterprise application, and by extension less expensive. I think mediocre coders (who will cost companies less) can build more robust apps in Java than other popular languages.
Sure, other languages have great libraries, and they are great languages too. My point was in response to your comment "What exactly is there in Java that allows one to build "complex applications?".
What exactly is there in Java that allows one to build "complex applications"?
Are you kidding? How about an extensive, reliable, tested library of networking, user interface, and I/O code which can be used to create "complex applications" extremely easily.
I look at their code and it appears to me like they don't know how to use a relational database, so they spend a bunch of code on reinventing indexing, joining, multi-user contentent management, persistence, searching, sorting, etc
I can't comment on your colleague's coding standards and style, but it appears that they may have been coding cross platform JDBC code, using only simple DB features so that they could switch databases easily. I know it's not unusual to develop initially using something like Apache/Tomcat and MySql, then switch to 3rd party commercial app servers and databases. Anyway, a criticism of their code cannot be taken as a criticism of the language. The fact that you can replace these DB functions in Java code makes it even more flexible.
couple of comments on that article
on
The Future of Java?
·
· Score: 2, Informative
They failed to mention the biggest advantage to using Java - a company can develop a front to back end solution completely using Java. Admittedly, this should be achievable using C# now, but I think this is what companies are interested in rather than any cross platform abilities of the code.
Also, it always irritates me when they ask only the most biased people imaginable whether such-and-such a technology is going to survive. It's like asking the Pope and the Ayatollah which is the best religion...and leaves us no clearer as to what is really going to happen...
You're right, but this is also about the corporate environment where users can now run web based Java applications without the hassles of downloading the JRE first.
Slashdot Mirror
A bowl of rice would contain far too many carbs to stay in ketosis. If you ate that, combined with all the recommended high fat foods for the Atkin's diet, then you'd end up fatter.
I'd also advise against for now...I've never seen so many bugs in a production application. Most of them are non-critical, but when you're annoyed by them constantly (copy and paste text bug anyone?) you feel like using switching to the latest release of Eclipse instead.
Hopefully things will be resolved in the next version.
Isn't that only in WSAD? I don't think Eclipse has any EJB support out of the box.
Make sure you're not using the 1.4.2_02 release. It has a major problem which causes various applications to crash frequently.
True, the ENVY based repository of VA Java was a great thing, but having used both IDE's I'd be very reluctant to move back to Visual Age. It lacks many more features in *all* other areas compared to Eclipse.
Not to nit-pick, but in this day and age I don't think we need to have the 80 char limit for a line of code anymore. I personally use a 120 char limit in Eclipse.
But very helpful for the Apache coders, and another addition to the 'Open Source Software bugs are fixed 10 times quicker' argument :)
IDE support is not just setup wizards - it would include things like compile time validation (e.g. 'Error in adduser.jsp: Action mapping "/addUser" does not exist' and the like)
It would also include good support for refactoring - have you ever tried to rename a function in one of your Struts applications? You need to rename jsp filenames, Action mappings, ActionForms, class files, packages...it's a bloody nightmare having to restart the server and test everything just to find what you've forgotten to change!
While I'm not sure about other IDE's, Websphere Studio Application Developer 5 has some initial Struts support (1.1 beta 2 I think), but it has a long way to go to providing the full set of features a Struts developer would like to see. It does do the GUI presentation of struts-config.xml files you'd like to see though.
It's like comparing a F1 racing car to a FIA World Rally Car:-
One is built from the ground up using completely custom in-house parts while the other is built from many separate already manufactured parts.
Almost everyone.
What platforms do you use for development?
Eclipse, Websphere Studio Application Developer
What Dbs do you use?
SQL Server 2000
What web server?
Apache/Tomcat/JBoss
Why?
Because they're all any 2 of the following 3:
a) Free
b) Easy to use/configure
c) Powerful
Actually, Websphere is only (c), but meh...
Closed source applications tend to follow the traditional model of aggressive release schedules. With coders struggling to hit these deadlines we see the quality of code going down because of the tendency to produce a quick fix for features.
Open source code tends to get released 'when it's ready', removing the deadline pressures from coders, leaving them to write more elegant, bug-free code.
It's more about quality in terms of the code being well-written, bug free, and maintainable. These are the things which create a lasting, reliable and hence popular product.
The problem isn't Eclipse, it's Websphere. WSAD is an absolute pig and the worst memory hog I've had the displeasure of having to work with. You need 1 GB to get it to run smoothly all day.
To be fair though, it does have a full J2EE Server/Test environment built in, and it is very useful when you get a chance to work with it between the 2 minute page swaps....
I would guess that the ONLY thing the OSX team and the GNOME team have in common is their coding skills.
does that mean we can't say 'Free as in beer' anymore?
is my pick for last year's underappreciated movie.
The Catcher in the Rye updated to modern times.
Yes it's easy to install, but Slackware never strived to have that illusion of simplicity that other distros tried and (IMO) have failed at. This scares some newbies, but teaches you Linux in the most straightforward way.
Repost - someone already posted about floppies above this....
If you can't imaging the Zaurus' organizer functions being any better, then you must have the imagination of a brick...
It's not better in all ways than all other languages. I don't think anyone would argue that point (ok, maybe Scott McNeilly..but not James Gosling).
The great thing about it is its extensive library, which alongside things like garbage collection and exception handling make it relatively simple to build a complex enterprise application, and by extension less expensive. I think mediocre coders (who will cost companies less) can build more robust apps in Java than other popular languages.
Sure, other languages have great libraries, and they are great languages too. My point was in response to your comment "What exactly is there in Java that allows one to build "complex applications?".
Are you kidding? How about an extensive, reliable, tested library of networking, user interface, and I/O code which can be used to create "complex applications" extremely easily.
I look at their code and it appears to me like they don't know how to use a relational database, so they spend a bunch of code on reinventing indexing, joining, multi-user contentent management, persistence, searching, sorting, etc
I can't comment on your colleague's coding standards and style, but it appears that they may have been coding cross platform JDBC code, using only simple DB features so that they could switch databases easily. I know it's not unusual to develop initially using something like Apache/Tomcat and MySql, then switch to 3rd party commercial app servers and databases. Anyway, a criticism of their code cannot be taken as a criticism of the language. The fact that you can replace these DB functions in Java code makes it even more flexible.
They failed to mention the biggest advantage to using Java - a company can develop a front to back end solution completely using Java. Admittedly, this should be achievable using C# now, but I think this is what companies are interested in rather than any cross platform abilities of the code.
Also, it always irritates me when they ask only the most biased people imaginable whether such-and-such a technology is going to survive. It's like asking the Pope and the Ayatollah which is the best religion...and leaves us no clearer as to what is really going to happen...
Shawn sometimes responds to Slashdot threads regarding TheKompany.
You're right, but this is also about the corporate environment where users can now run web based Java applications without the hassles of downloading the JRE first.