> and there was some JS lib (forgot the name) which added a reasonable debugger (this was before browsers themselves had reasonably good integrated debuggers!)
Firebug changed my life when it came out!
> Dude, IE was Windows-only.
Not originally it wasn’t. The UNIX versions are an interesting relic.
It was available on MacOS as well.
Re:SETI@home shuts down after 21 years
by savoytruffle on Wednesday March 04, 2020 @01:36PM
(#22486424)
the grandparent post made the point that for most of its history in the late 90's and early 00's (pretty much all of the CRT iMac era), IE for Mac used an entirely different rendering engine than the Windows version. And then it was abandoned.
If you wanted pixel-perfect it was a fucking nightmare. Literally doubled your work time just to add WinIE compatibility. This was in the IE5/6/7 era.
Speaking of JS... all this was made worse because there were NO good JS libraries at the time to make things easier. Debugging consisted of alerts. Eventually, Prototype (and later Jquery) were literally godsends, and there was some JS lib (forgot the name) which added a reasonable debugger (this was before browsers themselves had reasonably good integrated debuggers!)
Chrome is not like that. The same rendering engine exists on Linux, Windows and Mac, and it has an open-source highly-compatible version, Chromium.