What's the best in terms of ease of use? What about flexibility? Scalability? Performance?
Not sure what you mean by flexibility.
Scalability/Performance: If we're going to talk typical Slashdot-geek "I made a web site that generates random yo-mama jokes in PHP," then it's anybody's game. For actual high-volume sites, however, this all depends on the "container" (i.e., application server) the scripts are being run in. Big e-commerce sites will invest in a multiple machine cluster, running a bad boy like BEA WebLogic, and will out-scale/perform anything comparable on the market. Java is bar-none the most robust technology for highly scalable sites.
At this level, though, it's no longer about the fastest script compile time - it's about scalability of servers running your business logic. Again, this moves way beyond scripting languages and becomes a matter of robust application server technology.
No, I think you're missing the point. Showing off nifty new client-side technologies (of which I wouldn't even consider Java to be one anymore) has exactly zero to do with how the pages are processed on the server side. If you acknowledge (or don't, I don't care) that Java is a good technology for running an application server, that still says nothing at all about how those generated pages look on your browser.
Your idea of "old school" is just that - old school. Typical Slashdot reactionary-ism. Just because this site runs off the cgi-bin/ doesn't mean that's the best way to do it. I guarantee you BEA Weblogic running in a cluster using servlets would absolutely devastate the performance of this site on similar hardware. Java (on the server side) is here to stay, at least for a while. You guys won't acknowledge it, but that's okay... the world moves on without you.
And no one is talking about replacing HTML, either. I'm not even going to go into how silly that sounds.
I'd be really worried about burning out if I had to constantly code with at least one person looking over my shoulder. Personally, I like to code alone. I couldn't last too long with somebody else nagging/checking my work. Hell, I don't even like code reviews.
Well, I hate to break it to you, but I sure wouldn't hire someone with this attitude. You're not writing code for a company to have it squirreled away with no one there to look it over. They own it, not you, and they can do what they want with it. Furthermore, if you're not confident enough to have other people challenge you on your code, then you're probably too insecure and/or inexperienced to be terribly great at your job.
I say, bring it on! I want people to look at my code and show me my mistakes. That's how you learn.
I can easily see the principal turning this around saying, "Sorry kids, the reason football and basketball don't get new uniforms this year is because so-and-so cost us $62,000.
Personally, I'm planning to invest in the technology that allows the cameras to follow the "cheerleaders" up into the stands from such an advantageous angle.
I wish I had finished the web site for it by now, but I've been having too much fun playing with the actual machine! I started to build it out of some parts laying around after an upgrade. The specs are as follows:
Celeron 533Mhz (basically the best I could fit on my existing PII mobo)
Software to control mouse is Girder. (It's awesome)
Black desktop ATX case
Black wireless keyboard/trackball (Compaq)
Running Win98 (Radeon can't output digital audio thru SPDIF in 2000 yet)
Creative Labs MP3+ 5.1
Cheapo black DVD-ROM drive
100Mbps ethernet
It generally performs very well. I use it for DVD (only in a secondary capacity, my regular DVD player is superior and I laugh at anyone who claims their PC's DVD player does a better job than a decent component DVD player), MP3 (primarily the reason I built it), watching MPG1/2/DivX movies and VCDs. It can also act as a WebTV in a pinch, though it's running at 800x600 and the text can get hard to read, even when set at largest font.
I do have some issues with the Radeon card (besides the exorbitant price) - it does straight-to-MPEG2 capture, which is nice, but it doesn't enforce a/v synching, which isn't usually an issue until I decide to compress to DivX. Then you usually need to fire up something like AVI Info to correct the problem. I bought the Radeon because it comes with some TV-Guide type software to control listings and recording, but in my experience, it's not really worth it. From what I hear, the ATI AIW 32 is a better card for straight PVR uses.
Session migration over multiple load-balanced machines is touched upon lightly but no technical details were offered. I would have liked to see a practical example on session persistence coupled with a use case of load balancing a JSP website. It's unfortunate also that the authors didn't think that database connection pooling warrants a practical example.
The reason for this is that both of these issues (session persistence across servers & connection pooling) are supposed to be handled by your application server. You, as a developer, should not have to worry about their actual implementation, only that it does happen, and of course the limitations of your vendor's scheme.
Again, I'm afraid I just don't understand what you're saying. You're right in saying that a JSP is compiled into a servlet, but it's transparent to you as the writer of the JSP. The compilation is done by the appserver, and on the type of hardware that a decent server is run on, the largest of pages would take a couple of seconds (first hit after change only) tops.
When was the last time you talked to this friend who loved Java? And was he using Linux or Windows? Try jikes out and see if it's as slow as he claims. I assure you, it is not. Even the regular Sun JDK does nothing close to "slowing your system down to a halt."
By the way, compiling "the whole fricking page" is desirable. This is what makes it so fast. Subsequent hits are precompiled and quite fast.
What are you talking about? The majority of JSP containers have the ability to re-scan their JSP directories for changed JSPs often enough that you make a change, save, and pull it up in the browser!
True, with servlets, you have to re-compile (but this really has nothing to do with JSP/ASP/PHP) but you still don't have to restart your app server in most cases.
Well, what you're leaving out is that Broadvision is absolute crap. Like you said, it's server side JavaScript! Not Java. What a ludicrous concept.
On the other hand, server side Java is a great (IMO the best) way to implement an n-tier architecture. Our typical setups are I-Planet for static content, BEA WebLogic for Servlets and EJBs (may or may not be separate machines or clusters of machines between these tiers), and Oracle on the back end.
How can they objectively prove that an object millions and millions of miles away contains life forms (of course they all conveniently vanished, right).
He's right. We can't. Science is a religion too. Just that ours is cool and new, while the existing ones are old and moldy
Hogwash. Of course we can prove it: we go there. If there is life, thus it is proven.
And science is not a religion. It is the opposite of religion. There is no faith; everything is questioned. Science gives us the right to doubt anything! Faith is the opposite of that.
Slashdot Mirror
Pull down the console, and type fakelag 1000
Not sure what you mean by flexibility.
Scalability/Performance: If we're going to talk typical Slashdot-geek "I made a web site that generates random yo-mama jokes in PHP," then it's anybody's game. For actual high-volume sites, however, this all depends on the "container" (i.e., application server) the scripts are being run in. Big e-commerce sites will invest in a multiple machine cluster, running a bad boy like BEA WebLogic, and will out-scale/perform anything comparable on the market. Java is bar-none the most robust technology for highly scalable sites.
At this level, though, it's no longer about the fastest script compile time - it's about scalability of servers running your business logic. Again, this moves way beyond scripting languages and becomes a matter of robust application server technology.
Your idea of "old school" is just that - old school. Typical Slashdot reactionary-ism. Just because this site runs off the cgi-bin/ doesn't mean that's the best way to do it. I guarantee you BEA Weblogic running in a cluster using servlets would absolutely devastate the performance of this site on similar hardware. Java (on the server side) is here to stay, at least for a while. You guys won't acknowledge it, but that's okay... the world moves on without you.
And no one is talking about replacing HTML, either. I'm not even going to go into how silly that sounds.
Well, I hate to break it to you, but I sure wouldn't hire someone with this attitude. You're not writing code for a company to have it squirreled away with no one there to look it over. They own it, not you, and they can do what they want with it. Furthermore, if you're not confident enough to have other people challenge you on your code, then you're probably too insecure and/or inexperienced to be terribly great at your job.
I say, bring it on! I want people to look at my code and show me my mistakes. That's how you learn.
Nyah!
Pummel the computer geek!
Personally, I'm planning to invest in the technology that allows the cameras to follow the "cheerleaders" up into the stands from such an advantageous angle.
Try *1* CD! You just have to set the bitrate accordingly.
Celeron 533Mhz (basically the best I could fit on my existing PII mobo)
128MB RAM
40GB ATA/100 (running at 33 :( ) HDD, 7200RPM
ATI Radeon All-In-Wonder
Logitech AST Remote - to control mouse/applications
Software to control mouse is Girder. (It's awesome)
Black desktop ATX case
Black wireless keyboard/trackball (Compaq)
Running Win98 (Radeon can't output digital audio thru SPDIF in 2000 yet)
Creative Labs MP3+ 5.1
Cheapo black DVD-ROM drive
100Mbps ethernet
It generally performs very well. I use it for DVD (only in a secondary capacity, my regular DVD player is superior and I laugh at anyone who claims their PC's DVD player does a better job than a decent component DVD player), MP3 (primarily the reason I built it), watching MPG1/2/DivX movies and VCDs. It can also act as a WebTV in a pinch, though it's running at 800x600 and the text can get hard to read, even when set at largest font.
I do have some issues with the Radeon card (besides the exorbitant price) - it does straight-to-MPEG2 capture, which is nice, but it doesn't enforce a/v synching, which isn't usually an issue until I decide to compress to DivX. Then you usually need to fire up something like AVI Info to correct the problem. I bought the Radeon because it comes with some TV-Guide type software to control listings and recording, but in my experience, it's not really worth it. From what I hear, the ATI AIW 32 is a better card for straight PVR uses.
Just my $0.02.
In 3.22.34, it would crash just from a run o' the mill ORDER BY. Hope at least that much is fixed...
The reason for this is that both of these issues (session persistence across servers & connection pooling) are supposed to be handled by your application server. You, as a developer, should not have to worry about their actual implementation, only that it does happen, and of course the limitations of your vendor's scheme.
When was the last time you talked to this friend who loved Java? And was he using Linux or Windows? Try jikes out and see if it's as slow as he claims. I assure you, it is not. Even the regular Sun JDK does nothing close to "slowing your system down to a halt."
By the way, compiling "the whole fricking page" is desirable. This is what makes it so fast. Subsequent hits are precompiled and quite fast.
True, with servlets, you have to re-compile (but this really has nothing to do with JSP/ASP/PHP) but you still don't have to restart your app server in most cases.
On the other hand, server side Java is a great (IMO the best) way to implement an n-tier architecture. Our typical setups are I-Planet for static content, BEA WebLogic for Servlets and EJBs (may or may not be separate machines or clusters of machines between these tiers), and Oracle on the back end.
What he may be talking about is a black hole having infinite density. Zero size, nonzero mass = divide by zero error.
He's right. We can't. Science is a religion too. Just that ours is cool and new, while the existing ones are old and moldy
Hogwash. Of course we can prove it: we go there. If there is life, thus it is proven.
And science is not a religion. It is the opposite of religion. There is no faith; everything is questioned. Science gives us the right to doubt anything! Faith is the opposite of that.