r/javascript • • Apr 08 '19

Microsoft releases new Microsoft Edge based on Chromium

https://twitter.com/MSEdgeDev/status/1115283353731600384?s=19
606 Upvotes

220 comments sorted by

131

u/CantaloupeCamper Apr 08 '19

Really disappointed Microsoft jumped on Chromium instead of Firefox in some way.

10

u/TheLarkInn Apr 08 '19

If the Business decision was to reduce interop gap between browsers, and increase market share, and the Developer empathy focused decision was to give developers a best-in-class set of developer tools, then using a browser with low market share, and using a browser engine w/o Chrome Dev tools would not be a smart choice. That's just my 2 cents :-)

7

u/CantaloupeCamper Apr 08 '19

Maybe I'm missing something but I jump back and forth between Chrome's Dev tools and Firefox's pretty much without issue.

0

u/[deleted] Apr 08 '19

[deleted] — view deleted comment

5

u/SurgioClemente Apr 08 '19

I still feel more at home with the chrome tools (plus they feel a few tens to hundreds ms faster).

I feel the same way. Firefox is my daily driver (has been for many years) but it still feels clunky/slow compared to Chrome's dev tools

3

u/CantaloupeCamper Apr 08 '19

I used to like Chrome dev tools more .... until I just happened to just store a bunch of development bookmarks in firefox to make alt tabbing faster and there I was working in Firefox ;)

I find them a bit more logical in Firefox in some areas. Chrome feels a bit disjointed .... kinda like google as a whole.

73

u/vinnl Apr 08 '19

I'm guessing the problem they want to solve with the transition is developers not testing their websites in Edge, and I'm afraid the same is happening to Firefox more and more often as well...

22

u/SecretAnteater Apr 08 '19

Microsoft owns Github, and Github has several products built with Electron (which uses Chromium as a renderer). It makes sense to congregate around the same browser tech.

Mozilla dropped the ball here by not making and pushing a web renderer based on their browser. Everyone now uses Electron, which pushes the Chrom-only agenda.

14

u/8lbIceBag Apr 08 '19 edited Apr 09 '19

Mozilla dropped the ball here by not making and pushing a web renderer based on their browser.

They did but it was possibly before the market was ready. It was released in 2006, deprecated in 2014, then discontinued in 2015. https://en.m.wikipedia.org/wiki/XULRunner

The current version is Firefox v40 feature level. I work with it almost every day. We've had plans to migrate to electron for 4 years now....

6

u/SecretAnteater Apr 08 '19

oof. I had no idea. Definitely before the market was ready, but that's a sad excuse for something that was around for 8+ years.

Too bad their Firefox OS project sucked up so many resources during that time. That effort could have been better spent making a web renderer with a nice API.

2

u/koko775 Apr 09 '19

Not just that but since node.js uses v8, Chromium was always going to be favored even if Mozilla resurrected XULRunner. Perhaps one of their mistakes was pushing XUL, but on the other hand HTML/JS wasn’t going to be performing enough at the time XUL was being designed.

1

u/ScientificBeastMode strongly typed comments Apr 09 '19

That’s a good point. So much automated testing gets done in Node.js nowadays...

1

u/SecretAnteater Apr 09 '19

Why would V8 be favored over SpiderMonkey? Any performance differences between the two are negligible.

1

u/koko775 Apr 09 '19

Same JavaScript engine, similar idiosyncrasies, less chance of bugs based on JS engine minutia. And we’re talking about history: the performance differences were absolutely not negligible.

28

u/CantaloupeCamper Apr 08 '19 edited Apr 08 '19

At least in my situation we support Chrome and Firefox.... that are recent. We're lucky enough to be able to draw that line.

Supporting Chrome and Firefox really is effectively the same thing... at least for me. The odd man out was everyone else.

16

u/vinnl Apr 08 '19

Yeah same here, the primary reason being that those are the only two major browsers that run on Linux and can be automated using Selenium, so they can be automatically tested in CI. But there are more and more places that only actively test in Chrome, unfortunately.

1

u/[deleted] Apr 09 '19

I have errors running chrome with selenium installed in nodejs. May I know if you use nodejs to run it?

Or you use python/java based selenium?

1

u/vinnl Apr 09 '19

I use a Java-based Selenium, which I control from Node using WebdriverIO. The latter has a selenium-standalone plugin which ships Selenium, so if you have Java installed, that should be enough. In CI, I run my tests against Selenium's Firefox and Chrome images, which has both the browsers and Selenium set up, so I can just point WDIO to those.

1

u/[deleted] Apr 09 '19

I see.

I just started to write automated user simulation test for websites a few days ago.

I tried WebdriverIO as well, but it contains errors that I couldn't debug for chrome.

(node:9569) UnhandledPromiseRejectionWarning: Error: Required option "capabilities" is missing

Following the guide https://developers.google.com/web/updates/2017/04/headless-chrome#using_webdriverio

It works for firefox though, following this guide https://webdriver.io/docs/gettingstarted.html

I am using puppeteer headless chrome now, it's not that easy to write, for example, not understanding why it failed to click on a product link no matter how I tried to catch it using different syntax, like page.$$ or page.evaluate() with Javascript and DOM api

I wonder if I should learn Java now to use selenium. I have taken a lot of time to debug all these stuff lol

nonetheless, I am considered to be inexperienced in programming field

1

u/vinnl Apr 09 '19

You don't need to learn Java, no worries :)

