Archive for the ‘Linux’ Category
On a side-note, I’ve read that Safari can work on Linux under Wine. I’ll give it a try sometime. Now, if only I could run iTunes under Wine .
From: Linus Torvalds
Date: Sat, 1 Dec 2001 00:58:03 GMT
Subject: Re: Coding style – a non-issue
On Fri, 30 Nov 2001, Rik van Riel wrote:
> I’m very interested too, though I’ll have to agree with Larry
> that Linux really isn’t going anywhere in particular and seems
> to be making progress through sheer luck.
Hey, that’s not a bug, that’s a FEATURE!
You know what the most complex piece of engineering known to man in the whole solar system is?
Guess what – it’s not Linux, it’s not Solaris, and it’s not your car.
It’s you. And me.
And think about how you and me actually came about – not through any complex design.
Right. “sheer luck”.
Well, sheer luck, AND:
- free availability and _crosspollination_ through sharing of “source code”, although biologists call it DNA.
- a rather unforgiving user environment, that happily replaces bad versions of us with better working versions and thus culls the herd (biologists often call this “survival of the fittest”)
- massive undirected parallel development (“trial and error”)
I’m deadly serious: we humans have _never_ been able to replicate something more complicated than what we ourselves are, yet natural selection did it without even thinking.
Don’t underestimate the power of survival of the fittest.
And don’t EVER make the mistake that you can design something better than what you get from ruthless massively parallel trial-and-error with a feedback cycle. That’s giving your intelligence _much_ too much credit.
Quite frankly, Sun is doomed. And it has nothing to do with their engineering practices or their coding style.
I’ve downloaded Jetty Server Adapter for Eclipse recently. Jetty is supposedly very nimble Java-based HTTP Server and Servlet Container. I’m not sure if I’m doing it wrong, but I find code redeployment very slow and buggy when using Jetty on Eclipse. Even Jboss, another heavy duty application server, is bad on Eclipse with 15-25 second redeployment time.
So far I’ve found only Tomcat to be suitable for development with almost instant redeployment.
Another nuisance is that Jetty relies on the presence of PID file ( on my RHEL 4.2) to determine whether it’s running or not, which is, more often than not, inaccurate as I usually close Eclipse without shutting down Jetty server. Tomcat is much more stable in that sense. However, Jetty seems much more exciting to develop “for” (as opposed to “on”) as it has continuations, a very clever hack/feature.
I suppose that the preferred way to develop on Jetty is to use Maven, and Jetty Server Adapter will improve with future releases of WTP/Eclipse milestones.