Proceeds from the ads below will be donated to the
Bob Wuesthoff scholarship fund.
Friday, August 06, 2004 |
OT: I Hate Java
I don't know why people continue to use Java for actual web applications. mlb.com, 8/6/04 11:09 PDT:
|
Request Timeout The server timed out while waiting for the browser's request. |
I don't care what anybody says, whether it's blogger.com or mlb.com, every Java-based website I've ever used has reliability and performance issues. Every one.
Comments:
I used to work at a company that used the Netscape Application Server. It was unreliable, but we switched over to Weblogic, which is Java, too, but much more stable.
Aye, Ken, but "more stable" in Java isn't necessarily an improvement. Performance still is a problem. Try, for example, to get historical splits on MLB.com. The query will leave you stranded. In fairness, it might also be because they use Oracle for their backend. I could design a system that would have better query response time and handle loads better than the piece of junk that is MLB.com, and trust me, I'm no genius.
A query that takes that long is usually a sign of a poorly constructed SQL statement, or an unindexed database table, combined with bad QA. I doubt that's the fault of the programming language. It's the fault of the people using it.
Designing a system to scale to the size of MLB's traffic is tricky. Certainly, NAS was clearly not the best choice they could have made.
Designing a system to scale to the size of MLB's traffic is tricky. Certainly, NAS was clearly not the best choice they could have made.
Newer› ‹Older
 |
Post a Comment
Note: Only a member of this blog may post a comment.