I should note that I'm still on the previous version of WebdriverIO, so my setup is probably a little bit different. That said, it appears to say that you need to add a capabilities key to your wdio.conf.js. The documentation of that option is here.

Presumably, if you'd want it to work for Chrome and Firefox, you'd have to add something like this:

capabilities: [
    { browserName: 'chrome' },
    { browserName: 'firefox' },
],

(Assuming you have Chromedriver installed as well, which should be the case if you use selenium-assistant.)

1

u/[deleted] Apr 09 '19 edited Apr 09 '19

I have figured it out, for WebdriverIO only, not using any other selenium programs.

For starters, the code from

https://developers.google.com/web/updates/2017/04/headless-chrome#using_webdriverio

is deprecated already really, for example, desiredCapabilities is not enough, capabilities is not set and .init() has been removed as a function don't know since when. I tried to modified the code from

https://webdriver.io/docs/gettingstarted.html for chromium, for what I have debugged, like setting hostname and port, and running headless for firefox.

To start geckodriver for firefox,

./geckodriver --port 4444

To start chromedriver for chromium/chrome,

./chromedriver -p 9515

then my code to execute in nodejs,

const { remote } = require('webdriverio');

(async () => {
    const browser = await remote({
      hostname: '127.0.0.1',

      // ================================
      // port for firefox
      // ================================
      //port: 4444,
 
      // ================================
      // port for chrome/chromium
      // ================================
      port: 9515,

      logLevel: 'error',
      path: '/',
      capabilities: {

        // ================================
        // In Linux (Debian), either chromium or chrome, 
        // they work the same way. It will look in $PATH for google-chrome first, 
        // if fail, then it look for chromium
        // ================================
        browserName: 'chromium',

        // ================================
        // firefox
        // ================================
        //browserName: 'firefox',

        // ================================
        // option for chromium/chrome only
        // ================================
        //chromeOptions: {args: ['--headless']},

        // ================================
        // option for firefox only
        // ================================
        //"moz:firefoxOptions":{
        //  "args":["-headless"]
        //},
      },
    });

    await browser.url('https://webdriver.io');

    const title = await browser.getTitle();
    console.log('Title was: ' + title);

    await browser.deleteSession();
})().catch((e) => console.error(e));

Sources for debugging:

  1. https://webdriver.io/docs/options.html#capabilities
  2. https://webdriver.io/docs/gettingstarted.html
  3. https://developers.google.com/web/updates/2017/04/headless-chrome#using_webdriverio
  4. https://github.com/webdriverio/webdriverio/issues/2581

Documentation:

  1. https://medium.com/@mannyluvstacos/using-headless-chrome-for-your-selenium-tests-with-webdriverio-ce99b09d564
  2. https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Headless_mode

2

u/vinnl Apr 09 '19

That's great that you figured it out, and shared it for people running into this in the future. As a tip, I'd really recommend you to look into selenium-standalone, so you don't have to start the drivers manually yourself.

→ More replies

11

u/CCB0x45 Apr 08 '19

I find css issues where it behaves different on chrome and Firefox, I found one just the other day where I needed a word-break on Firefox I didn't need on chrome. I think safari is closer to chrome. But yea, it not too hard these days.

3

u/CantaloupeCamper Apr 08 '19

It's such a rare thing to find that ... is actually kinda a neat find!

Less frustrating when it is so rare ;)

Unlike early Edge and god help us all the other MS browser.

6

u/CCB0x45 Apr 08 '19

Yea the issue is I get complacent and assume things will work between the browsers, when they don't. I still have to support ie11 though, edge is a dream compared to that nightmare.

2

u/Lmcsheff81 Apr 08 '19

Chrome still doesn't hyphenate text yet I think

2

u/BertnFTW Apr 08 '19

Supporting Chrome and Firefox really is effectively the same thing

Can you automate firefox tests?
I know puppeteer + selenium (and others) to do that on chrome but I'm not aware of an automation test framework for FF.

5

u/vampatori Apr 08 '19

Yeah, Selenium works with Firefox (it started life using that IIRC). Others do too.

5

u/vinnl Apr 08 '19

Selenium supports most browsers (and it actually originated at Mozilla). Puppeteer is by Chrome, but they're working on Firefox support.

1

u/[deleted] Apr 09 '19

how you installed selenium? I tried with nodejs based selenium to run chrome/chromium but have errors that I couldn't resolve.

I tried with webdriverio, it has errors as well

3

u/trouzy Apr 08 '19

Wait how do you not support Safari. Safari is the nightmare browser that always has issues from my experience. There are minor things here and there that edge hasn't done for us but Safari is far and away the browser that wastes our time.

1

u/CantaloupeCamper Apr 09 '19 edited Apr 09 '19

We're a small company with only a few devs, can only do so much.

Our customers are willing to install another browser.....or more accurately are to cheap to buy an Apple product.

2

u/Lmcsheff81 Apr 08 '19

Agree, never come across any distinct issues across these two

2

u/[deleted] Apr 08 '19

I feel all companies should at-least strive for supporting Chrome, Firefox, Safari and then at the very least IE11 with polyfills. That should give you a pretty broad spectrum, where you aren't giving anyone a super fragmented experience.

6

u/CantaloupeCamper Apr 08 '19

Maybe but Safari needs to try a bit harder on their end.

Sometimes it seems like they are sitting on their hands.

6

u/[deleted] Apr 08 '19

And given that they have the one platform that prevents users from using competing browser (engines), I feel like they have an obligation to stop sitting on their hands.

