Slashdot Mirror
Microsoft is Building a Chromium-powered Web Browser That Will Replace Edge on Windows 10: Report (windowscentral.com)
Microsoft is throwing in the towel with Edge and is building a new web browser for Windows 10, this time powered by Chromium, news blog Windows Central reported Monday. From the report: Microsoft's Edge web browser has seen little success since its debut on Windows 10 back in 2015. Built from the ground up with a new rendering engine known as EdgeHTML, Microsoft Edge was designed to be fast, lightweight, and secure, but launched with a plethora of issues which resulted in users rejecting it early on. Edge has since struggled to gain any traction, thanks to its continued instability and lack of mindshare, from users and web developers.
Because of this, I'm told that Microsoft is throwing in the towel with EdgeHTML and is instead building a new web browser powered by Chromium, a rendering engine first popularized by Google's Chrome browser. Codenamed Anaheim, this new web browser for Windows 10 will replace Edge as the default browser on the platform. It's unknown at this time if Anaheim will use the Edge brand or a new brand, or if the user interface between Edge and Anaheim is different. One thing is for sure, however; EdgeHTML in Windows 10's default browser is dead.
Because of this, I'm told that Microsoft is throwing in the towel with EdgeHTML and is instead building a new web browser powered by Chromium, a rendering engine first popularized by Google's Chrome browser. Codenamed Anaheim, this new web browser for Windows 10 will replace Edge as the default browser on the platform. It's unknown at this time if Anaheim will use the Edge brand or a new brand, or if the user interface between Edge and Anaheim is different. One thing is for sure, however; EdgeHTML in Windows 10's default browser is dead.
At least part of Edge is already open source:
https://github.com/Microsoft/C...
I feel bad for Microsoft. They have been trying very hard to support all the standards.
Don't because those assholes only implement standard when they have no other choice. Microsoft has a long history of trying to undermine standards with purposely shitty support.
Anons need not reply. Questions end with a question mark.
whether open source or not. It is going to be interesting to see how we address open source monopolies.
KHTML is a fork of webkit
Wrong, it's the other way round.
When all you have is a hammer, every problem starts to look like a thumb.
I guess we still haven't forgiven or forgotten IE6. Any MS web browser should be treated with extreme suspicion.
Not to mention SharePoint 2013/2016 still needs to run in IE10 mode on IE11.
I would love nothing more than to see DirectX DIAF but the truth is no developer is going to rewrite their existing code because there is no $$$ in it. Therefore, if I can get all my Steam games to work on a Linux kernel via a Microsoft derived Linux kernel/DirectX implementation I'm all for it.
Nobody implied developers should go rewrite their shit to remove DirectX
You could use the Linux version of Steam with Proton to make the Windows games from your Steam account work on Linux
And I just played the Windows version of Starcraft 2 on Linux using Lutris to configure the correct Wine version etc.
I've got more instabilities with Chrome than actually with Edge. Both have their plusses. Biggest problem with chrome was that it was doing exactly what people bitcht at with IE6, but a lot of webdevs didn't mind this time, as it was their prefered browser.. a lot of times they don't even check their sites with Edge, which is even more HTML5 compliant than Chrome.. Ahwel, I don't care (like a lot of people), as long as I can browse..
PROTIP: Use a package manager like Chocolatey to avoid needing to open Edge at all! Install it from a flash drive and then easily install/update all the software you need without visiting a dozen websites.
Scoop (https://github.com/lukesampson/scoop) is pretty good too. Fewer packages but you can install it directly from PowerShell without even a flash drive or browser.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
It's Palemoon for me!
I used to like Pale Moon but it has severe performance issues, and one of the updates deleted a lot of user data. I don't have confidence in the developers or that performance will ever get competitive. While it doesn't seem to have spying built in, the fact that it's using an old version of the Firefox codebase with known vulnerabilities being exploited in the wild means you will probably be p0wned by someone far worse than Google anyway.
My post above was really just mocking the Slashdot posters who always post about how Chrome is spyware, Firefox is total crap, IE is spyware AND total crap... Without being able to point to any real alternative.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
The KDE Project was mainly designed for a UI experience for *nix systems.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Brave has advertising spyware built in. https://brave.com/about-ad-rep...
They gotta make their money somehow.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Back in the late 1990's Microsoft won the browser war against Netscape
Microsoft didnt win. Netscape lost. It was a do-it-yourself mugging.
Netscape committed suicide.
"His name was James Damore."
I don't know which parallel Universe you come from, but Safari pre-dates Chrome by more than five years. Also, Google used WebKit, Apple's fork of KHTML, until Chrome version 27. Starting with Chrome 28, it used Blink as its rendering engine which is Google's fork of WebKit.
https://en.wikipedia.org/wiki/...
January 7, 2003, at Macworld San Francisco, Steve Jobs announced that Apple had developed its own web browser, called Safari. It was based on Apple's internal fork of the KHTML rendering engine, called WebKit.[9] The company released the first beta version, available only for Mac OS X, later
https://en.wikipedia.org/wiki/...
The browser was first publicly released on September 2, 2008 for Windows XP and later, with 43 supported languages, officially a beta version,[33] and as a stable public release on December 11, 2008.
#DeleteFacebook
but there has been so much code flow back and forth between the two it's hard to tell where one ends and the other one begins.
Wrong. KHTML project has long struggled to integrate WebKit patches from Apple. Partially because Apple releases massive patches with little to no documentation, different approaches to coding, and difficulties in code sharing. At this time the code bases have diverged significantly enough that KDE currently supports both KHTML and WebKit using some wrappers, rather than integrating everything into KHTML.
Linux has "POSIX.1e DRAFT" ACLs. They are functional, but limited, and based upon an unratified and abandoned draft standard. Other Unix sytems, like Solaris, IllumOS and FreeBSD, implemented NFSv4 ACLs which are both a ratified published standard and are compatible with both POSIX.1e DRAFT and Windows ACLs. (They are a superset of both.) If you're using NFSv4 ACLs they are modifiable and queryable from the command-line with get/setfacl and they are also modifiable and queryable from the Windows security/permissions property pages in the explorer (if exported via Samba or NFSv4). The whole ACL situation is limited by the fact that Linux hasn't implemented NFSv4 ACLs in the VFS. Yet filesystems like ZFS and NFSv4 use them, but they are hidden and inaccessible on Linux. If Linux implemented them, we would have pretty comprehensive and interoperable ACL support between all the major platforms.
This security problem brought in a new lightweight browser called Firefox. Which supported the standards much better then IE, was faster and didn't use the stuff that allowed people to break into the computer. Then Firefox grew where it started to be too big, that is where Google Chrome came in (at around the same time Safari came in for Apple also based on WebKit)
A couple important missing bits to note in your history here:
- Firefox is powered by Mozilla which was also the core of Netscape Navigator, so Firefox was basically the revenge of Netscape.
- WebKit was created by Apple (as a fork of the KHTML renderer from KDE) specifically to power Safari (all of the OSX/OpenStep/NeXTSTEP libraries are named something-Kit), and then Google adopted that for Chrome, so Safari isn't really just a side note, Safari is essentially the ancestor of Chrome.
-Forrest Cameranesi, Geek of all Trades
"I am Sam. Sam I am. I do not like trolls, flames, or spam."
The big problem with Active X security is if you ever downloaded a control and checked off "Trust Microsoft".
At that point any website could force a different version of an Microsoft signed active-x control to download.
So if there was a serious exploit was found in version 1.2 of a control, does not matter it is 5 years later and the user has version 1.8. When they visit your site you can force the download of version 1.2 and then execute your exploit.
There was just no way round this. If you had to do business with a trusted site that had active-x controls, if they ever got hacked AND you had ever clicked "Trust Microsoft" there was no way to defend against that.
vi +