3 ms·

Well, it's 2023 and a) most user-facing apps are browser-based, and b) development is done in WSL2 so not much of that matters and c) their x86 emulation is now

Well, it's 2023 and a) most user-facing apps are browser-based, and b) development is done in WSL2 so not much of that matters and c) their x86 emulation is now great. Source: using a Surface Pro X for all my work when traveling for 1y, and running dusty decks such as Quickbooks too.

pjmlp 3y ago
I am yet to do any development in WSL2.
- PaulHoule 3y ago
  I liked the old WSL back in the day. I've never really gotten traction w/ WSL2 between having a machine at work that is locked down so I can't install apps from the Windows store (hardly ever need to do that except for the occasional crapplet you need for a printer... and WSL2) and feeling completely comfortable running Linux in HyperV when I need to. My RSS reader YOShInOn is written in Python and hypothetically it could use multiprocessing, celery, and other stuff that would work better with WSL2, but I have it working just fine in ordinary windows and when I need to do something that doesn't fit will with the asyncio paradigm (long running CPU-bound tasks) I just open a pipe to a new process.
wongarsu 3y ago
As the owner of a Lenovo laptop with Qualcomm processor I agree (except that my development for the most part is outside WSL). Some of the drivers are immature, but on the application side the end user really doesn't notice. I couldn't tell you which applications are compiled for arm64 and which for amd64. And battery life is notably improved compared to intel. The development experience is a bit different, because you can run both arm64 and x64 toolchains, and of course everything has to match there. But that's not a big issue.
lionkor 3y ago
> most user-facing apps are browser-based maybe most new apps are browser based, but in terms of number of users per app, definitely not. If I look at the PC of any of my relatives or friends, the only stuff that isnt native is chat apps and the occasional weird poweruser tool. Most everyday work apps are native. > development is done in WSL2 so not much of that matters and thats also mostly a bubble phenomenon. a lot of development is done in visual studio, or some JetBrains product, vscode, and that's pretty much it. a lot of Linux devs run Linux, instead, too.
oldpersonintx 3y ago
> a) most user-facing apps are browser-based if MSFT admitted this they would be telling everyone that Chromebooks are a solution
- pjmlp 3y ago
  That is what rumors say Windows 12 is going to be, which is another reason for those of us that got burned with the whole WinRT/UAP/UWP mismanagement, to not care about WinUI 3.0 and the team's platry resources. https://www.tomshardware.com/news/microsoft-developing-chrome-os-like-version-of-windows-12-report https://www.tomshardware.com/news/microsoft-developing-chrom...

pjmlp 3y ago

I am yet to do any development in WSL2.

PaulHoule 3y ago
I liked the old WSL back in the day. I've never really gotten traction w/ WSL2 between having a machine at work that is locked down so I can't install apps from the Windows store (hardly ever need to do that except for the occasional crapplet you need for a printer... and WSL2) and feeling completely comfortable running Linux in HyperV when I need to. My RSS reader YOShInOn is written in Python and hypothetically it could use multiprocessing, celery, and other stuff that would work better with WSL2, but I have it working just fine in ordinary windows and when I need to do something that doesn't fit will with the asyncio paradigm (long running CPU-bound tasks) I just open a pipe to a new process.

wongarsu 3y ago

As the owner of a Lenovo laptop with Qualcomm processor I agree (except that my development for the most part is outside WSL). Some of the drivers are immature, but on the application side the end user really doesn't notice. I couldn't tell you which applications are compiled for arm64 and which for amd64. And battery life is notably improved compared to intel. The development experience is a bit different, because you can run both arm64 and x64 toolchains, and of course everything has to match there. But that's not a big issue.

lionkor 3y ago

> most user-facing apps are browser-based maybe most new apps are browser based, but in terms of number of users per app, definitely not. If I look at the PC of any of my relatives or friends, the only stuff that isnt native is chat apps and the occasional weird poweruser tool. Most everyday work apps are native. > development is done in WSL2 so not much of that matters and thats also mostly a bubble phenomenon. a lot of development is done in visual studio, or some JetBrains product, vscode, and that's pretty much it. a lot of Linux devs run Linux, instead, too.

oldpersonintx 3y ago

> a) most user-facing apps are browser-based if MSFT admitted this they would be telling everyone that Chromebooks are a solution

pjmlp 3y ago
That is what rumors say Windows 12 is going to be, which is another reason for those of us that got burned with the whole WinRT/UAP/UWP mismanagement, to not care about WinUI 3.0 and the team's platry resources. https://www.tomshardware.com/news/microsoft-developing-chrome-os-like-version-of-windows-12-report https://www.tomshardware.com/news/microsoft-developing-chrom...