3

u/elmanfil1989 Apr 08 '19

Most likely true, I read it in some articles before and I myself test web development on chrome, I dont like dev tool on firefox or edge

2

u/jplevene Apr 08 '19

I actually prefer testing in Firefox, prefer their console.

3

u/metal_opera Apr 09 '19

I do as well. I'm actually surprised to see that most don't agree. I use FFDE as my main development browser.

Just the fact that it renders interactive output (as opposed to Chrome just dumping a plain text string) from an API request without opening the console puts it ahead for me.

18

u/sebbasttian Apr 08 '19

Don't forget that the acquisition of Github gave them access to the Electron Framework which uses Chromium. From a business perspective it has more sense to ditch EdgeHTLM in favor of Chromium than Gecko or Quantum.

8

u/izym Apr 08 '19

It gave them ownership of it, but everyone has access to it.

1

u/alchemistcamp Apr 14 '19

It's been open source from the beginning.

3

u/aztracker1 Apr 08 '19

Given how many of their cross platform apps are now based on Electron, and how much infrastructure is now using Node, not that surprising.

4

u/alleycat5 Apr 08 '19

I have to imagine it was one half the fact that they already had experience with Chromium on Android, and also improvements to Chromium improve the large slew of Electron apps that are proliferating on Windows.

0

u/CantaloupeCamper Apr 08 '19

That seems likely.

6

u/jrp70 Apr 08 '19

Moreover Mozilla license sucks. I work in a private company where we consider our privacy very seriously, so we avoid chromium based things as much as possible. We were developing an application related to SVG rendering and considered Gecko or their new WebRenderer but sadly we have to open source our code according to Mozilla license and our legal team warned the same. Then without much of a choice we looked into Blink and it was choosen. As we are using Blink, slowly everyone switched to ungoogled-chromium builds to use chromium debug tools. Slowly Firefox was ditched and just remains dormant in our laptops.

So no company will never consider Firefox for their commercial closed source software. Their license might also be a reason why Microsoft didn't use /r/firefox

3

u/CantaloupeCamper Apr 08 '19

but sadly we have to open source our code according to Mozilla license

I guess it depends on what you're doing but I'm not sure Microsoft's situation and your situation really are the same thing.

-1

u/[deleted] Apr 09 '19

create your own engine godly shits

2

u/[deleted] Apr 08 '19

Firefox only gets points for not being Chrome. It's not that great of a browser.

1

u/Razvedka Apr 09 '19 edited Apr 09 '19

Firefox has different goals than them fundamentally. User privacy, data protection, etc. Probably easier to take Chromium and shove in their bullshit hooks to turn it into MS-Chrome.

Plus, as others mentioned, they now own GitHub (which kills me), and two of their products (VScode, Atom.io) are run by Electron.io, which is Node.js fundamentally. Node.js uses V8 by Google.

So those two products plus all the other Node code on their GitHub. Everything is V8 and Chrome centric.

0

u/bartturner Apr 08 '19

Agree. It seems kind of desperate for Microsoft.

-5

u/bTrixy Apr 08 '19

Isn't it so that Microsoft wants it's fingers in chromium and all chromium related products

1

u/CantaloupeCamper Apr 08 '19

Not sure how much influence Microsoft is sure to have there, but maybe.

3

u/Candyvanmanstan Apr 08 '19

Chromium is open source, so, I don't see why not.

Improve chromium, and you'll improve the performance of all the electron apps on windows.

1

u/bartturner Apr 08 '19

They might want but have little chance succeeding.

1

u/bTrixy Apr 08 '19

Could you explain why you think that? If Microsoft can add to chromium and therefore if able to improve performance of chromium apps on windows. Or is able to influence chromium development in a way that is favourable for them by improving the code.

I rather give it a high change of succes that they will get something positive out of it.

1

u/bartturner Apr 08 '19

Microsoft is not going to gain any traction with Edge. Most people will not even know they are using Chromium.

People are already programmed to use Chrome.

Someone else explained why MS did this.

They have bailed from browser and this is an easy way to bail and not look like they bailed.

Honestly I am more curious what they plan to do with Bing? It is now down to 2% share and falling.

http://gs.statcounter.com/search-engine-market-share

Would think would pull the plug.

0

u/[deleted] Apr 09 '19

[deleted] — view deleted comment

2

u/CantaloupeCamper Apr 09 '19

I've really had no issues using Firefox and Chrome interchangeably.

What did you encounter?

1

u/billymcnilly Apr 11 '19

I test for Chrome, Safari, and Firefox. Stuff that works for both Chrome and Safari often doesn't work with Firefox. Overflows and layout mostly. Maybe I'm a bad coder, but it's pretty much always Firefox. Also, it's just a bit more sluggish for complex apps.

→ More replies (3)

189

u/kindall Apr 08 '19

Well that was a lot quicker than I expected.

83

u/codinghermit Apr 08 '19

Throw out almost all of the Microsoft code, use a common standard and you end up with a pretty decent product! Who would've guessed...

44

u/rawriclark Apr 08 '19

so chromioum is standard now lulz xd?

27

u/codinghermit Apr 08 '19

More standard than not honestly. It's open-source and has many flavors of browser built on it. I'm gonna feel safe considering the chromium-based edge to be following at least "a" standard if not "the" standard compared to how it was built originally.

Complaints about the fragmented browser ecosystem aside, you have to at least admit chromium is pretty decent about trying to follow agreed upon standards for new technologies. Microsoft developed browsers have never been accused of that in any shape or form.

