News for hackers. Stuff that matters.

A comment on Closing a 30 pixel gap between native and web. Parent comment

Re:Closing a 30 pixel gap between native and web by mdmglr on Wednesday September 28, 2022 @12:31AM (#33004265)
> Even Office and Visual Studio (not Code) are using web technologies to render substantial parts of the UI.

Any more details on what web technologies are being used in Visual Studio and what parts of the UI are done with web?

[ Parent | on HN ]
Re:Closing a 30 pixel gap between native and web by fuzzy2 on Wednesday September 28, 2022 @07:32AM (#33006748)
The Diagnostic Tools window is implemented as a web view, probably since its introduction in… VS2017?. I’m not aware of any other GUI parts implemented using web technologies.

Node.js processes are invisible backend stuff.

[ Parent | on HN ]
Re:Closing a 30 pixel gap between native and web by n8cpdx on Wednesday September 28, 2022 @01:59PM (#33011046)
This is what I was thinking of. Kind of a telling statement of Microsoft’s perception of WPF when they turn to WebView2 to render newer parts of the UI in their WPF app (which was never ported to WinRT, UWP, or WinUI). They didn’t even use XAML islands for the newer parts, they just jumped straight to web.
[ Parent | on HN ]
Re:Closing a 30 pixel gap between native and web by pjmlp on Wednesday September 28, 2022 @02:33AM (#33004863)
You just have to peek into what is running as child process from VS, as node.exe instances.

Mostly related to Web stuff, Blazor or VSCode plugins that they are "porting" into VS.

[ Parent | on HN ]