I love the paragraph stating the upcoming introduction of Java into Netscape will help the server generate the stores on a user's screen. Every programmer who've seen it, including Paul, must have laughed at that line later on. "Client-side Java taking load off the server? That's silly!" I believe Paul himself has said, in one of his other articles, that some startups failed during the dot com boom simply because they tried to create their businesses using Java.
That is, until last year. With the JavaScript (AJAX) technology saving CPU server cycles[1] by doing a lot of logic in the web browser itself, Paul's one paragraph predicting something he expected to occur within a few months now sounds way ahead of its time. Either that, or such technology has taken 10 years too long to brew. (Coffee reference!)
I would also like to read the business plans of crazy dot com companies which tanked immediately. It would be great to be able to contrast the two. I'm thinking those business plans probably used a lot of made-up words to confuse the investors. Paul's document is pretty succinct.
[1] as well as saving bandwidth and time, of course.
That is, until last year. With the JavaScript (AJAX) technology saving CPU server cycles[1] by doing a lot of logic in the web browser itself, Paul's one paragraph predicting something he expected to occur within a few months now sounds way ahead of its time. Either that, or such technology has taken 10 years too long to brew. (Coffee reference!)
I would also like to read the business plans of crazy dot com companies which tanked immediately. It would be great to be able to contrast the two. I'm thinking those business plans probably used a lot of made-up words to confuse the investors. Paul's document is pretty succinct.
[1] as well as saving bandwidth and time, of course.