5 ms·

This is BIG for machine learning adoption! 2 years ago it was a nightmare to setup everything on a Windows box, and wasn't working in any VMs (WSL or VirtualBox

This is BIG for machine learning adoption! 2 years ago it was a nightmare to setup everything on a Windows box, and wasn't working in any VMs (WSL or VirtualBox). Very excited about this.

black_puppydog 6y ago
This feels like it's gonna be terrible for people already doing ML. Now, the following has more than a bit of elitism, I'm aware of that, so please don't comment to point that bit out... I'm afraid that searching for answers to specific ML questions will start feeling like trying to google some Windows problems (every few years when I make the mistake of trying to help someone out) where it's all "download this, then click here..." I hope I'm wrong and this will only be used by people willing to go the extra mile...
- Tenoke 6y ago
  Doubt it. Even though you can run e.g. anaconda or pandas on Windows if I google an issue, I have no provlem getting linux-relevant results.
- cma 6y ago
  Hope we don't see things like: "Google announces today that to work around Windows' file path length limitations, Tensorflow's directory structure is being rewritten to use three characters or less per directory."
  - avandvrnot 6y ago
    What sold me on NT 3.1 was the in-the-box Microsoft Transaction Server. MTS is the single largest reason why SQLServer_Linux was a shoehorn refit, not anything like the job that it could have been. Out of the box CICS interop was bigger than my memory of the first browsers for W/NT. Want to trade with the world and speak EDIFACT, or do X.500 real money movement? You had codes running before you could put the screws on your local IBM account rep to get out of bed for you. I last looked at HN just as Lockdown was announced in England. The last discussion I perused was showing a project that provided secure remote access to sensitive ports. Which I think is stable CICS fayre since about ‘85 on the cross platform side I would guess at least twenty years older for anything/360.
  - washadjeffmad 6y ago
    I recently helped a friend with their museum's collection management software. The server and client were Windows based, and even with the proper dependencies and provisioning, the installs kept failing. Some of the paths were too long and the installer could only be executed after being unpacked to root. It's been a while since I more than casually gutted and used Windows as an app container, but I hadn't realized how much has remained the same after more than two decades.
    - int_19h 6y ago
      Windows itself can deal with long paths for a long time now. The problem is the apps - they need to use newer APIs that don't e.g. deal with structs with wchar_t[MAX_PATH] fields in them. For apps written in higher-level languages, it's usually the standard library that needs to be updated - e.g. Node.js and Python already have such support. But if it's C++, then it depends on how much the app developer cares.
- speedgoose 6y ago
  Don't be too elitist and scared, machine learning developers using Cuda and WSL are far from the windows non technical average user. You can take a look at the Github issues for Microsoft's projects related to WSL if you don't believe me. They are normal developers like you and me.
- emsal 6y ago
  What's scary about Googling for specific ML questions beginning to look like googling some Windows problems? This kind of dichotomy already exists between people who interact with ML only through keras and those who use a more flexible library. If you fall into the latter category it's still easy enough to find the answers to ML questions that mostly pertain to the deeper stuff. Don't even get me started on the difference between people who do and don't know statistics theory. But the point is that all of these groups do ML and they coexist just fine. On another note. I don't think technical proficiency (or whatever your elitism-metric is) is very correlated with using Windows as the primary platform. You can Google stuff related to a Windows problem and through that learn how to work with the registry, and yes, some of the things you need to do require you to RTFM. So this elitism also suffers from being off the mark.
curiousgal 6y ago
Other than C# and other Microsoft specific stacks, I've found coding on Windows to be absolutely horrible compared to Linux.
- wvenable 6y ago
  Agreed. But with WSL you're no longer shoehorning Linux software into Windows, you're running Linux software on Linux within Windows.