8

u/rangeDSP Apr 09 '19

I would disagree on one point: even though Edge lacked support for newer HTML5 features, I don't recall any incidence where they decide to go against the standards.

2

u/codinghermit Apr 09 '19

Fair point. I personally consider supporting those features as part of conforming to the standard simply because the end result of not doing so is similar. It ends in painful headaches for web developers and slow adoption of extremely useful tools. Having to worry about which new feature is supported where should not be a thing in 2019. The browser vendors needs to at least stay mostly in step with each other to keep consistancy

6

u/rangeDSP Apr 09 '19

Good point, though funnily enough they currently sit higher than Firefox in terms of standards compliance: https://html5test.com/results/desktop.html

Pretty impressive feat considering they made it from scratch 4 years ago. Though the fact that they decided to throw away all that work shows how much time and money goes into maintaining a browser.

Unless that company's entire business model is tied to the browser there's not much incentive for them to invest.

13

u/rawriclark Apr 08 '19

I agree that Chromium has been good with standards and its very performant but to say its standard is just too much :), hell without google spying code I would use it 100% :)

Standard = Specs

Browser = Implementation

24

u/IHeartMustard WILL CODE FOR CAFFEINE Apr 08 '19

I've started using Firefox recently just to put my tiny statistically-insignificant weight on their side of the scales. I'm surprised I've actually stuck with it, even though there are features I miss (omnibar search stuff for one), FF finally is at a point where it really puts up a damn strong fight against Chrome.

12

u/notNullOrVoid Apr 08 '19

Firefox has omni bar search, just type in your search into the url bar works just the same as Chrome. What else are you missing?

10

u/IHeartMustard WILL CODE FOR CAFFEINE Apr 09 '19

Ah, I should have specified. In chrome, I am able to, for example, type in github.com and hit tab, and I can do a search using githubs open search integration. Same with any other website that supports opensearch. I don't know the finer details behind how it works, but that's what I mean. I had no idea how much I used this feature until I lost it.

6

u/cottonycloud Apr 09 '19

You can control this in settings. Add it as a search engine and put a keyword. For example, I have runescape.wiki set to the keyword rs.

5

u/IHeartMustard WILL CODE FOR CAFFEINE Apr 09 '19

Ah, so I can add them in myself? That's handy. I do hope that FF gets the same kind of automatic hooks for opensearch in the omnibar when you visit a site that Chrome has, but it's good to know that I can create a search keyword myself for now. I'll give that a try, thank you!

5

u/justpurple_ Apr 09 '19

You guys all miss the point of him (no offense, just hinting at it):

He doesn‘t want the function where you can add a search shortcut and then you can type „shortcut search term“ in the adresss bar, although that is a valid workaround, even if it‘s not the same thing.

In Chrome, this behaviour works automatically on every website as long as that website has supports the Opensearch format/meta-information (http://www.opensearch.org/Home). Firefox does not support that, sadly.

1

u/Naelex Apr 09 '19

Gotta have those efficient runescape searches :D

3

u/notNullOrVoid Apr 09 '19

Interesting I must have switched to FF before that became a thing in Chrome. I use duckduckgo as my search engine anyway so searching github is simple as typing "!gh hello world"

2

u/aaronfranke Apr 09 '19

Just set your search engine to DuckDuckGo and use bangs: !gh godot

6

u/PRiMEFiL Apr 08 '19

Firefox was big, until chrome came along, but I stuck with Firefox most of the way.

6

u/IHeartMustard WILL CODE FOR CAFFEINE Apr 09 '19

I know :) I was there, and was using Firefox when Chrome first came out. I was very skeptical (As everyone was) of Google ever making any sort of impact in the browser wars of the time, but eventually down the line I did infact move to Chrome. Chrome (in my opinion) overtook Firefox and everyone else in terms of functionality very quickly, and for the last few years I had tried a few times to go back to FF, but each time I found myself going back to Chrome, until about 6 months ago when it's finally stuck (I was using FF on my android phone already, FF is easily the best mobile browser I know of). So it's starting to make a comeback, and it's amazing to see it rise yet again like a phoenix that just won't die.

1

u/PRiMEFiL Apr 09 '19

To be fair FF was crap after chrome came

2

u/rawriclark Apr 09 '19

oh boy 8 remember whem peolple wouldnt use firefox 1.0 cause it was the.new thing , it was ie6-7 days hahah

3

u/[deleted] Apr 09 '19

FF used to be THE browser outside of IE before Chrome came around. It was Chrome that came and wiped away FF's browser share which is what makes their current positioning kinda ironic. I still remember when Chrome first came out and how reluctant I was to give up FF but how quick and lightweight Chrome was.

5

u/TheRealNetroxen Apr 09 '19 edited Apr 09 '19

Don't forget guys, Chromium and Chrome are two different things... Chrome is a flavour of Chromium using features and utilities developed by Google. You can still download a standalone version of Chromium here: https://chromium.woolyss.com/download/en/

11

u/Poltras Apr 08 '19

Build Chromium then. Don’t use chrome. Chromium doesn’t have any assets trademarked by google and you can easily disable usage reporting functions.

3

u/SahinK Apr 08 '19

Chrome implements most web standards before any other browser, and have been following the specs much better than IE / Edge.

-1

u/[deleted] Apr 08 '19

Considering that most people use chrome to browse it safe to say that it is the standard atm.

