Maintaining an Independent Browser Is Expensive

Re:Maintaining an Independent Browser Is Expensive by erikbye on Sunday December 03, 2017 @03:21AM (#15836602)

I guess it's not wrong to call it their original engine, just remember it's a two-decades-old development that started at Netscape.

[ Parent | on HN ]

Re:Maintaining an Independent Browser Is Expensive by gsnedders on Sunday December 03, 2017 @04:11AM (#15836748)

Well, arguably started at DigitalStyle.

[ Parent | on HN ]

Re:Maintaining an Independent Browser Is Expensive by robin_reala on Sunday December 03, 2017 @05:35AM (#15836978)

Can you expand? I thought I had a good grasp of Mozilla’s history but this is the first time I’ve heard of them.

[ Parent | on HN ]

Re:Maintaining an Independent Browser Is Expensive by dev_tty01 on Sunday December 03, 2017 @08:49AM (#15837553)

https://en.m.wikipedia.org/wiki/DigitalStyle

[ Parent | on HN ]

Re:Maintaining an Independent Browser Is Expensive by gsnedders on Sunday December 03, 2017 @12:02PM (#15838378)

So my understanding is following Netscape's acquisition of DigitalStyle, the decision was made to replace Netscape's existing layout engine with something based on what DigitalStyle had in their editor (which, unlike Netscape's existing one, supported things like reflow), and it was this combination that was open-sourced. Notably, it was only really the layout engine that was replaced: the HTML parser and the JS VM survived unchanged, hence the name NGLayout for what became Gecko.

[ Parent | on HN ]