4 ms·

Microsoft are insane about providing compatibility when it suits them. It will work - if they see a business case for it.

cududa 11y ago
I was just thinking after reading this - sure there were some engineering marvels that enabled this, but for the implementation it was just rote work with the sheer manpower Microsoft can muster up. That in itself is just really impressive. Edit: giving it more thought, a Mozilla engineer recently demo'd an immediate mode rendering engine that him and one other dev wrote in 9 months, with feature parity of modern browsers. So either way - big engineering effort or a couple '10x developers' - pretty impressive .
- mamon 11y ago
  >> big engineering effort or a couple '10x developers' - pretty impressive Or, being Mozilla engineer for quite some time he had enough domain knowledge to do that. Or he found a clever way to reuse good parts of Mozilla code with just enough changes to avoid copyright infringement lawsuit.
  - cyphar 11y ago
    > Or he found a clever way to reuse good parts of Mozilla code with just enough changes to avoid copyright infringement lawsuit. If he used code from free software he wouldn't be liable for copyright infringement, because that's the point of free software.
  - cyphar 11y ago
    > Or he found a clever way to reuse good parts of Mozilla code with just enough changes to avoid copyright infringement lawsuit. If he used code from free software he wouldn't be liable for copyright infringement, because that's the point of free software.
- the_why_of_y 11y ago
  Assuming you're talking about WebRender? http://pcwalton.github.io/slides/webrender-talk-022016/ http://pcwalton.github.io/slides/webrender-talk-022016/ ... which is notable because it is not immediate mode but the first retained mode renderer in a browser. Also, they used Rust to cut down on the time spent debugging threading issues.
  - cududa 11y ago
    Sorry - mixed up immediate/ retained

cududa 11y ago

I was just thinking after reading this - sure there were some engineering marvels that enabled this, but for the implementation it was just rote work with the sheer manpower Microsoft can muster up. That in itself is just really impressive. Edit: giving it more thought, a Mozilla engineer recently demo'd an immediate mode rendering engine that him and one other dev wrote in 9 months, with feature parity of modern browsers. So either way - big engineering effort or a couple '10x developers' - pretty impressive .

mamon 11y ago
>> big engineering effort or a couple '10x developers' - pretty impressive Or, being Mozilla engineer for quite some time he had enough domain knowledge to do that. Or he found a clever way to reuse good parts of Mozilla code with just enough changes to avoid copyright infringement lawsuit.
- cyphar 11y ago
  > Or he found a clever way to reuse good parts of Mozilla code with just enough changes to avoid copyright infringement lawsuit. If he used code from free software he wouldn't be liable for copyright infringement, because that's the point of free software.
- cyphar 11y ago
  > Or he found a clever way to reuse good parts of Mozilla code with just enough changes to avoid copyright infringement lawsuit. If he used code from free software he wouldn't be liable for copyright infringement, because that's the point of free software.
the_why_of_y 11y ago
Assuming you're talking about WebRender? http://pcwalton.github.io/slides/webrender-talk-022016/ http://pcwalton.github.io/slides/webrender-talk-022016/ ... which is notable because it is not immediate mode but the first retained mode renderer in a browser. Also, they used Rust to cut down on the time spent debugging threading issues.
- cududa 11y ago
  Sorry - mixed up immediate/ retained