3 ms·
I think the biggest reason why this is important to most people isn't the performance of JS in IE/Edge, but rather for the native html/js apps. A lot of people
by jjcm 10y ago
I think the biggest reason why this is important to most people isn't the performance of JS in IE/Edge, but rather for the native html/js apps. A lot of people don't realize that a lot of the new windows 10 features were written in html/js. Native components like the start menu are all html5 (one of the few things for windows desktop that I helped ship).
Curious to see if more of the UI gets converted over as performance continues to improve.
- CommanderData 10y agoCare to elaborate on the start menu? I couldn't find any info the start menu being html5, maybe I understood that incorrectly. I'd love to read more about that maybe a blog or article. Thanks.
- mwcampbell 10y agoAs far as I can tell, the Start menu in Windows 10 is XAML, not HTML.
- ClassyJacket 10y agoWow, it's really HTML? That seems crazy to me, for performance and customisability (on Microsoft's end) reasons. Can you share the motivation behind that? Since the Start Menu is obviously not something that needs to be multiplatform, it doesn't require that strength of HTML.
- frik 10y agoThe Win10 startmenu is coded in C++ with XAML. A few months ago, the proud dev mentioned it here on HN - he mentioned he was proud how responsive the layout is. A HTML5 responsive design page would be have a more responsive layout reflow and won't fill that static.
- shultays 10y agoIt certainly does not feel fast at all. As far as I remember start menus were instant. Now it is not. Much better than those monstrosity at windows 8 though.
- iLoch 10y agoOh that's why it's so slow.
- pjmlp 10y agoI very much doubt that, given the presentations at Build about the start menu features.
- agumonkey 10y agoIt might not be obvious but a lot of the 98/XP shell was html/js in disguise. And even before that, 95a had active desktop IIRC. Progress.