3 ms·
> It was bad. > Real bad. Apparently it was not so bad that we needed a multitude of JS to JS compilation stages and instead could just, you know, execute the
by _pmf_ 7y ago
> It was bad.
> Real bad.
Apparently it was not so bad that we needed a multitude of JS to JS compilation stages and instead could just, you know, execute the same JS in the browser that we actually wrote.
Also, MS invented DHTML and AJAX single handedly, against backlash from "pure" web developers.
- TimTheTinker 7y agoPlease don't argue with others about their experiences and feelings. I was there, and it was intensely bad. I think it's easy to forget how bad it was, even for those who went through it. Starting mid-2006, I spent almost a year building a full-stack internal SPA for tracking manual and checklist testing at my company. I made the (then brave) decision to target Firefox instead of IE6, which everyone was using at the time - since FF was more standards-compliant. It was a very good decision in retrospect. But I had to spend 4-5 weeks just getting the front-end to work in IE6. So many HTML/CSS hacks, trying to wrangle the layout engine to do my bidding. Check out the Wikipedia article on the Acid2 test, and the image at the bottom of IE6's rendering, to get an idea how far IE6's layout was from standards: https://en.wikipedia.org/wiki/Acid2 https://en.wikipedia.org/wiki/Acid2