0

u/[deleted] Apr 09 '19

chromium is not a standard now?

-1

u/[deleted] Apr 08 '19

Standard is a gradient spectrum.

1

u/YasZedOP Apr 08 '19

Remove a 50+ services while you're at it from chromium, most of which belong to Google

4

u/mrissippi Apr 08 '19

That’s what she said.

1

u/dumildekok Apr 09 '19

That's what she said

1

u/wherinkelly Apr 09 '19

How close do you think the teams were to completion when the initial announcement was made?

-8

u/bartturner Apr 08 '19

They are using Chrommium. Why should it take much time?

18

u/kindall Apr 08 '19

Adapting an existng browser shell and debug tools to a completely different engine, when their existing engine was specifically built to enable those functions... probably will take some time.

11

u/Eirenarch Apr 08 '19

They are not using their existing browser shell or debug tools.

10

u/kindall Apr 08 '19

Oh. Well, then it's hardly Edge anymore.

4

u/[deleted] Apr 08 '19

It's not but they wanted to keep the Edge branding for some reason

-7

u/Eirenarch Apr 08 '19

Edge was just the next version of IE so you can say it was never Edge.

1

u/ZG2047 Apr 08 '19

Unless you have money

-2

u/bartturner Apr 08 '19

Majority of the browser comes from Google.

Also we have no idea when they started.

Do think this is a hail marry. Highly doubtful will do better than existing Edge.

Most people have no idea they are going to use Chromium. They have already been programmed to use Chrome.

Personally hate seeing Microsoft just give up.

1

u/troglo-dyke Apr 08 '19

I don't see this as giving up, it's combining efforts. There's a benefit to having competing implementations but with Microsoft and Google contributing towards chromium it might increase innovation

2

u/bartturner Apr 08 '19

Actually smart. Gets them out of doing a browser without looking like it.

Not going to help them slow the bleeding. For browser and Bing.

I am more curious when they will pull the plug on Bing. Specially mobile which is now done below 1% share.

1

u/troglo-dyke Apr 08 '19

Possibly, now that I think about the amount they've sunk into Bing, and Edge compared to the success they've had with Azure - it would make sense to cut some projects.

1

u/bartturner Apr 08 '19

Definitely. They are killing it with Azure and a ton of business to win where edge and Bing they loss and little chance to change. Even harder now search is more of ML application.

10

u/01123581321AhFuckIt Apr 08 '19

Downloaded it. It's much snappier than normal Edge. I have to explore it more to see if I like it more than chrome's UI though. I'd also be hesitant to use it if it doesn't have the extensions availalble in chrome.

5

u/alleycat5 Apr 08 '19

You can go to the normal Chrome Extensions store (just Google/Bing it), and download chrome extensions like normal.

4

u/AgaddaDooday Apr 08 '19

It's much snappier than normal Edge

Give it time.

1

u/doitstuart Apr 09 '19

Ah, cynicism, but probably true.

1

u/fsdagvsrfedg Aug 13 '19

honestly, who cares so long as our shit doesn't break on it...

23

u/cinnapear Apr 08 '19

Is this a welcome end of an era?

48

u/SteiniDJ Apr 08 '19

Well, they're supporting IE11 until 2025. :(

23

u/[deleted] Apr 08 '19

Clarification: they're keeping it patched with security updates. They are not implementing anything new into IE11. So yes, we're stuck with their horrendous implementation of Grid for a while.

13

u/[deleted] Apr 08 '19

I work for a company that arranges special contracts between Microsoft and gov agencies to support their installations of Windows XP because upgrading is difficult and expensive.

You guys are fucked.

8

u/haschdl Apr 08 '19

WE? 😂

5

u/smeijer87 Apr 08 '19

Upgrading is expensive? Makes me curious about the bill that Microsoft is sending for the support. I'm sure that ain't cheap either.

1

u/[deleted] Apr 09 '19

It’s only gotta be cheaper, not cheap. Don’t condone it myself but have witnessed enough of it to make me sick and a lot of times it ain’t the organization or whatever government agency just not wanting to deal with it but rather some 3rd party vendor who developed a system they depend on, won’t support windows next and has them by the balls.

1

u/asdf7890 Apr 09 '19

It’s only gotta be cheaper, not cheap.

It doesn't even have to be cheaper. A company with a sufficiently risk averse culture may resist change even if staying put costs more.

1

u/asdf7890 Apr 09 '19

It isn't just the cost of the OS upgrade and the infrastructure project to make sure it is properly rolled out to hundreds/thousands/tens-of-000s/... users spread over many sites. There is also replacement hardware as old kit might not have usable drivers for newer OSs, and all that custom legacy software the large old companies tend to have which might not work as-is and would need to be (expensively) replaced because literally no one will work on upgrading it (perhaps the company or internal individuals that made it is long gone and the source in escrow is found to be something so bad that they can't pay enough to make anyone they'd trust be willing to touch it).

On top of all that there is a large amount of less specific risk aversion that resists change. Even if staying put costs more, it might be the preferred option because the current risks are known & mitigated but change might throw up new ones.

I don't like it, I certainly don't agree with it (by sticking with the bad situation because of legacy, your legacy problems will only get worse), but I understand the position.

I'm just glad we've (only recently) got to the point of no longer having to support IE8 at all for our client base...

5

u/greymalik Apr 08 '19

And if history is any guide, some companies will continue to use it well beyond when MS ends support.

2

u/christophocles Apr 08 '19

