News for hackers. Stuff that matters.

A comment on Maintaining an Independent Browser Is Expensive. Parent comment

Re:Maintaining an Independent Browser Is Expensive by gsnedders on Sunday December 03, 2017 @04:14AM (#15836757)
Note those releases were based on an entirely different codebase to the Windows version of IE.
[ Parent | on HN ]
Re:Maintaining an Independent Browser Is Expensive by thristian on Sunday December 03, 2017 @05:55AM (#15837048)
Internet Explorer for Mac was a separate codebase from the Windows version.

The Unix workstation versions (HP-UX, AIX, etc.) were built with a commercial equivalent to Winelib: a library that implemented Win32 APIs on top of Unix and X11.

I have no idea how they managed to build the IE code on a compiler that wasn't MSVC.

[ Parent | on HN ]
Re:Maintaining an Independent Browser Is Expensive by gardnr on Sunday December 03, 2017 @03:38PM (#15839449)
When you say "entirely different" you mean they didn't even share the same rendering engine?
[ Parent | on HN ]
Re:Maintaining an Independent Browser Is Expensive by gsnedders on Sunday December 03, 2017 @05:13PM (#15839942)
The sibling suggests that non-Mac ports shared the Trident rendering engine with IE/Win. IE/Mac used Tasman, which was totally different (and was the first implementation of many CSS 3 features); as far as I'm aware there was no code shared at all between IE/Win and IE/Mac.
[ Parent | on HN ]