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

Closing a 30 pixel gap between native and web

blogs.windows.com

Post reply on HN
Print view View original

21–30 of 313 posts

Re: Closing a 30 pixel gap between native and web

#21

Post by loudmax »

MaXtreeM wrote: post #6

With all this Electron and PWA focused development a cannot shake a feeling that we add an extra layer of a "runtime" on top of an operating system, that could be avoided. An extra layer which occupies RAM space and processor time which feels unnecessary but it is where we are headed. I wonder if the reason is simple, that we (myself included) have not provided anything better or the reason is that big corporations w…

The bottom line is that Electron is portable. Unless native apps become as portable as Electron there will be a need for this layer.

The optimistic scenario is that WASM becomes the single target that everyone settles on, and that the performance penalty is minimized while the security sandbox is strengthened.

Re: Closing a 30 pixel gap between native and web

#22

Post by jonathankoren »

intrasight wrote: post #19

> ability to create their own title bar experiences It was a sad day, IMHO, in UX-world when this became possible in desktop apps. The window system should own the chrome and the apps should not be able to touch it.

Looking forward to the day when Winamp style apps are back.

Remember round windows? They’re back, in Electron form.

Re: Closing a 30 pixel gap between native and web

#23

Post by gildas »

tshaddox wrote: post #20
gildas wrote: post #16

Earlier quoted context omitted.

And then a shady company offers to buy the owner's website...

That’s a real problem, of course, but it seems fairly equivalent to any native app you install that can update itself or otherwise make a network request to obtain instructions.

I agree with you. On the other hand, in the case of a native application, we can hope that the antivirus removes it. I hope that Microsoft has planned to update Defender accordingly.

Re: Closing a 30 pixel gap between native and web

#24

Post by amadeuspagel »

MaXtreeM wrote: post #6

With all this Electron and PWA focused development a cannot shake a feeling that we add an extra layer of a "runtime" on top of an operating system, that could be avoided. An extra layer which occupies RAM space and processor time which feels unnecessary but it is where we are headed. I wonder if the reason is simple, that we (myself included) have not provided anything better or the reason is that big corporations w…

The obvious solution to this is to remove the bottom layer so that the browser is not a layer on top of the OS, but is the OS.

Re: Closing a 30 pixel gap between native and web

#25

Post by echelon »

dmayle wrote: post #12

I think this is a sign that Microsoft sees the writing on the wall. There will be a day when Windows is left behind, and they want to make sure that they can continue to deliver the Microsoft experience, even on other platforms.

I think this is the wrong take.

Microsoft is trying to land on the PWA beachhead in an attempt to make mobile devices irrelevant and app agnostic.

Furthermore, they want to provide the tooling to develop and deploy into this ecosystem. Github, Github CI, VSCode, Azure, ...

Re: Closing a 30 pixel gap between native and web

#29

Post by ieegdiuf »

guhidalg wrote: post #18
dmayle wrote: post #12

I think this is a sign that Microsoft sees the writing on the wall. There will be a day when Windows is left behind, and they want to make sure that they can continue to deliver the Microsoft experience, even on other platforms.

I don’t think Windows is ever going to be left behind, you still need a kernel to make use of all your hardware and an OS to give users something to do. I view this move as Microsoft recognizing that the future of most development is cross-platform web technologies and they need to give Windows users reasons not to migrate to macOS and ChromeOS (though it’s ok if they do as long as they’re paying for O365 and Azure).

No post body was provided.
Post reply on HN