3 ms·
No company would do that. What OEM is going to pay for a new, less compatible browser engine written in an unproven language that no one knows? Even if it is sa
by ecnahc515 3y ago
No company would do that. What OEM is going to pay for a new, less compatible browser engine written in an unproven language that no one knows? Even if it is safer, that's pretty much the lowest priority for many companies, and safer != unable to exploit.
Companies who want to embed a browser engine into their product use WebKit, which is free, and maintained by multiple other companies, and has been around long enough that it should be compatible with pretty much any website that exists.
- toyg 3y agoWebkit was "new and unproven" once. It won out because it was easy to slot in, well-performing, and more modern than alternatives at the time. Most big projects have slowly moved away from WebKit anyway, to its more modern derivatives Blink and Chromium. If Mozilla could produce an engine that is easier/as easy as to slot in, it's maybe faster or lighter in a few areas, and basically guarantees no exploits and crashes, there would be a massive market. Browser views power more and more appliances and applications, for which the current options are "the lesser evil" - cue the complaints about massive Electron apps. There is a big space for competition there, for someone whose main business is building browsers.