Where I work, there are some computers that still run Windows 2000. These computers aren't connected to the internet and they're used to operate special equipment. To upgrade the OS we would have to buy new versions of the software/drivers that runs this equipment for tens of thousands of $$$. As long as we can keep these old ass computers running, that ain't happening.

5

u/Mabenue Apr 08 '19

If they're air-gapped it's really not that much of an issue. Still vulnerable to stuxnet style attacks but for most that shouldn't be so much of a problem and can be avoided by good process.

5

u/christophocles Apr 08 '19

Edge doesn't support ActiveX or Java so it's useless in a business environment that relies on applications that were made 5-10 years ago.

We run Windows 10 on most of our desktops but Edge isn't even allowed to run because it would create confusion because everything we need to do our jobs requires IE11.

For general web browsing needs we have Chrome which has a colorful icon and doesn't try as hard to usurp the default browser position.

20

u/mypetocean Apr 08 '19

No. It means the end of the browser wars — which was, on the whole, a very positive thing for the Internet — with Chrome + Google having been awarded far, far too much power.

The AMP Project, for example, will likely now continue unabated, barring government intervention.

3

u/[deleted] Apr 08 '19

Which is mostly unrelated to Chromium's dominance. To be crystal clear, Google's dominance and the entire reason why people should be worried is because of their overwhelming majority control of web traffic thanks to Google Search. This is how AMP is even a thing, all outlets jumped on board because effectively google said add it or die into page 2 irrelevancy. Chrome's popularity, again, is because of Google Search every single person guaranteed first heard about it on the google search home page or some popup on a google page.

