Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The birth of Microsoft's new web rendering engine

blogs.msdn.com

Post reply on HN
Print view View original

211–220 of 247 posts

Re: The birth of Microsoft's new web rendering engine

#211

Post by scrollaway »

jsprogrammer wrote: post #210
scrollaway wrote: post #209

Earlier quoted context omitted.

I think you got downvoted for asking a foolish question. If there were linux builds in the plans, they would have announced it. If open sourcing the whole thing was planned... well, you get the idea.

I don't see what is foolish about the question (and was taught [and believe] that there are no foolish questions). MS has opened up their flagship development platform (.NET) and even has it building on Linux. MS will also rent you Linux virtual machines. The post also talks about interoperability and running across many kinds of devices, including "try out RemoteIE which will stream our latest browser from the Azure…

What's foolish is to think that such a thing wouldn't have been announced outside of the comments section of some website.

Re: The birth of Microsoft's new web rendering engine

#212

Post by stephenr »

leeoniya wrote: post #89
stephenr wrote: post #66

Earlier quoted context omitted.

the point is you should be doing feature tests, not browser tests.

there's no such thing as a feature test on the server side.

The things that are different are almost exlusively related to client side tech- html, css and js.

Re: The birth of Microsoft's new web rendering engine

#213

Post by touristtam »

Now if they could just force this new web browser onto every single Windows XP and later installation out there, so we could get ride of the horrendous amount of IE version < 11 still in use, I would see this in a positive light. The only way I am using IE at the moment if for corporate website that are engulfed in MSFT technologies.

Re: The birth of Microsoft's new web rendering engine

#214

Post by jsprogrammer »

scrollaway wrote: post #211
jsprogrammer wrote: post #210

Earlier quoted context omitted.

I don't see what is foolish about the question (and was taught [and believe] that there are no foolish questions). MS has opened up their flagship development platform (.NET) and even has it building on Linux. MS will also rent you Linux virtual machines. The post also talks about interoperability and running across many kinds of devices, including "try out RemoteIE which will stream our latest browser from the Azure…

What's foolish is to think that such a thing wouldn't have been announced outside of the comments section of some website.

Sorry, I don't have time to go through Microsoft's entire PR archive to verify. Why would anyone ask Microsoft (or an employee) a question then?

Re: The birth of Microsoft's new web rendering engine

#215

Post by couchand »

scrollaway wrote: post #209
jsprogrammer wrote: post #206

Earlier quoted context omitted.

Will there be an open source Linux build? Edit: Really? Downmods for a legitimate question?

I think you got downvoted for asking a foolish question. If there were linux builds in the plans, they would have announced it. If open sourcing the whole thing was planned... well, you get the idea.

The first rule of Linux builds is...

Re: The birth of Microsoft's new web rendering engine

#216

Post by throwaway3453 »

indians_pro wrote: post #170
icantthinkofone wrote: post #139

Earlier quoted context omitted.

I thoroughly disagree. Net Neutrality, today, is case in point. Until Chrome came along, Firefox was going it alone against IE. Until Google Fiber came along, we all had less than 10Mb downloads for $80/month. There's much, much more. Pick better battles. Google is not your enemy.

lol people like you are going to be happy when in a decade, everyone is going to be wearing google glasses, browsing through google chrome, having a google fiber internet connection, and 'renting' self-driving google cars. Cameras everywhere, control of the source internet, control of the browser, and I bet through some magic prominent universities decide that Go is the perfect language to teach beginners, over Pytho…

While I enjoyed your apocalyptic fiction, it's an indulgent fantasy. I really don't think you think this is true, and if you do, I'm very sad for you.

Regards, -Google Search Spider #52837

Re: The birth of Microsoft's new web rendering engine

#217

Post by madaxe_again »

EdSharkey wrote: post #15

YES! 1-2-3-4, I declare a browser war! Finally. This is the Microsoft I've been waiting for! No more rolling over and no defeatist talk of adopting WebKit or whatever. Microsoft is going to use its muscle and position to make a truly competitive browser. We need more competition, and we need the default browser in Windows to be just as good as Chrome and Firefox. Microsoft, I hope you pull every -ms- vendor flaggin',…

