It seems that when Webkit2 is ready then everyone except Chromium will use it. Since Apple will probably throw webkit out the window anyway when webkit2 is ready it seems that everyone moaning about Google here may be a bit backward. Google have long taken the approach it seems to just have entirely separate processes for each page talk to a webkit subprocess via api calls.The webkit2 project are taking a different approach by trying to put multiprocess stuff actually into the webkit2 api itself. They have some pretty diagrams here showing the differences: It seems that the reason for this is to do with the upcoming webkit2 Apple project taking a very different approach to how multiprocess stuff should work. I have just been digging around and think I can answer this question. Why not just make the choice of rendering engine user configurable? Stuff never goes away even if it is broken. Not a closed vs open debate more than a standard one. This is a classic lesson on why standards are so important and why going proprietary is bad. Logic is backwards but CMS never get replaced, sites stay, and users whine and blame YOU if something doesn't work. IE 6 and XP is still being used with its users considering an open standard broken because it breaks and broken standard to them which is open. Things stay freaking forever in the industry once it someone or a corporation is dependent on something. So if removing prefixed properties breaks some pages, that means they were broken in the first place. It was never good practice to use a prefixed property without its unprefixed version. The CSSWG agreement doesn't say anything about phasing out existing prefixed properties, but keeping them around with outdated syntax/behavior doesn't seem like a good idea. Also my IDE VScode, is built with Electron, which exactly the kind of framework as NW.JS.I hope they don't keep -webkit-* enabled forever. Basically it has a webview(that also uses webkit engine) that renders the UI.
Yes even the apps I made, I made them using NW.JS, a framework that allows you to make desktop apps using web programming(HTML+CSS+JavaScript). So far the only thing that I see these apps have in common is that they are using webkit Web Engine.
Https:///WebKit/webkit/tree/main/Source/JavaScriptCoreĪbout Why every browser switching to Blink could be bad news for the web. What is the reason behind choosing a browser engine for making a mail client?
Webkit vs blink windows#
Windows Mail is based on EdgeHTML, Thunderbird is based on Gecko, and Apple Mail is based on WebKit. Why many major mail clients based on web browser engines? As far as I know, if you mean this never had anything to do with the electron project (). I don't know what you mean by Webkit and electron.
įolks, you need to be aware of the very real security risks of themes and plug-ins
Webkit vs blink download#
You can download a copy of WebKit yourself.
0 kommentar(er)