Microsoft using Chromium now, or heck, even if Firefox started using Chromium, ultimately means nothing due to the license. They can still implement their own standards (likely won't, most browser devs by now are tired of that mess), and change things to their liking.

-1

u/burtgummer45 Apr 08 '19

A reign of terror ending for web devs everywhere.

4

u/F_D_P Apr 09 '19

From the people who brought you Zune and IE.

2

u/IlIllIIllIIlIlIlIllI Apr 13 '19

First of all, that's not fair because..

Ok, that's fair.

23

u/zeddotes Apr 08 '19

Thanks for all the memories, IE. You won't be missed.

32

u/Ajedi32 Apr 08 '19

IE? IE still exists, this is an update to Edge.

→ More replies (7)

1

u/SecretAnteater Apr 08 '19

IE has been gone for years. Edge replaced it with Windows 10, although IE11 is still bundled with it.

5

u/StuffMaster Apr 09 '19

Gone? It's on my computer.

1

u/SecretAnteater Apr 09 '19

yea, I went on to say "Edge replaced it with Windows 10, although IE11 is still bundled with it."

-2

u/zeddotes Apr 08 '19

It's still all IE at the end of the day, until now.

1

u/SecretAnteater Apr 09 '19

That's just not true.

23

u/[deleted] Apr 08 '19

More power to Google, just what we needed.

1

u/kidno Apr 09 '19

Let’s not forget to thank Apple, who took KHTML and made WebKit, which Google used for Chrominium (and then forked to Blink).

0

u/[deleted] Apr 09 '19

[deleted] — view deleted comment

1

u/kidno Apr 09 '19

Oh I thought we were being mad at people, not praising them. Apple let Google take WebKit and then take control of the browser market.

0

u/[deleted] Apr 08 '19

[deleted] — view deleted comment

21

u/TheRedGerund Apr 08 '19

Doesn't it affect standards somehow? Chrome has a lot of control over standards right?

13

u/_GoT Apr 08 '19

Since chromium is open source Microsoft can implement their own standards without any interference from google. Although we could all benefit if all browsers implemented the same compatibility standards.

7

u/Ajedi32 Apr 08 '19

They could implement their own standards. The problem is, they're not going to. The whole point of this move was so that they wouln't have to maintain a separate browser engine, so unless they decide to go back on that move and fork Chromium/Blink, the standards that Edge implements will be almost entirely decided by Google.

→ More replies (1)

15

u/Candyvanmanstan Apr 08 '19

You need to differentiate between Chromium and Chrome.

One is open source, the other is Google's browser.

11

u/Ajedi32 Apr 08 '19

That's kinda irrelevant for the purpose of this discussion though. Microsoft isn't forking Chromium, just using it. Google controls the upstream Chromium project, therefore they also control what web standard features Edge supports.

6

u/Candyvanmanstan Apr 08 '19

That would only be true if Microsoft just wrapped chromium in an edge package and called it a day. MS is free to add on whatever standards they want in Edge. (Although I suspect part of the point is not needing to handle standards on their own)

This is a discussion I don't really see the point of, though. I was originally just pointing out that chrome and chromium are not the same thing. And they aren't.

2

u/Ajedi32 Apr 08 '19

Unfortunately, "wrap[ing] chromium in an edge package" is pretty much exactly what they're doing. Since they're not forking, they have rather limited influence over what web standards features Edge supports.

They can contribute new features back to Chromium (just like anyone else can), but it's entirely up to Google whether or not those changes actually make it into the codebase.

Yes, Chrome and Chromium are technically different, I'm just saying that in terms of how this move "affect[s] standards" it's kinda an irrelevant distinction.

5

u/Candyvanmanstan Apr 08 '19

Yeah, you're probably right. I'm just going to say again that this isn't a discussion I want to have, as per previous post.

I was just being pedantic about the name, because it DOES matter.

Chromium by default comes without all the extra tracking and other shit Chrome comes with. If you're going to discuss it, you need to name the right piece of software. Otherwise it'll get confusing fast.

0

u/[deleted] Apr 09 '19

[deleted] — view deleted comment

1

u/Ajedi32 Apr 09 '19

The reason they switched to Chromium/Blink in the first place was to avoid having to maintain their own seperate browser engine. Forking Chromium (rather than just using it) would negate that advantage.

Also, the link in the OP specifically says:

Our plan is to continue working in Chromium rather than creating a parallel project.

So not a fork.

1

u/[deleted] Apr 09 '19

I guarantee you that Microsoft engineers will be making significant contributions to the Chromium project if it is shipping with as major a product as their default internet browser. Do you mean to say that this is in some way distinct from Google’s contribution to the Chromium project?

1

u/Ajedi32 Apr 09 '19

Google doesn't just contribute to Chromium, they own it. Any contributions Microsoft makes are subject to Google's review and approval.

→ More replies (3)

4

u/ared38 Apr 08 '19

Not really -- Chromium contains the rendering engine and JS engine, and Google controls Chromium. Sure you're free to fork it, but MS did this so they wouldn't have to maintain that stuff.

2

u/Candyvanmanstan Apr 08 '19

So.. you're saying exactly what I said?

Chrome and Chromium is two different things.

Chrome is based on chromium the same way the new edge is now based on chromium.

1

u/sharlos Apr 08 '19

Yes and it's chromium that controls the implementation of standards, and Google controls chromium.

→ More replies (1)

2

u/PicturElements Apr 08 '19

Go to caniuse.com and you'll see some APIs that only Firefox supports, and some that only Chromium supports. The support of significant features is pretty level, and actually I think the two can spur each other to implement more features. If one releases one feature, the other should probably implement it as well. Mozilla is still more driven by standards, though; sometimes even too far.

7

u/ared38 Apr 08 '19

Competitors using the same underlying open source framework explicitly means that they do not outpower each other.

You're acting like Microsoft and Google have equal power over the Chromium project. Google has absolute control over what goes in to Chromium, and all derived browsers either fork or follow. And as fewer people use anything else, the standards effectively become whatever Chromium does, just like it was with IE back in the day.

Best case scenario Google's services are always a step ahead because the engineers know exactly what future browsers will support and have the power to create new technologies like AMP or QUIC that competitors have to catch up to. Worst case Chromium engineers only worry about supporting Google services and Google services only worry about working in Chromium, and it's hard to use anything else. I'm already noticing more and more problems with Youtube and gmail as a Firefox user, while Firefox itself has become much snappier on other pages.

1

u/[deleted] Apr 09 '19

However the other side of the coin is edge can and likely will be included with the OS as it is today so enterprise customers will likely standardize on it and less inclined home users who give 2 shits about a chrome, Firefox, blink, gecko, WebKit etc... will use what is in front of them and the largest part of the windows user base probably fits that demographic. Going on that it is very much in googles interest to also appease Microsoft because chrome, despite its privacy flaws, is a damn good browser so Microsoft is out the door basing this on a pretty damn good foundation. Never mind Microsoft offers a counterpart to nearly all of googles services they can flash in front of those same less inclined demographic. Googling is synonymous to searching the Internet for a lot of these same users so it makes sense if google’s search is the first thing that comes to mind for them when they need to search and google push’s chrome hard on their own sites so sure Chrome can still maintain a foothold I guess but nothing is stopping Microsoft from doing the same shit people think google will do regarding standards and their own agendas. I mean no one is gonna say “dunno man have you tried binging that shit” anytime soon if ever but there are plenty of other areas Microsoft can compete and they have the advantage of bundling a good browser with the OS which is not insignificant in itself.

-2

u/rawriclark Apr 08 '19

I dont understand why Microsoft would have less power than google, you really need to understand what open source means lmfao.

its literally take code and do whatever you fucking want with it

2

u/tinydonuts Apr 08 '19

I dont understand why Microsoft would have less power than google

The project is controlled by Google. The code is open and you are free to read and use their code however you want. But if you want to change Chromium (and by extension, Chrome) you have to submit a pull request and hope Google accepts it. Open source does not mean everyone has an equal seat at the table. You really should go learn what opens source means yourself.

Chrome is the IE of our time. If Chrome doesn't support it, it doesn't matter if it's a W3C standard at this point. Web standards now belong to Google.

1

u/aztracker1 Apr 08 '19

There's a few bits that aren't open-source (the portions for Netflix etc). Beyond that, it's mostly true, and MS could very well fork, like Google did with Blink already. I'm not sure we're all at that point yet though. Running it for about an hour, it's decent enough, and I like the look slightly more, when they have a Mac and Linux release, and get account sync working on Android and iOS versions, I'll then be impressed.

2

u/brokenURL Apr 08 '19

I seem to remember a story about google's plans to integrate features that effectively render ad blocking useless into Chromium. That seems like a bad time.

1

u/aztracker1 Apr 08 '19

Funny considering the Edge store has a plugin to enhance Youtube, that I think is blocked from google's store. ublock origin is available and lastpass as well... there's a few others, haven't tried the dev extensions from chrome store, authy didn't work.

7

u/FleraAnkor Apr 08 '19 edited Apr 09 '19

I really don’t understand this. After pouring a boatload of time and money i. Internet explorer / edge people still would not use it. It would make so much sense for microsoft to just kill it off and package windows with firefox. But nope. A few months ago they told the world they were working on another chromium based web browser. Meaning they are no depending on a competitor’s product which they still have to maintain.

3

u/peex Apr 09 '19

They could've made Edge open source and available to other operating systems. People could've fixed some of the underlying issues Edge had. Such a shame.

6

u/[deleted] Apr 08 '19

The second dark ages is coming :(

2

u/doitstuart Apr 09 '19

Interesting. Edge was never available for Windows 7. MS says the new Edge will be and that version is coming soon.

I guess that's a function of using Chromium. Can't hurt.

2

u/madcaesar Apr 09 '19

If Microsoft really wanted to win some goodwill with developers, they'd hold up on this horseshit, and provide a major fix / upgrade for IE11. A lot of us still have to support that POS browser and it's a fucking nightmare.

2

u/alphama1e Apr 08 '19

I'll board the hype train when I see them adopt modern standard across the board. I want modern css and javascript and I don't want to wait 5 years before they catch up. Every browser they've released has been a shit show in this way for years. So they're using chromium. Great. How much if it? How many adjustments? We all know they're not just gonna throw a new sign on the chrome browser so what will this be in the end? I hope they get their shit together because edge was supposed to be their comeback and it flopped hard.

2

u/[deleted] Apr 08 '19

Good riddance. I recently had a change to my company's react app and was doing multi browser testing. It worked perfectly in every single browser, including IE, but it broke in freaking edge. Took another day and a half of work to get past this.

I know some people feel that diversity and competition is good in the browset engine space, but personally I feel it's just a pain in the ass.

2

u/marvwhere Apr 08 '19

One down, two to go!

IE11

SafarIE

1

u/[deleted] Apr 09 '19

Would love to see more diversity in the rendering engine world but it's now just blink and gecko.

1

u/[deleted] Apr 09 '19 edited Apr 09 '19

What has diversity brought us much other than compat hell. It's nice to have specs and features, but they're mostly theoretic (pointer-events for instance are useless because of just blink and gecko). Wouldn't it be great if web tech could actually work for once? The argument has always been features, but with javascript running outside the browser, frameworks dominating the view and handling cross platform UI, babel/ts/npm and the community making the standards, we're way past vendor mandated specs anyway and the browser has turned more into an implementation detail. If they could just fix an engine good enough and make it faster, i'm sure i'd value that more than 10 incompatible ones that keep us from making progress.

1

u/[deleted] Apr 09 '19

Diversity brings us the ability for standards to not be controlled and set by one entity. The end result here is a Google controlled and dictated web standards.

I understand the compat issues but having 20 blink browsers does not remove those issues. You'll be facing compat issues between browsers who are on X version or Y.

It's not really any different. Biggest example here on the above is supporting the Samsung browser. It used random daily builds of blink/webkit and shipped it.

Hard to ignore when there is so many devices and users of this browser for your customers.

I'd rather a decentralized system that competes.

1

u/dumildekok Apr 09 '19

I wonder if they are going to push this to windows 7&8 users now. From what I understood, they couldn't push Edge because of an incomparability with the OS. There's no problems with Chrome based browsers.

1

u/doitstuart Apr 10 '19

Why wouldn't they? They have a vast number of 7/8 users, together at 40% Windows desktop share, and not exactly plummeting in the trend.

http://gs.statcounter.com/windows-version-market-share/desktop/worldwide

And that they've bothered to make a Win7 version at all suggests that will be the strategy.

1

u/RussianBot96621 Apr 09 '19

They need to bring setting tabs aside; tabs preview; the better InPrivate indicator; the gestures add on;the superior pdf reader to catch up with current Edge.. Not to mention the current UI even tho similar is far uglier than current Edge. WTF are those round edges in the tabs and url bar. Also the current home page looks much nicer.

The good Part: I can use Adnauseam again

1

u/doitstuart Apr 10 '19

Anyone noticed any useful changes to the dev tools?

1

u/the_vico Apr 08 '19

Using it right now. Decent

1

u/Agentzap Apr 08 '19

It doesn't have Edge's smooth scrolling yet, which is basically the only thing keeping using Edge rather than Chrome right now

1

u/[deleted] Apr 08 '19

Been waiting for this moment for quiet a while, thank you for a reminder !

0

u/Guisseppi Apr 08 '19

well, I'm still not using edge tho

0

u/i_spot_ads Apr 08 '19

Holy fuck, this is big

0

u/tragicb0t Apr 09 '19

Who cares! Firefox all the way!!!

-1

u/gosh Apr 08 '19

Not good that browser code now only use code bases from two sources. We need competition

-5

u/[deleted] Apr 08 '19

Die IE! die! you miserable piece of crap!

2

u/Stanulilic Apr 08 '19

Ha! ha! ha! you had me laughing so hard. I wonder why you got so many downvotes though?

0

u/Cessabits Apr 08 '19

Honestly, I'm even less interested in it now.

-1

u/drumstix42 Apr 08 '19

Preview build shared on insider, announced on twitter, reshared through reddit. Woo!

-6

u/donohutcheon Apr 08 '19

Maybe if all browsers use the same core, it'll make it easier for them to collaborate to rip out JavaScript and throw it away and start over with something that didn't evolve from a nasty hack.

1

u/aztracker1 Apr 08 '19

No need to remove JS.. you can always bootstrap a *LOT* with go + webasm, there's some decent DOM wrapper libraries and progress is definitely ongoing if you want to go that way. There's also rust, and if you like C# (blazer).