<venividi> hooray for emacs and jdee. *much* easier, faster, and more resource friendly than eclipse.
<venividi> (that's *right* folks, i've found something where emacs is *more*
resource friendly than the competitor...)
I swear that Java is the bane of my existence. Every single bloated app that runs on our servers is either some poorly-coded Java thing, or it's a freaking unsupported middleware product.
Also, emacs used to be the bomb back in college, but that was before I had to boot a server from a tape backup in maintenance mode...
You know, I really want to assume the problem is poor server allocation and load balancing, but I swear that the worst, slowest sites I use on a regular basis are uniformly JSP/ASP backed by Cold Fusion or SQLServer.
Please, somebody, prove to me that similarly spec'd hardware can, under similar conditions, handle the same load whether it's some raggedy-ass LAMP setup or finely-tuned MS/MS-CF setup.
Personally, I heart IDEA. Sure, you have to pay for it. But it's like Eclipse if Eclipse had more features that you actually need for Java dev and if Eclipse didn't suck horrendously. And, something that has always been key for me, it will still allow you to do code analysis and refactoring even if you aren't set up to build using it's build tools! (Honestly, who uses their IDE to build? Who ever has a build system simple enough for an IDE to emulate well? I've never seen it happen.)
Overall, I find it to be a huge productivity enhancer.
There is a free 30-day trial.
(Note - There is an annoying issue I see with the 5.0.2 release on Debian - my typing goes to the wrong open tab! You may want to just use 4.0 if you're on a Linux platform. Hell, any release since 3.0 is pretty damn spiffy.)
Last week I made my first serious attempt at using Eclipse to earn a living. I confess however that I would never have stooped to this if I had reasonable access to the filesystem of the development server.
It's not too bad as IDEs go, although it's still slightly behind where Cafe and Visual J++ were five years ago. (My current client is IBM, so my chances of being able to use IntelliJ are basically zero.)
Tomcat 5, when coupled with Eclipse and the Sysdeo plugin, has also finally reached a tolerable modicum of usability, although it's documented even more poorly than was version 4.
Emacs is fine for Java apps that are intended to be shell-launched, but I swear to God I would go postal on somebody if I had to configure Tomcat manually.
Nobody cares about efficiency any more. For what it costs to get a knowledgeable person to do performance tuning, you can buy two or three more servers.
The proof of this is that we're using Java for ANYTHING, let alone almost everything.
I just got done coding a really slick perl app for NASA that runs almost entirely out of RAM cache and hardly ever touches the disk, but does anyone care?
Nah. They'd rather have it in Java so they can have their junior code monkeys hack on it.
Pet peeve: Sites that rebuild the exact same pages dynamically every time someone views the page. And then people complain when they're only allowed to use 60 CPU-minutes a day on their shared host.
I've written software that serves up a handful of pages a second, and barely registers on the CPU, with the incredible innovation of writing static pages to disk as HTML files and letting Apache serve them up.
The app I'm talking about is like that, except that the static pages live in memory (there are only a few of them), along with (nearly) all the prepared DBI queries. (There was another guy working on the project who couldn't get beyond preparing a new query every time he hit the database, but fortunately most of the code is mine, not his.)
It replaced a monstrosity of embperl templates, served afresh from disk every time they were hit. Because the previous contractor couldn't be bothered to design a database schema, they stored all the data as serialized hashes in CLOB fields. Yay.
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif){kind=small}
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
syntheid
no subject
Date: 2006-01-22 06:47 pm (UTC)Also, emacs used to be the bomb back in college, but that was before I had to boot a server from a tape backup in maintenance mode...
no subject
Date: 2006-01-23 01:08 am (UTC)Please, somebody, prove to me that similarly spec'd hardware can, under similar conditions, handle the same load whether it's some raggedy-ass LAMP setup or finely-tuned MS/MS-CF setup.
no subject
Date: 2006-01-23 02:21 am (UTC)Overall, I find it to be a huge productivity enhancer.
There is a free 30-day trial.
(Note - There is an annoying issue I see with the 5.0.2 release on Debian - my typing goes to the wrong open tab! You may want to just use 4.0 if you're on a Linux platform. Hell, any release since 3.0 is pretty damn spiffy.)
no subject
Date: 2006-01-23 10:46 pm (UTC)It's not too bad as IDEs go, although it's still slightly behind where Cafe and Visual J++ were five years ago. (My current client is IBM, so my chances of being able to use IntelliJ are basically zero.)
Tomcat 5, when coupled with Eclipse and the Sysdeo plugin, has also finally reached a tolerable modicum of usability, although it's documented even more poorly than was version 4.
Emacs is fine for Java apps that are intended to be shell-launched, but I swear to God I would go postal on somebody if I had to configure Tomcat manually.
no subject
Date: 2006-01-23 10:55 pm (UTC)The proof of this is that we're using Java for ANYTHING, let alone almost everything.
I just got done coding a really slick perl app for NASA that runs almost entirely out of RAM cache and hardly ever touches the disk, but does anyone care?
Nah. They'd rather have it in Java so they can have their junior code monkeys hack on it.
no subject
Date: 2006-01-24 03:04 pm (UTC)I've written software that serves up a handful of pages a second, and barely registers on the CPU, with the incredible innovation of writing static pages to disk as HTML files and letting Apache serve them up.
no subject
Date: 2006-01-25 02:48 am (UTC)It replaced a monstrosity of embperl templates, served afresh from disk every time they were hit. Because the previous contractor couldn't be bothered to design a database schema, they stored all the data as serialized hashes in CLOB fields. Yay.