5 ms·

"Rule No. 11: Be nice to nerds. You may end up working for them. We all could." It's funny, but at the time this was written this was kind of a controversial a

• crikli 16y ago
  Fifteen, wasn't it? 1996 was the "reprinted from" date. The net was really just breaking public at that point. If I time traveled back to visit 1996-me, I don't think I could even explain what 2011-me did for a living because the technology didn't exist yet.
  • dasil003 16y ago
    I would say "software applications that run purely on the web" to which the 1996-me would say "how do you even do that?"
    • Samuel_Michon 16y ago
      And that would be a valid question, as 1996-you would be using Netscape Navigator 2 or Internet Explorer 2. Good luck building web apps for those browsers ;)
      • zackattack 16y ago
        School a youngster. Exactly what would have been so difficult about building a spreadsheet interface for IE2? Assuming a crap UI is tolerable for business purposes and assuming that you wouldn't have to market it.
        • evilduck 16y ago
          I assume you mean something like Google Doc's spreadsheet app. Let's say it's 1996. The DOM wasn't standard, HTML4 was still in the works. I'm not sure if IE2/3 or Netscape 2 could even dynamically access table elements at the time. Javascript performance was utterly terrible, and JScript had a strong presence that created an important and problematic language/support divide. CSS didn't exist at all, your visual styles were either images or elements rendered as the browser saw fit. XHR didn't exist and wouldn't exist until IE5, 4 years later. There was no way to update a page without a round trip to the server. This was also during the days of AOL and Dialup.
          • Natsu 16y ago
            I envision a table filled with a grid text input boxes and some buttons to add more rows or columns and maybe to do a few other things. We'll do things server-side if we have to. Ugly as sin? Slow as hell? Absolutely. Probably doable, though.
            • zackattack 16y ago
              exactly...it seems like all the developments have ben purely cosmetic
              • deleted 16y ago
                [deleted]
        • deleted 16y ago
          [deleted]
        • Samuel_Michon 16y ago
          There were few web applications back in 1996. I can only think of two major ones: Lotus had a webmail product called cc:Mail and eBay just started offering online auctions. Back then, you wouldn't use PHP, CSS, Javascript, XMLHttpRequest or Flash. They didn't exist or hadn't matured yet. Most likely, you would've used a Java based solution, such as NeXT WebObjects. That's what e-commerce businesses did back then. However, you wouldn't have developed the product on your own. You would've needed a team and plenty of funding, in part because WebObjects came with a $50,000 price tag. I encourage you to read this WebObjects advertorial from april 1997, courtesy of the Wayback Machine. It's a good illustration of what was considered modern web development: http://replay.waybackmachine.org/19970412201603/http://www.next.com/WebObjects/Overview.html http://replay.waybackmachine.org/19970412201603/http://www.n...
          • mgkimsal 16y ago
            You would have used Perl or PHP - I was using both from early 1996, and they worked just fine. Yes, they hadn't "matured", but they were functional well before Java or ASP were even available. Server-side Java was not something as widely available as Perl or PHP, and Java as a language was not written for the web like PHP was (easily embeddable in HTML, straightforward DB access, etc). WebObjects - didn't have any direct experience with that back then, but it and many other proprietary options were quite pricey, IIRC.
      • wazoox 16y ago
        Hey, I really tried, but I didn't know any better back then.
      • jarek 16y ago
        Correct me if I'm wrong but I don't believe client-server applications were a new idea in 1996. Instead of having a fat client, generate HTML and go back to the HTTP server for every request. The application wouldn't be fast and the code probably wouldn't be pretty, but it would definitely be a software application that runs purely on the web.
    • spc476 16y ago
      Painfully. I remember working on sites back then that might be considered web apps, and I don't think you could even count on cookies at that time. One experiment I did involved passing data along (part of the URL in a GET, or a continuous set of pages generated via POST requests). Everything done on the server side (even Java applets were problematic: http://www.conman.org/people/spc/refs/search/search.hp1.html http://www.conman.org/people/spc/refs/search/search.hp1.html). Web apps at the time were more ... um ... document centric than now. But still, despite the lack of cookies, AJAX and Javascript, databases still existed back then, and CGI programs could be written in any langauge (Perl was popular back then). So it wasn't completely hopeless, but the apps were simpler though.
      • InclinedPlane 16y ago
        You'd think it was the dark ages back then, with people rubbing sticks and stones together. In truth it wasn't so bad. Markup was more cruder and more troublesome than today with HTML4/5 and CSS2/3 but there's nothing wrong with a simple layout. Cookies couldn't be entirely depended on but you could still keep track of the equivalent with a query parameter that you put into every url. Server side tools were cruder but there was still perl so you didn't have to roll everything on your own out of C (though many web apps in 1996 were written in C/C++). Some of the biggest web companies of today such as amazon and ebay got their start in that era and were already doing big business even back then.
• dennisgorelik 16y ago
  It's only obvious to you because you personally grew up. It's still not obvious to modern teenagers.