![]() Presumably a part of the fees that Apple collects from developers covers the cost of auditing extensions for security, and identifying developers which provides a disincentive for user-hostile activity. However, the tension between developer and user friendliness as noted elsewhere in this discussion applies here as well. It definitely would be great if you could use your preferred tools and build from the commandline, or if Apple could ease the process of self-signing for local deployment. (Yes not everyone but it will be widespread enough that browsers will be forced to invent countermeasures.) If you give a web developer service workers they will absolutely drain your battery. If you give a web developer cookies, they inject tracking bugs to invade your privacy. If you give a web developer responsive layouts, they steal your ability to zoom. If you give a web developer media playback, they force auto-playing media on you. With great power comes great responsibility and the JS-advertising-infested web has a really poor record on handling responsibility. Some of the features supported by Chrome are interesting to web-only developers I'm sure, but I don't want the browser on my mobile phone running service workers eating my battery in the background. That isn't wrong or right but it is the truth and it does mean duplicated effort. They could have collaborated on JSCore instead of creating V8. They could have contributed to the process isolation refactor but chose to do their own thing instead. They could have contributed their IndexDB engine to webkit at any time but chose not to. ![]() ![]() I would also remind everyone that Google chose to fork Webkit to create Blink. Safari is actually the first to 100% ES6 compliance Chrome sits at 89%. Looking at the list there are plenty of features supported by Safari and not supported by Chrome including Audio Tracks, Video Tracks, ES6 modules, SVG Fonts, Animated PNG, CSS regions. I don't think it is fair to discount battery life, memory usage, and performance so heavily.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |