4 ms·

If you don't care about the default telemetry and ads, switch to Windows 10 with WSL. I was a die hard Mac user for a decade and since switching I haven't looke

by pault 7y ago

If you don't care about the default telemetry and ads, switch to Windows 10 with WSL. I was a die hard Mac user for a decade and since switching I haven't looked back. Windows is a different beast than it was 10 years ago, and having the whole ecosystem of hardware and software at your disposal is fantastic.

nsriv 7y ago
I blocked telemetry through hosts file blocking as detailed here, might be helpful to some. https://www.thurrott.com/forums/microsoft/windows/thread/disabling-windows-10-telemetry https://www.thurrott.com/forums/microsoft/windows/thread/dis...
hiram112 7y ago
I still am trying to figure out what WSL has solved for anyone. It works fine for the little tutorials they use to showcase it, but on any real project it is just as bad as what many of us have had to do for the last 10 years if we were stuck with Windows: use a VM with all the problems it brings like using extra CPU and memory, poor filesystem performance, duplicating tools and configs in both the Windows and Linux environments, etc.
- pault 7y ago
  I'm not sure what your threshold is for a real project, but I've been using it for multi-stack dev environments with no trouble at all for the past year. You shouldn't use it to host a production environment, but I'm not sure why you would want to. What it solves is you don't have to use the minority, poorly supported windows ports of your language runtime, if it even has one. Many smaller languages I've tried don't support windows at all, and many NPM libraries have terrible bugs in windows (hard coding posix paths/environment variables, etc). WSL allows you to skip all of that trouble and use windows without changing any of your workflows or having to learn a totally new shell. The upcoming 2.0 release should be even better.
  - hiram112 7y ago
    I'm definitely not running a production environment. But imagine this scenario: I've got my Linux shell with various tools like GIt, JDK, NPM, NVM, Maven, etc. All the config files are setup in my Linux home in the VM. But the whole point of WSL is that I can use the nice GUIs available on Windows. So now I've SourceTree for Git, IntelliJ, WebStorm, etc running on Windows. And they all need the same tools installed like maven, Git, JDK, etc. First problem is that the I now have to duplicate all the tools in both Windows and Linux - all sorts of fun problems when they get out of sync. Same with the config files which are always screwing up due to differences in line endings and path slashes. But the worst of all is performance. If I compile some huge multi-module Scala and Java project completely in native Windows, it takes five minutes. Doing it in WSL bash takes 15 minutes. And having my IDE in Windows doing it on the code that's on the Linux WSL filesystem takes 60 minutes, assuming it even works with all the path and line ending problems as the tools are sometimes called in Windows, sometimes called in Linux. Exact same problems with python apps, Node apps, and everything else that is common these days. It's absolutely no better than what I did 10 years ago when I had my company spend $200 for VMWare Workstation license and I ran Fedora or Ubuntu VMs with Linux, but still tried to use Windows for half the build. Same with Cygwin...
    - pault 7y ago
      > But the whole point of WSL is that I can use the nice GUIs available on Windows. I think the point is that you can have a linux environment on your windows machine without running your own VM, not that you can use GUIs for your platform back end. If I just wanted GUIs I would use Mac OS. The real godsend of WSL is that we poor souls who are forced to use windows machines at work can finally have a development environment that isn't a second class citizen (assuming you aren't a windows platform developer). I'm not sure that it's fair to say that WSL doesn't solve anything for anyone just because it doesn't fit your workflow. I run node, haskell, and python in WSL and VSCode remote development extensions provides me with a full featured IDE for each of those environments, along with git integration if I should need it. Usually I just open up a terminal when I need to use git. Anyway, the next version of WSL will host a full linux kernel, so it should be easier to use X forwarding if you need linux-native GUI applications.
- GioM 7y ago
  One example, Qiime[1] can now run on windows via WSL. Much faster than the previous best solution, which was virtualbox. [1] https://qiime2.org/ https://qiime2.org/
