Live data from Hacker News

The new Microsoft Edge is out of preview

blogs.windows.com

271–280 of 487 posts

Re: The new Microsoft Edge is out of preview

#271

Regarding the topic of browser mono-cultures, I was web developer in the post browser war era in the early 2000s where we had a dominant IE6 and a stagnant browser landscape. It was bad. Real bad. But I'm actually fairly positive about MS getting into the chromium landscape and back into the game. Let's face it MS had lost all of its influence in the browser world before dropping IE and making this move. It is a Goog…

I just wish they'd moved to Gecko instead of Chromium.

It's not like Gecko is an inherently inferior engine by any stretch, and it would significantly bolster their marketshare so that developers actually have to test against it.

Re: The new Microsoft Edge is out of preview

#272
post #56

Earlier quoted context omitted.

It doesn't have to make it worse, just not make it better. Almost no one ever says "I love using such-and-such a website, the adverts on the side are just so relevant".

When I'm looking for something , relevant ads are great. Ads that were relevant to something I was looking for a month ago? Not so much.

You don't have a refrigerator collection???

Re: The new Microsoft Edge is out of preview

#274
post #237

Earlier quoted context omitted.

One difference that stands out to me about Microsoft vs Google. Both are very heavy C++ shops. Both have invested in developing tools for enhancing developer productivity on their respective platforms (Windows and Linux). Yes, Linux is not a Google product (thank god) but it is what they build on. Microsoft's C++ IDE and debugger are the gold standard for productivity and ease of use - everyone who writes native appl…

Have you actually tried to use Visual Studio? It's an unusable piece of crap. The navigation is nearly unusable. Don't focus the project navigation on a tree browser if you're not going to integrate it into the rest of the navigation workflow. NuGet regularly fails silently to restore packages. It uses a virtual filesystem that usually maps 1:1 to the actual project folder.. except files created outside of VS are com…

Euh, lol.

You are talking about the biggest architecture change of. Net in 30 years ( going cross platform) and they are still going to support VB 6, WPF,..

Visual studio is actually a very robust IDE. The issue you are mentioning is .net framework project files and if you copy files within or to Visual Studio it will be added. .net framework only wants to add files you want to deploy ( not perfect, but okay).

For migrating to. Net standard 2.0, remove assemblyinfo.cs and change the. Csproj file. You should manually add the Nugget packages again or change it to the new structure. The biggest issue is entity framework though, in a lot of projects. From. Net standard to . Net core is a lot easier.

Seems pretty reasonable to me, updating other things ( eg. Android) have caused more issues than this.

Ps. Navigating is mostly f12 of control+f12

Re: The new Microsoft Edge is out of preview

#275

If someone told the young Linux freak me back in the early 2000s that one day Internet Explorer’s rendering engine is based on the KDE rendering engine I would’ve probably died laughing and frozen in horror at the same time. Yeah, I realize there’s probably nothing left if the old KHTML but it still does give me a chuckle.

But one wouldn't have been surprised to find out that the Microsoft's KHTML based browser doesn't run on any open source operating system.

IIRC it exists for Android.

Re: The new Microsoft Edge is out of preview

#276

Regarding the topic of browser mono-cultures, I was web developer in the post browser war era in the early 2000s where we had a dominant IE6 and a stagnant browser landscape. It was bad. Real bad. But I'm actually fairly positive about MS getting into the chromium landscape and back into the game. Let's face it MS had lost all of its influence in the browser world before dropping IE and making this move. It is a Goog…

I just wish they'd moved to Gecko instead of Chromium. It's not like Gecko is an inherently inferior engine by any stretch, and it would significantly bolster their marketshare so that developers actually have to test against it.

One huge advantage the Chromium has over Gecko is Google's Security Team (ie Project Zero).

For most users, the web browser is one of the biggest attack surfaces and having arguably the best security team behind the browser engine is a good thing.

Re: The new Microsoft Edge is out of preview

#277

Regarding the topic of browser mono-cultures, I was web developer in the post browser war era in the early 2000s where we had a dominant IE6 and a stagnant browser landscape. It was bad. Real bad. But I'm actually fairly positive about MS getting into the chromium landscape and back into the game. Let's face it MS had lost all of its influence in the browser world before dropping IE and making this move. It is a Goog…

Chromium is open source, Microsoft has published most of their interesting work on Chromium itself. A monoculture is a big problem if the alternative is to write a new browser to compete , less so if you can just fork and have the same start line.

Well they could have picked up one of the other less-dominate browser engines. WebKit and Firefox are good starting points, and both could use the extra help maintaining their open-source core.

I get that they wanted to use the same browser as Electron, now that they own it...it just sucks.

Re: The new Microsoft Edge is out of preview

#278

Earlier quoted context omitted.

I wish they had thrown in with helping Firefox instead of handing even more web influence over to Google. A percentage of what Microsoft spent on EdgeHTML contributed to the Firefox project—ideally as employee time—would go a long way, along with the counterbalance of putting the Firefox engine and code base front and center of more Windows users.

Sadly Chromium is WAYYYY easier to development on than Firefox. Had Mozilla spent effort making the base of it as a framework in the same way Chromium is, they may have considered it. There is a reason why Electron, QT etc use Chromium.

Then they could have chosen WebKit.

I get the Electron reason...it just sucks.

Re: The new Microsoft Edge is out of preview

#279
post #148

Earlier quoted context omitted.

I have a feeling this might change once Firefox is either entirely written in Rust, or mostly written in Rust.

Why?

A lot of legacy code is being removed. As this happens the codebase will be reworked with contributors in mind.

Re: The new Microsoft Edge is out of preview

#280

Regarding the topic of browser mono-cultures, I was web developer in the post browser war era in the early 2000s where we had a dominant IE6 and a stagnant browser landscape. It was bad. Real bad. But I'm actually fairly positive about MS getting into the chromium landscape and back into the game. Let's face it MS had lost all of its influence in the browser world before dropping IE and making this move. It is a Goog…

I just wish they'd moved to Gecko instead of Chromium. It's not like Gecko is an inherently inferior engine by any stretch, and it would significantly bolster their marketshare so that developers actually have to test against it.

I think the biggest reason they went with Chromium/Blink is simply because of market share... most users at this point are using Chrome for better or worse, and MS is going with the safest bet in terms of user compatibility for today's web.
Post reply on HN