Microsoft Edge: Building a safer browser • Hacker News Board

Re: Microsoft Edge: Building a safer browser

#71

Post by zyx321 » Tue, May 12, 2015, 8:48 AM UTC

lawnchair_larry wrote: post #53

"A broad variety of memory corruption mitigations have been devised since the mid-1990s, and in the 2000s Microsoft has lead the way with advances including ASLR, DEP, and SeHOP." No, they didn't lead the way. PaX beat them by at least 5 years, yet they still take credit for this. They didn't even create the Windows version of ASLR in house. "including industry leading sandboxing" They're really going to claim that t…

Has the Win 8 app store sandbox been broken? There's a "Win8 RT Jailbreak" on XDA, but the author says there's no risk of regular apps compromising your system using the same exploit.

Re: Microsoft Edge: Building a safer browser

#72

Post by mynameisvlad » Tue, May 12, 2015, 2:16 PM UTC

Turing_Machine wrote: post #44

adventured wrote: post #43

Earlier quoted context omitted.

More likely closer to 25% to 30% Every other major source than that one reports IE well above 12% http://www.zdnet.com/article/the-most-u-s-popular-web-browse... https://www.netmarketshare.com/browser-market-share.aspx?qpr...

The first one is limited to .gov websites, and lots of government agencies still use IE for internal use. The second one excludes mobile, for no good reason that I can see. Mobile is huge.

Because the browser landscape is completely different in mobile? There isn't really any reason not to separate them. They're completely different markets.

Re: Microsoft Edge: Building a safer browser

#73

Post by cantankerous » Tue, May 12, 2015, 2:29 PM UTC

magicalist wrote: post #54

cantankerous wrote: post #47

Earlier quoted context omitted.

Google has its own proprietary sign in features across its offering. I think it's becoming more or less standard fare.

If you're talking about password syncing, Chrome uses the system's password store. Hopefully the Microsoft Passport the article refers to is just a password manager. edit: unfortunately, no, it just appears to be another sign-in with company X: http://blogs.windows.com/bloggingwindows/2015/03/17/making-w...

No. I'm talking about the Google user sign in features for Chrome and Android. Microsoft is adding a twist to its version, but in my mind they're pretty much the same.

Re: Microsoft Edge: Building a safer browser

#74

Post by Navarr » Tue, May 12, 2015, 4:11 PM UTC

cantankerous wrote: post #73

magicalist wrote: post #54

Earlier quoted context omitted.

If you're talking about password syncing, Chrome uses the system's password store. Hopefully the Microsoft Passport the article refers to is just a password manager. edit: unfortunately, no, it just appears to be another sign-in with company X: http://blogs.windows.com/bloggingwindows/2015/03/17/making-w...

No. I'm talking about the Google user sign in features for Chrome and Android. Microsoft is adding a twist to its version, but in my mind they're pretty much the same.

The automatic sign in to Google if you're signed in to Google on Chrome?

This sounds more like an extension of the browser that either you use Edge or you can't sign in

Re: Microsoft Edge: Building a safer browser

#75

Post by Turing_Machine » Thu, May 14, 2015, 12:06 AM UTC

mynameisvlad wrote: post #72

Turing_Machine wrote: post #44

Earlier quoted context omitted.

The first one is limited to .gov websites, and lots of government agencies still use IE for internal use. The second one excludes mobile, for no good reason that I can see. Mobile is huge.

Because the browser landscape is completely different in mobile? There isn't really any reason not to separate them. They're completely different markets.

No, they aren't different "markets" They're not even different code. Safari on iOS comes from the same code base as Safari on desktop, and I'm pretty sure the same is true for Chrome on Android (Chrome on iOS, like other iOS browsers, is just a wrapper around the Safari engine).

The old Android browser was different code, but that's been on its deathbed for a while now.

Mobile users use the same sites as desktop users, to a very large degree. They use the same browser code (again, to a very large degree). The only reason to separate them that I can see is to artificially inflate the number of IE users.