jammygit 7y ago
If you do care about the telemetry and ads, try a Linux computer
mcyukon 7y ago
As well as the other methods in this thread, check out Windows Privacy Dashboard. It's got a simple toggle to turn off almost everything ad/privacy/telemetry related you can think off. https://wpd.app/ https://wpd.app/

by pault 7y ago

nsriv 7y ago

I blocked telemetry through hosts file blocking as detailed here, might be helpful to some. https://www.thurrott.com/forums/microsoft/windows/thread/disabling-windows-10-telemetry https://www.thurrott.com/forums/microsoft/windows/thread/dis...

hiram112 7y ago

I still am trying to figure out what WSL has solved for anyone. It works fine for the little tutorials they use to showcase it, but on any real project it is just as bad as what many of us have had to do for the last 10 years if we were stuck with Windows: use a VM with all the problems it brings like using extra CPU and memory, poor filesystem performance, duplicating tools and configs in both the Windows and Linux environments, etc.

pault 7y ago
I'm not sure what your threshold is for a real project, but I've been using it for multi-stack dev environments with no trouble at all for the past year. You shouldn't use it to host a production environment, but I'm not sure why you would want to. What it solves is you don't have to use the minority, poorly supported windows ports of your language runtime, if it even has one. Many smaller languages I've tried don't support windows at all, and many NPM libraries have terrible bugs in windows (hard coding posix paths/environment variables, etc). WSL allows you to skip all of that trouble and use windows without changing any of your workflows or having to learn a totally new shell. The upcoming 2.0 release should be even better.
- hiram112 7y ago
  I'm definitely not running a production environment. But imagine this scenario: I've got my Linux shell with various tools like GIt, JDK, NPM, NVM, Maven, etc. All the config files are setup in my Linux home in the VM. But the whole point of WSL is that I can use the nice GUIs available on Windows. So now I've SourceTree for Git, IntelliJ, WebStorm, etc running on Windows. And they all need the same tools installed like maven, Git, JDK, etc. First problem is that the I now have to duplicate all the tools in both Windows and Linux - all sorts of fun problems when they get out of sync. Same with the config files which are always screwing up due to differences in line endings and path slashes. But the worst of all is performance. If I compile some huge multi-module Scala and Java project completely in native Windows, it takes five minutes. Doing it in WSL bash takes 15 minutes. And having my IDE in Windows doing it on the code that's on the Linux WSL filesystem takes 60 minutes, assuming it even works with all the path and line ending problems as the tools are sometimes called in Windows, sometimes called in Linux. Exact same problems with python apps, Node apps, and everything else that is common these days. It's absolutely no better than what I did 10 years ago when I had my company spend $200 for VMWare Workstation license and I ran Fedora or Ubuntu VMs with Linux, but still tried to use Windows for half the build. Same with Cygwin...
  - pault 7y ago
    > But the whole point of WSL is that I can use the nice GUIs available on Windows. I think the point is that you can have a linux environment on your windows machine without running your own VM, not that you can use GUIs for your platform back end. If I just wanted GUIs I would use Mac OS. The real godsend of WSL is that we poor souls who are forced to use windows machines at work can finally have a development environment that isn't a second class citizen (assuming you aren't a windows platform developer). I'm not sure that it's fair to say that WSL doesn't solve anything for anyone just because it doesn't fit your workflow. I run node, haskell, and python in WSL and VSCode remote development extensions provides me with a full featured IDE for each of those environments, along with git integration if I should need it. Usually I just open up a terminal when I need to use git. Anyway, the next version of WSL will host a full linux kernel, so it should be easier to use X forwarding if you need linux-native GUI applications.
GioM 7y ago
One example, Qiime[1] can now run on windows via WSL. Much faster than the previous best solution, which was virtualbox. [1] https://qiime2.org/ https://qiime2.org/

jammygit 7y ago

If you do care about the telemetry and ads, try a Linux computer

mcyukon 7y ago

As well as the other methods in this thread, check out Windows Privacy Dashboard. It's got a simple toggle to turn off almost everything ad/privacy/telemetry related you can think off. https://wpd.app/ https://wpd.app/