Yes! Because trident wasn't different to WebKit and they definitely worked hard to make it superior!

Wait, no, this is Microsoft we're talking about, and they'll use their monopoly to force everyone to have the "new IE", and they'll break the web, again.

Honestly, I don't know why you think they'd do anything different. They've managed one release of IE that was actually innovative and good for its time - IE4.

I have little faith that they won't just produce some xslt spewing horror show that only works with drm monitors and complains if the backend isn't .net.

Re: The birth of Microsoft's new web rendering engine

#218

Post by madaxe_again »

gtjrossi wrote: post #179
Throwaway90283 wrote: post #96

Earlier quoted context omitted.

I'd like to see some competition as well, but in my perspective, they're taking the wrong approach. This entire project seems to be about improving compatibility with older websites, by adding more algorithms and layers to the rendering process. I don't believe everyone is using Firefox and Chrome because they have better compatibility than IE. I think they should focus on cutting the fat, and making the lightest wei…

Actually, our approach is effectively yielding the results you're looking for. Removal of old IE legacy cruft is slimming Spartan's disk and memory footprint when compared with IE. Advances in the Chakra engine are pushing performance ahead. We're rearchitecting our DOM, which is yielding perf and security wins too. We're planning an extension platform also, with top add-ons like ad block being a clear target. There'…

So you're saying that Microsoft doesn't break web standards, users do?

Cool logic from the company that refuse to follow any standard they haven't defined.

Re: The birth of Microsoft's new web rendering engine

#219

Post by SiVal »

gtjrossi wrote: post #179
Throwaway90283 wrote: post #96

Earlier quoted context omitted.

I'd like to see some competition as well, but in my perspective, they're taking the wrong approach. This entire project seems to be about improving compatibility with older websites, by adding more algorithms and layers to the rendering process. I don't believe everyone is using Firefox and Chrome because they have better compatibility than IE. I think they should focus on cutting the fat, and making the lightest wei…

Actually, our approach is effectively yielding the results you're looking for. Removal of old IE legacy cruft is slimming Spartan's disk and memory footprint when compared with IE. Advances in the Chakra engine are pushing performance ahead. We're rearchitecting our DOM, which is yielding perf and security wins too. We're planning an extension platform also, with top add-ons like ad block being a clear target. There'…

I strongly hope that there will be a drive among the major browser makers to do what it takes to make the future Web as powerful a platform as possible, even at the expense of delegating support for some old websites to legacy-support plug-ins. I personally would not have a problem with a dual-path approach to the Web: one set of browsers that specify a "current standards" Web platform with maximum capabilities, strict rules, and no legacy baggage, and an optional set of browser plug-ins, to which older, non-conforming sites are delegated.

This would allow the Web platform on small-capacity devices such as watches or headsets to grow in capability like an iOS device with its frequent OS upgrades and deprecation of older code, but would make the whole Web back to the earliest websites still accessible to somewhat larger and more capable devices (desktops, laptops) that could afford to include plug-ins for any old crazy code from the past.

I really don't want the Web to be the "we'll keep hanging on to the past" platform, while the native APIs are the "we'll keep bringing you the future" platforms.

Re: The birth of Microsoft's new web rendering engine

#220

Post by 72deluxe »

hyperbovine wrote: post #24

> Finally. This is the Microsoft I've been waiting for! ... Microsoft is going to use its muscle and position to make a truly competitive browser. Oh-ho man, what I wouldn't give to teleport this comment back to 1997 or so...

Haha very true. It reminds me of the time Apple announced that Internet Explorer was going to be the browser for classic Mac OS, with Bill Gates calling in, to shouts of NO!!! NO!!!!! NO!!!!

It makes me chuckle. It always boggles the mind that the web is mostly just rendering of documents and flinging backwards and forwards of requests, yet the passion it invokes with browser wars and web developers. A browser is essentially a HTML Help File viewer yet you get followings and wars! It doesn't make sense.

Even less sense is made when they reinvent all application features in a web browser to make web pages behave like desktop applications. Kind of useful, but an incessant broken/fix/reimplement cycle

Post reply on HN