Read more.Quote:
And it will be releasing its first browser for Apple Mac, after 15 years of absence.
Printable View
Read more.Quote:
And it will be releasing its first browser for Apple Mac, after 15 years of absence.
...Mozilla engine could be a better option. Google will dominate.
Given the bad history between Netscape and Microsoft, I can't see them ever adopting the Gecko engine, which is a shame.
Still, all the more reason to use Firefox.
Embrace, extend, and extinguish.
I think this is an excellent move - with Microsoft contributing to the Open Source project that is Chromium, we may see further leaps in development which may really help optimise the browsers for efficiency.
Well... I'd rather see them work with Mozilla but I suppose this does mean I don't need to install chrome (yes I know I could just get chromium) just check if a website works....
Having said that, half the problem is that websites are now being designed to take into account chrome only features (google earth for example ONLY works in chrome browser, yes I know it's a google property) which are not web standards.... got to love web devs who moaned like crazy about ie6 having it's own browser specific code and now we're seeing them using the same 'browser specific' code they hated so much for another browser, basically because it's from Google...
I thought this was more down to Google proposing a standard to W3, implementing it early in Chromium and then using it almost immediately rather than Microsoft 'custom' web (activeX :( ). Not perfect but at least others can implement and benefit from the new standards rather than just hijacking. Only risk is Google are increasingly writing the web standards however someone has too - The standards did get stale for a while.Quote:
Originally Posted by LSG501
One in same and prefer google verQuote:
Originally Posted by LSG501
Some of it might be that but there's also some code that dev's are tapping into that only works on Chrome from what I've read.Quote:
Originally Posted by cheesempI thought this was more down to Google proposing a standard to W3, implementing it early in Chromium and then using it almost immediately rather than Microsoft 'custom' web (activeX :( ). Not perfect but at least others can implement and benefit from the new standards rather than just hijacking. Only risk is Google are increasingly writing the web standards however someone has too - The standards did get stale for a while.Quote:
Originally Posted by LSG501
Luckily, at least on the sites I browse, I haven't seen anything that won't work well on firefox, although the 'new' google maps was a little lacking in features when it first came out unless I used chrome...
The difference between the ie6 days and Chromium now is that Chromium is open source and community makes many of the decisions in how the development continues.Quote:
Originally Posted by LSG501
Does this mean we no longer get actual high res netflix? Edge was the only browser that allowed above 720p...
It seems like almost everyone seems to think that the only way to get a share of the popular browser pie is to follow Chrome's lead (as Firefox did) or become a Chromium rebrand, despite plenty of perfectly good technology being left behind as a result.
It seems that soon the only ones actually using a different technology will be the smaller independent browser makers, such as Pale Moon and others built on UXP (Unified XUL Platform).
But not everything in Chrome is in chromium, and this is the bit some companies are 'tapping into' at the expense of other browsers.Quote:
Originally Posted by deepblue08
You can use the netflix app :)Quote:
Originally Posted by outwar6010
Wow, has it really been 15 years since IE for OSX? Sheesh.....
I was wondering why I hadn't seen anyone use it in years :)
It will also have the chromiums ram management issues?
They'll still find a way to screw it up. For me, one of the most irritating behaviours with Edge was the taskbar 'helpfully' unhiding itself when I move the mouse cursor to the bottom of a full screen window to unfullscreen it. They do the same thing with all UWP apps, so switching rendering engines wont help here.
From security perspectives, it will make even more sense for hackers to target Chromium over FF and everything else.