Microsoft Is Embracing Chromium, Bringing Edge To Windows 7, Windows 8, and Mac 139
An anonymous reader writes: Microsoft today embraced Google's Chromium open source project for Edge development on the desktop. The company also announced Edge is coming to all supported versions of Windows and to macOS. Microsoft wants to make some big changes, which it says will happen "over the next year or so." The first preview builds of the Chromium-powered Edge will arrive in early 2019, according to Microsoft.
And yes, this means Chrome extension support.
And yes, this means Chrome extension support.
As a Win7 user (Score:1)
Re: As a Win7 user (Score:2)
As a Linux user, I can't fathom why MS would support a dead platform like Windows 7 but not RHEL or Ubuntu.
Re: As a Win7 user (Score:2)
I have a Windows 10 laptop that I have used Edge on, I just spend most of my time in KDE and Android. So I'm less likely to use a technology that doesn't work on all my platforms.
Support for Windows 7 ends in January, 2020 so developing for a platform that will have less than a year until EOL seems counterproductive.
Developers are more likely to test their webapps in Edge if they can run it on their development machine. Surely there's a Windows 10 engineer at MS that sees the value in getting its GUI workin
Re: (Score:1)
If the original Edge didn't sway people from using Internet Explorer, this new Chromium-powered version isn't going to do any better. You have two camps of Windows web users:
Microsoft switching rendering engines doesn't affect those in camp #2, so until there's a concerted effort to get everyone off of IE11, we're going to be stuck writing
A chromium based browser to download a chromium... (Score:2)
Re: (Score:3)
...based browser? So it will download Chrome even faster or/and it will periodically set itself as the default browser?
I think they're hoping "why would anyone download Chrome if they have the same thing in different colour paper with our product?"
Re: (Score:2)
I would assume that the browsers would be competing against features (the stuff outside the actual web page)
Things like developer debugging tools, handling hot keys and bookmarks.
Re: (Score:3)
Because Microsoft will support it. Ticking the "Vendor support agreement" box is a requirement for a PHB signoff
Re: (Score:2)
Re: (Score:1)
Re: A chromium based browser to download a chromiu (Score:2)
Privacy would be the obvious selling point.
Re: (Score:1)
Re: A chromium based browser to download a chromi (Score:2)
Are YOU joking? MS sells software. They are giving you ads. And they don't even do that if unless you use the cheap ad-subsidized home version. That's not really related to privacy and demonstrates nothing about how MS operates.
Privacy is a problem with a few types of companies: advertisers who profit from your personal data, smash and grab service providers who develop minimal products which they support with ads, failing companies trying to trump up revenue by selling lists, and companies with incompetent
Re: (Score:1)
Re: (Score:2)
It's not google. Therefore likely less spyware.
Re:A chromium based browser to download a chromium (Score:5, Insightful)
Nice try. But, now that they've announced versions for Windows 7 and Mac, it's pretty obvious that, in addition to not wanting to spend development resources on a redundant browser engine, they're real goal is to get Edge telemetry onto non Windows 10 boxes. So if you want to get rid of spyware, you're gonna have to use vanilla Chromium.
I guess if desktop Linux were a factor, they'd be 'porting' it there too - but (much as they 'love' Linux these days) they're still not fond of the idea of desktop Linux as a viable competitor to Windows.
Re: (Score:3)
Are you aware that Win10 telemetry was pushed on win7 via updates something like a year ago? It makes no sense to fuck themselves over as anyone who doesn't care about telemetry already has it installed.
Re: (Score:1)
Re: (Score:2)
It's both. The purposes are not mutually exclusive.
Re: (Score:2)
You put the cart before the horse. This is a story about edge coming to win7 and win8. Both of which can simply not install telemetry, as on both operating systems, user has full control over updates.
It therefore makes little sense for MS to put additional spyware to the similar tune as google into their version of Chromium. Those who don't care about spyware on win7 and win8 already installed it via windows update. There's no benefit in having second layer of spyware for these users.
There's only benefit if
Re: (Score:2)
I never had a desire to use Edge, but do use Chrome from time to time as a secondary browser, and would love to have an option not from Google. I'll probably switch to using Edge for secondary browsing unless I encounter some major issue.
Re: (Score:2)
Good point (Score:1)
Probably will evaluate Chromium also, I honestly had not heard there was a standalone Google-free variant.
Re: (Score:2)
You also have to deal with software certification for governmental organizations and other certain industries. Chrome may not be on the list, but Microsoft's browsers almost universally are if Windows is the desktop OS of ch
Re: (Score:2)
I
Re: (Score:1)
Re: (Score:1)
google is still tracking u buddy. whether u use Google services or not
Google is not tracking me. I have all of their domains and ASN blacklisted. Their universal presence on other websites is a NOOP. I'm happy with startpage.
Re: (Score:2)
I despise Google and try to avoid them as much as possible, but unfortunately there's a few domains of theirs that there's no getting away from...
namely, GoogleApi, Google Captcha, their cdn, as well as arguably the products: Maps and YouTube.
Without some of those domains, a large portion of websites would be broken, including many of those that require authentication using Captcha.
How do you possibly get around that?!
Standards Compliant Finally (Score:2)
Is this a repeat or just an old story?
Either way- my thoughts on this are the same as they were back when I first heard about this: excellent news for web developers. It's about time Microsoft had a standards-compliant browser so we don't have to have two sets of code; one for Microsoft, and one for everyone else.
Re: (Score:3)
Re:Standards Compliant Finally (Score:5, Insightful)
Please. IE6 broke every standard it could (although IE5.5, for macs, was remarkably compliant.) They started adhering to more standards as it went through 7, 8 and 9 (the most standard uncompliant thing in 9 was websites could include tags that said "render this like you were IE6, 7 or 8") By 11 I'm not aware of any issues, and Edge was designed to the specification. I recall MS would proudly pointing to stupid edge cases it didn't comply, show how no one did, and explain why complying would cause major issues.
Meanwhile, Chrome has been becoming more and more like IE6, inventing new optional add-ons, and doing its own EEE to the free webstandards. Meanwhile, Google has been downranking pages that don't use their EEE "features" to force websites to integrate them. It's at least as evil as MS wanting to own the browser on PCs, because at least then it just would render the page slightly off if you didn't buy into the monopolist's browser. Now, you (essentially) don't exist, cause you're on page 103 of the search results.
Are you stuck in 2014? (Score:2)
Chrome hasn't done that for a long time.
There are still plugins available to have backspace go to the previous page, for those who want that.
Re: (Score:1)
Re: Standards Compliant Finally (Score:2)
This is your boss. I use IE 8 because html 5 is too scary and am too cheap to upgrade our crm. Your website looks funny on my computer.
Can you fix by tomorrow morning? Thanks
Re: (Score:1)
Yes there may be some things that Edge doesn't support, but one could cherry-pick features that any given browser doesn't support.
Re:Standards Compliant Finally (Score:5, Insightful)
It's about time Microsoft had a standards-compliant browser so we don't have to have two sets of code; one for Microsoft, and one for everyone else.
Well, there are a couple issues I can see.
1) Monocultures are generally a bad idea, and this is moving us further down the road towards a web monoculture. I'd rather Microsoft work harder to implement standards compliance in their existing rendering engine.
2) Google seems to be doing the same thing Microsoft did 10-15 years ago - trying to push people into adopt Chrome-optimized web sites and Google-specific coding. I hated it when Microsoft did it, and I hate it now.
Re: (Score:2)
I'm aware of 0 non-standard rendering issues in IE11 or Edge. Also, as far as I know, Edge has fewer non-standard JS issues than Chrome.
Re: (Score:2)
2) Google seems to be doing the same thing Microsoft did 10-15 years ago - trying to push people into adopt Chrome-optimized web sites and Google-specific coding. I hated it when Microsoft did it, and I hate it now.
The big problem here is that websites can only barely be bothered to test with a single browser, and rolling out standards strong enough to count on is hard hard hard work, so the ground truth is that websites routinely rely on browser-specific behaviour without even knowing it. At the user level, figuring out why a site doesn't work is basically impossible, so you just switch browsers until one works well enough then you stop. Together, these mean that it is extremely hard to have a browser with a render
Re: (Score:2)
But should Standards Compliant be based off the same code set?
There is often more then one way to code a product and still follow the same standards, some features will run faster then others, others may be sacrificed. A newer build would be based on current browsing habits vs older ones. Also this could mean greater security issues, as there will be mostly a unified browser engine across all the major browsers, so with the same code set behind it, a flaw will have more of a universal problem.
Re: (Score:2)
But should Standards Compliant be based off the same code set?
There is often more then one way to code a product and still follow the same standards, some features will run faster then others, others may be sacrificed. A newer build would be based on current browsing habits vs older ones. Also this could mean greater security issues, as there will be mostly a unified browser engine across all the major browsers, so with the same code set behind it, a flaw will have more of a universal problem.
I'll give you that. It would be better if Microsoft managed Standards Compliance on their own and had a separate source and perhaps different vulnerabilities to make a hack one place not work everywhere.
They tried to be standard with Edge, and it was an improvement, but there were still a few issues. (Edge is much closer to where MS needed to be though).
Re: (Score:1)
That would be nice, but Microsoft switching browser code doesn't magically make IE11 and his older siblings go away. God, I wish it had. Edge was a great step toward standards compliance; any CSS I write for Firefox renders perfectly in Chrome, Safari, and Edge. Edge is even up there with supporting CSS grid. But we still have dinosaurs that use Windows 7 and 8 and don't know how to download and run a new browser. That "e" with the swoosh on their desktop stands for "eeenternet" so they can log into Yahoo M
Re: (Score:2)
That would be nice, but Microsoft switching browser code doesn't magically make IE11 and his older siblings go away. God, I wish it had. Edge was a great step toward standards compliance; any CSS I write for Firefox renders perfectly in Chrome, Safari, and Edge. Edge is even up there with supporting CSS grid. But we still have dinosaurs that use Windows 7 and 8 and don't know how to download and run a new browser. That "e" with the swoosh on their desktop stands for "eeenternet" so they can log into Yahoo Mail and send their family FWDs about Russian models being better immigrants than Mexican welfare babies.
As a web designer, I'm ambivalent about this. Maybe Microsoft can contribute something worthwhile to the Chromium project.
CSS works great on Edge. I still see differences in how Microsoft handles JavaScript compared to the other browsers.
SPDY is HTTP/2 (Score:3)
remember Chrome implements a bunch of standards like SPDY (Google-only extension)
I thought SPDY had been standardized as HTTP/2. Do you refer to old draft versions of the protocol that should have been phased out by now?
and enforcing https on .dev
The owner of any top-level domain can set HSTS preload guidelines for that domain.
except what if I'm not on the public internet?
Use an explicitly reserved TLD, not a TLD that someone else owns. For multicast DNS, use .local; for static allocation on a private DNS server, use .internal.
Re: (Score:1)
> Do you refer to old draft versions of the protocol that should have been phased out by now?
Who created and implemented those drafts? Do you think that if HTTP/2 wasn't close to SPDY, that Google wouldn't have effectively enforced it? It was at a time when Google didn't have the control it, well, now has. So back then, what other browsers did actually sort of mattered.
Now? Whatever.
> except what if I'm not on the public internet?
You completely misunderstood what I meant by "not on the public inte
Firefox also warns "Connection Is Not Secure" (Score:2)
Who created and implemented those drafts [of HTTP/2]?
Google. But who should have created and implemented them, if not Google?
As I understand it, the .dev constraint is enforced in chrome's source code, not in any DNS record
The same is true of other ICANNverse domain names whose owners have set the HSTS preload bit [hstspreload.org]. If you were to create a site called google.com in your air-gapped private parallel internet, the major browsers would force HTTPS on that as well.
Who do you think will define HTML5? It isn't going to be W3C. Or Google saying all http is 'not secure'
"Secure Contexts", a policy to block JavaScript from doing sensitive things on cleartext HTTP sites, is in fact a W3C Candidate Recommendation [w3.org]. Besides, Firefox has similar behavior. Visit some random [explosm.net]
Re: (Score:2)
Hmmmm ... It does not look like Edge is more compliant.
https://html5test.com/results/... [html5test.com]
Adblocking (Score:5, Insightful)
Re: (Score:2)
Adblocking their approved ads in their OS?
Re: (Score:2)
Adblocking is fine until you find that half the results of a typical Google sear...
This is a free preview.
To read the entire comment, log in [slashdot.org] or subscribe [slashdot.org] to comments by tepples
Re:Adblocking (Score:4, Informative)
Oh, goody. (Score:2)
Re: Oh, goody. (Score:2)
I think Apple might have something to say about that
Re: (Score:3)
What do you think Safari is based on?
Re: (Score:3)
WOW. Can't believe I brain-farted that bad. I must need more coffee
Re: (Score:2)
Yes I know Blink is a fork of WebKit, and WebKit is a fork of KHTML.
Comment removed (Score:5, Informative)
Re: (Score:3)
Mr. Fusion?
Re: (Score:2)
I'm going to assume you have the came combination on your luggage as me.
Re: (Score:2)
KDE Konqueror.
KHTML (Konqueror) was first. Apple forked that to make Webkit. Google initially used Webkit and then forked Webkit to make Blink.
Blink powers Chrome/Chromium, Opera, and the future versions of Edge. It's based upon Webkit.
Webkit powers Safari. It's based on KHTML.
KHTML powers Konqueror. It's something the KDE team hacked together from chewing gum, old razor blades, and discarded coffee grinds.
Discarded coffee grinds powers Mr Coffee. They're based on coffee beans.
You see where this is going.
So all the browsers are java-based?
Re: (Score:2)
Konqueror has more or less been superseded by Falkon - a browser based on Chromium?
Re: Oh, goody. (Score:2)
Not Blink
Re: Oh, goody. (Score:2)
Gecko still has like 16% market share, so the dominance is not nearly so complete as IE/Trident back in the day.
Re: (Score:2)
Yet another reskinned Chrome, can never have enough of those. It wasn't even 5 years ago when we had a healthy selection of browser engines, some of them even web standards compliant. Now Chromium/Chrome devoured the entire market, and Google has final say on how the web is rendered.
Well, despite Firefox trying to continuously look like Chrome, it isn't Chrome powered.
Yet.
Re: (Score:3)
The problem with IE/Trident was that it was closed source -- and worse, Windows-only. Blink is easily forked if Google does anything bad with it, as proved by KTML being forked into Webkit being forked into Blink.
The great thing about Microsoft switching Edge to Chromium is that web developers no longer need to keep a copy of Windows around to check.
MS platform compatibility solved by Google (Score:2)
I think it's hilarious that by switching to Google technology, MS's new software will run on more MS platforms.
Re: (Score:2)
Slowing innovation?? (Score:2)
Re: (Score:2)
It's speeding "innovation", that is, the ability of Google to supplant W3C as the maintainers of HTML5+, allowing them to add lots more support for ads and tracking.
It is going to kill competition, for the same reason that IE6 killed competition - there will be no spec to write to (or the Chromium implementation will differ from the spec), so you'll have to use the supplied engine or GTFO.
Edge on Windows 7 (Score:2)
Yayyyyy ... Just what I haven't been waiting for. [ shoots self in head ]
What about Windows XP (Score:5, Funny)
Re: (Score:2)
hell no (Score:2)
C'mon MS, leave OSX out of it, go screw with the other platforms.
Comment removed (Score:3)
Re: (Score:1)
Edge was a ground-up rewrite.
Re: (Score:3)
Lynx (Score:1)
Seriously... it's all you need.
SO: Microsoft is pushing Edge over the ... (Score:5, Funny)
IE11 still used (Score:2)
There are 2 use cases where I still need to use IE11: .docx file and edits it locally. I'm sure Slashdot will poo-poo this but it is super useful. If they push Chromium, they ought to make an extension so that th
1) Windows IoT and Windows Server. For reasons I don't understand, Microsoft does not ship Edge onto those OS editions.
2) Office integration. If you put a Microsoft Office document onto a Sharepoint or OneDrive site, using IE11 gives you the integration. On other browsers, it just downloads the
Re: (Score:2)
My kids use IE11 for that as well. Just make sure you "End Task" on iexplore.exe and on the Flash player EXEs because they don't exit cleanly. And make sure that you don't visit any place sketchy because Flash has so many security holes.
For the sake of browser diversity (Score:5, Insightful)
Re: (Score:1)
What's the point in that? If chromium goes evil simply fork the code and carry on - hardly difficult and you could even do it yourself if you had the time (which ms probably has lots of)
Business as usual (Score:2)
Embrace Extend Extinguish
Market opening (Score:1)
It's a good thing. (Score:1)
At first glance, I'd say this is a bad thing because it reduces competition, but since Microsoft Edge is a Windows 10-only browser, it's probably a good thing; developers eventually won't need to code for a Windows-specific browser unless Microsoft forks the rendering engine.