Tom Warren:, writing for The Verge:
Something had to give. Microsoft had to change its Edge browser in a big way. That meeting with Nadella ultimately led to Microsoft’s huge decision to jettison the browser it built in house and start from scratch using Chromium as a new foundation. The stakes for success couldn’t be much higher: the future of Windows and the web itself could hinge on this project.
This is the story of how Microsoft made that monumental decision and what could happen next.
I’m not personally interested in Edge or particularly happy that Microsoft joined the Blink/Chromium camp. I would have definitely been more please had they based Edge on WebKit or Gecko…
And speaking of WebKit…
I’m deeply disappointed in Apple for discontinuing Safari for Windows and not expanding to Linux and other operating systems. I don’t trust Google or Microsoft’s priorities (Google’s especially), and Chrome needs to lose some market share for our benefit. History has shown that a monopoly in the browser department doesn’t end well. Apple had the unique ability to challenge Google on competing desktop OSes and they forfeited that fight. Yes, Safari is holding its own on mobile. For now. That could change, when something new comes along, replacing our iOS and Android devices. At this point, all I can do is also root for Mozilla and Firefox.
Filip Pizlo, for WebKit.org:
This document explains how Spectre and Meltdown affect existing WebKit security mechanisms and what short-term and long-term fixes WebKit is deploying to provide protection against this new class of attacks.
I feel so guilty for wasting Don Melton’s time today. It all started with his post regarding the switch to Nanoc from WordPress. I admit I have been thinking about switching to a static site generator for years now, but I never could justify spending the time to do so. Anyway, I was teasing Don about his CSS in IE problems…
Continue reading →
The past few years have seen a dramatic improvement in display technology. First it was the upgrade to higher-resolution screens, starting with mobile devices and then desktops and laptops. Web developers had to understand high-DPI and know how to implement page designs that used this extra resolution. The next revolutionary improvement in displays is happening now: better color reproduction. Here I’ll explain what that means, and how you, the Web developer, can detect such displays and provide a better experience for your users.
This will seem a hassle until multiple profiles can be included in one image. I can see only photographers caring for this in the meantime. But it’s great that this is finally coming to the web.