Microsoft Edge is Microsofts replacement for Internet Explorer. We all know this, it isn’t surprising at all. Anyway, ever since Microsoft released Project Spartan in the wild back in April 2015, they released 45 updates to it. You know what else got 45 updates since that day? Windows itself. Dhu. Windows and Microsoft Edge are being developed in parallel and if and only if one gets an update, so does the other.
And so far, that works just fine. Since its original release on July 29, Edge has seen 1 update and is about to see another one. And sure, browsers like Chrome and Firefox release almost 9 version each year, but let’s face it: that is ridiculous. There is absolutely no need for such a fast cadence. Edge’s 2-a-year is fine. The fact that it is tied to Windows… not so much.
Edge rolls out new feature updates to the general public every time Windows gets updated. That has happened with Threshold 2, and it will happen again with Redstone 1. And again with Redstone 2. The only problem with Redstone 2 is, if the rumors are right, we won’t see Edge 15 until early next year. Somewhere in Spring. You know, March – April – May 2017. That’s too long.
So here I am hoping for one last big change to Edge 14: cutting its ties to Windows. Make it possible for Edge to get updated beyond fixes and security enhancements on a stable release of Windows, because the update scheme is fine if Windows can keep up with a 2-a-year release, but that’s is (sadly) not the case.
I’m not saying that we should get a new update every month (or 6 weeks) but it should be possible to test new versions of Edge during the Redstone 2 Insider Previews and roll Edge 15 out to the Current Branch (first passing through the Preview Release Ring, of course) to what will become the Anniversary Update somewhere at the end of this year and have Edge 16 launch with the Redstone 2 release in 2017.
We can wait for an update to Edge. Just not that long.