2,116 karma · joined June 2, 2012
Hopefully Microsoft releases a small batch of developer-focused Neo's for developers that want to get a head start building for dual-screen devices.
That being said, your general point that there's so many ways to develop an app for Windows, and that not all of them support the same features, is definitely true. I think the general advice these days is that if you _can_ build your app as a UWP, do that. Otherwise, use the Win32 APIs as sparingly as possible, defaulting to the UWP APIs. Legacy apps are a bit trickier, and that's where Microsoft is investing in things like the Desktop Bridge (run Win32 apps in a UWP container) and XAML Islands (host UWP controls in a Win32 app).
[1] https://docs.microsoft.com/en-us/windows/uwp/audio-video-cam...
This is still the current state of WebAssembly. There's several proposals out there that, if implemented, could change the situation. The primary one that I'm aware of is the interface types proposal [1].
[1] https://github.com/WebAssembly/interface-types/blob/master/p...
Again, the number of people who this impacts is so small that it's hardly significant. Sure, here on HN I'm sure it seems that everyone is confused, but we're hardly a representative sample here.
> has trademark problems
Honestly I don't buy this. When you trademark something, you do so in a very specific manner, and I think Screen's market is specific enough as to defend a trademark in the screen sharing/collaboration segment _should they even choose to trademark the name_, which they can easily choose not to do.
If you're intelligent enough to use screen, surely you're intelligent enough to understand the difference between a terminal app and an app that shares your screen.
This is an issue with that particular website's implementation, not something inherent to the browser or the API.
Source: https://www.windowscentral.com/surface-duo-spring-summer-ear...
As far as I can tell, there's no new information on the linked page, so I'm not sure why it's resurfacing (ba dum tisss).
The biggest difference I see between them is that Replicache sits in front of your server, whereas Kinto _is_ your server.
Disclosure: I'm a contributor to Kinto, primarily working on transitioning the JavaScript libraries to TypeScript.
Apart from that, I do really enjoy all the screen real estate. It's nice to be able to have a full-sized browser window and two instances of VS Code all running within a visible portion of the screen. That being said, I'd easily give it up for a reasonably priced 27in 5K display that works over DisplayPort. The extra screen space is nice, but I'd much rather a display that had crisp, high-DPI text.