- kyberias 6y ago
  Can you be more specific? What exactly is horrible on Windows when you've tried coding?
  - deleuze 6y ago
    - Powershell sucks - Graphical installers / no package manager - No search results / docs for most languages - Weird bugs due to being second class for most languages - Have to use docker in VM - Bad env for writing scripts - We deploy on Linux
    - Kipters 6y ago
      Some of these are fixed or there's progress being made: - IMHO PowerShell is not that bad, but the newer PowerShell Core works better and with WSL you can use your favorite linux shell (and mix and match Windows and Linux binaries) - WinGet is in preview - No search results: my experience is 50/50 on that - second class citizen: I wouldn't say most, definitely for Golang - Docker now runs on WSL2 (which is still a sort of VM, but in my experience it's night and day with the old VM and especially compared to the default Docker experience on macOS) - Why? You can use Python, and scripts are where Powershell really shines as a language - That's the entire point of WSL I guess
      - FridgeSeal 6y ago
        PowerShell is horrible and confusing to use. Maybe I’m just dumb, but it was confusing to learn and super unintuitive. If I’m running everything in WSL/2 why not just run Linux? I don’t remember the last time I had to use something windows specific - and word is available online for the sporadic times that needs to be used.
alerighi 6y ago
I mean there are services like Amazon AWS, Azure, Google Cloud that will set up everyting for you. The money you pay them to me is worth the time you otherwise would have spent to do the setup yourself.

This is BIG for machine learning adoption! 2 years ago it was a nightmare to setup everything on a Windows box, and wasn't working in any VMs (WSL or VirtualBox). Very excited about this.

black_puppydog 6y ago

This feels like it's gonna be terrible for people already doing ML. Now, the following has more than a bit of elitism, I'm aware of that, so please don't comment to point that bit out... I'm afraid that searching for answers to specific ML questions will start feeling like trying to google some Windows problems (every few years when I make the mistake of trying to help someone out) where it's all "download this, then click here..." I hope I'm wrong and this will only be used by people willing to go the extra mile...

Tenoke 6y ago
Doubt it. Even though you can run e.g. anaconda or pandas on Windows if I google an issue, I have no provlem getting linux-relevant results.
cma 6y ago
Hope we don't see things like: "Google announces today that to work around Windows' file path length limitations, Tensorflow's directory structure is being rewritten to use three characters or less per directory."
- avandvrnot 6y ago
  What sold me on NT 3.1 was the in-the-box Microsoft Transaction Server. MTS is the single largest reason why SQLServer_Linux was a shoehorn refit, not anything like the job that it could have been. Out of the box CICS interop was bigger than my memory of the first browsers for W/NT. Want to trade with the world and speak EDIFACT, or do X.500 real money movement? You had codes running before you could put the screws on your local IBM account rep to get out of bed for you. I last looked at HN just as Lockdown was announced in England. The last discussion I perused was showing a project that provided secure remote access to sensitive ports. Which I think is stable CICS fayre since about ‘85 on the cross platform side I would guess at least twenty years older for anything/360.
- washadjeffmad 6y ago
  I recently helped a friend with their museum's collection management software. The server and client were Windows based, and even with the proper dependencies and provisioning, the installs kept failing. Some of the paths were too long and the installer could only be executed after being unpacked to root. It's been a while since I more than casually gutted and used Windows as an app container, but I hadn't realized how much has remained the same after more than two decades.
  - int_19h 6y ago
    Windows itself can deal with long paths for a long time now. The problem is the apps - they need to use newer APIs that don't e.g. deal with structs with wchar_t[MAX_PATH] fields in them. For apps written in higher-level languages, it's usually the standard library that needs to be updated - e.g. Node.js and Python already have such support. But if it's C++, then it depends on how much the app developer cares.
speedgoose 6y ago
Don't be too elitist and scared, machine learning developers using Cuda and WSL are far from the windows non technical average user. You can take a look at the Github issues for Microsoft's projects related to WSL if you don't believe me. They are normal developers like you and me.
emsal 6y ago
What's scary about Googling for specific ML questions beginning to look like googling some Windows problems? This kind of dichotomy already exists between people who interact with ML only through keras and those who use a more flexible library. If you fall into the latter category it's still easy enough to find the answers to ML questions that mostly pertain to the deeper stuff. Don't even get me started on the difference between people who do and don't know statistics theory. But the point is that all of these groups do ML and they coexist just fine. On another note. I don't think technical proficiency (or whatever your elitism-metric is) is very correlated with using Windows as the primary platform. You can Google stuff related to a Windows problem and through that learn how to work with the registry, and yes, some of the things you need to do require you to RTFM. So this elitism also suffers from being off the mark.

curiousgal 6y ago

Other than C# and other Microsoft specific stacks, I've found coding on Windows to be absolutely horrible compared to Linux.

wvenable 6y ago
Agreed. But with WSL you're no longer shoehorning Linux software into Windows, you're running Linux software on Linux within Windows.
kyberias 6y ago
Can you be more specific? What exactly is horrible on Windows when you've tried coding?
- deleuze 6y ago
  - Powershell sucks - Graphical installers / no package manager - No search results / docs for most languages - Weird bugs due to being second class for most languages - Have to use docker in VM - Bad env for writing scripts - We deploy on Linux
  - Kipters 6y ago
    Some of these are fixed or there's progress being made: - IMHO PowerShell is not that bad, but the newer PowerShell Core works better and with WSL you can use your favorite linux shell (and mix and match Windows and Linux binaries) - WinGet is in preview - No search results: my experience is 50/50 on that - second class citizen: I wouldn't say most, definitely for Golang - Docker now runs on WSL2 (which is still a sort of VM, but in my experience it's night and day with the old VM and especially compared to the default Docker experience on macOS) - Why? You can use Python, and scripts are where Powershell really shines as a language - That's the entire point of WSL I guess
    - FridgeSeal 6y ago
      PowerShell is horrible and confusing to use. Maybe I’m just dumb, but it was confusing to learn and super unintuitive. If I’m running everything in WSL/2 why not just run Linux? I don’t remember the last time I had to use something windows specific - and word is available online for the sporadic times that needs to be used.

alerighi 6y ago

I mean there are services like Amazon AWS, Azure, Google Cloud that will set up everyting for you. The money you pay them to me is worth the time you otherwise would have spent to do the setup yourself.