> their Mac set up is all sorts of broken and buggy. I can hear legit sadness in their voice.

I'm normally very happy with the dev experience on my 2016 MacBook Pro. I run iTerm2 (multiple split panes in a window), zsh/ohmyzsh, homebrew, and VSCode. The new APFS filesystem is insanely fast, especially when combined with VSCode's ripgrep-based text search. I watch my Windows-based colleagues start a VSCode text search in our repo and it takes 10-15 seconds to complete. Me - it's usually less than 5 seconds and often instant. Also, moving/copying/deleting large directories (i.e. 25k+ files) is unbelievably fast.

So macOS is great, in my opinion. But I'm often frustrated with this machine: (a) the keyboard is unreliable - certain keys develop habits of not responding (the `fn` key is currently driving me round the bend), (b) it crashes every time the battery runs low, and (c) my corporate policy installs Sophos which sometimes slows it to an absolute crawl.

From many developers' perspective, Windows' greatest downfall is that it's, well, still Windows. There is so much legacy to maintain, and so many ways that it differs from macOS and Linux at low levels. WSL and the new terminal/PTY are making inroads, but if Microsoft would only fork Debian and build their own supported distro, I can guess that's where we'd all be going very soon. What if they forked Wine as well and built a supported Windows compatibility layer on top?

> The new APFS filesystem is insanely fast, especially when combined with VSCode's ripgrep-based text search.

I think this must be due to the NVMe drives they use in MacBook Pros. APFS has some performance overhead that makes it slightly slower than HFS+ (but I do think you get other improvements, when copying files etc.).

I own a 2014 MBP I use as my main work laptop. I also own a desktop running Windows 10. I currently maintain a VSCode dev environment for my coworkers who all use Windows.

We switched from XAMPP and Eclipse for PHP development to WSL with VSCode and so far the transition has been really good. The only problem is that OS X still has a way better free MySQL client in the form of Sequel Pro compared to Windows which only has MySQL Workbench and HeidiSQL for the free options. I wish there was a better SQL client we could use.

There are tons of SQL clients for Windows.

Dbeaver, sqlyog (free edition) are a few more free ones that come to mind.

If you're willing to pay, TablePlus is pretty good.

Hey Nick. I'm the PM for Windows Terminal, and formerly, WSL:

Thanks for your thoughts on WSL & the new Terminal.

Re. release mechanisms, etc: Terminal will be delivered via the Store so we can ship out-of-band.

We're aiming to deliver new Terminal preview builds every 2 weeks or so which, since we're delivering via the Store, will auto-upgrade everyone soon after each release.

Re. Insiders: We do NOT gather any personally identifiable information. We only collect anonymized statistics about some of the features you use and/or issues you experience. Why? To ensure that we can find and fix issues as effectively as possible.

For example, with WSL, we collect the number of times an un-implemented syscall is called, or # of times a syscall returns an unexpected error. We couldn't care less WHO experiences these issues, only how OFTEN they occur. This info (esp. combined with bug reports in our repo, etc.) has been essential in helping us prioritize which syscalls are being called, which we've implemented, which are failing, and thus, which we need to pay attention to. Without this info, we wouldn't have been able to make WSL as good as it is.

We understand the community's concern about data collection - heck, EVERYONE should be - but in the general scheme of things, I think it fair to say that Microsoft's telemetry data collection is pretty well contained and is not egregious.

If you'd like to see what telemetry is being collected, on your machines, this may be of help: https://docs.microsoft.com/en-us/windows/privacy/diagnostic-...

HTH.

Hi,

The last time I tried to install insiders it mandated that I sign into Windows with a real Microsoft Live account, which requires an email address sign up.

Where as the stable version of Windows allows you to create an offline account.

If I sign in with a Microsoft Live account, now you can associate my email address to my OS usage stats. Isn't that the definition of personally identifiable data?

Also, you may have linked to the wrong sub-link. The page that lists what's tracked for insiders is this one I think? https://docs.microsoft.com/en-us/windows/privacy/windows-dia...

It mentions "User ID -- a unique identifier associated with the user's Microsoft Account (if one is used)". It also mentions collecting a bunch of low level network data that look questionable, such as IP addresses flowing through network devices. Isn't that saying "logs every website you visit"?

Then it mentions it logs every app I open and how long it was opened for, and even what I search for in those apps. I didn't go through the whole list in detail but that was what I saw in a 60 second scan of the page.

But on the topic of WSL, are you saying if we run Windows stable we'll be able to get and continuously update WSL v2 from the store? That would be neat.

I'm on OSX and I have to have a docker container up and running in order to do development. GNU v. BSD tooling just isn't cutting it, and that's actually (IMHO) what's stealing market share from OSX.

They got windows+linux users in the first place by pre-installing curl+ssh, now their version of ls, find, and bash are all holding back those same windows+linux users.

I use homebrew to install updated versions of gnu utilities. Sometimes it doesn't symlink them into /usr/local/bin because of potential conflicts with preinstalled versions, but you can override that by adding them to $PATH in your .bashrc or .zshrc - it provides the command to do so in the console.