Too bad you need wsl2, i hate running hyperv and the apps that dont play nice with it.
CUDA on Windows Subsystem for Linux 2
121–130 of 221 posts
Re: CUDA on Windows Subsystem for Linux 2
#122This is finally the year of the Linux desktop. However, it is running on Windows as WSL. With this support now for CUDA now, it can be argued that the best, most versatile developer experience is on Windows. You now have access to all the Windows specific tools (such as Visual Studio) as well as all the Linux tools in a very seamless environment.
plus telemetry!
Re: CUDA on Windows Subsystem for Linux 2
#123Pity. CUDA was/is proof positive that Linux on the desktop is perfectly feasible and that you can use it to both do a UI and do meaningful computation on the same machine without getting tied down into all kinds of licensing schemes. Opening this further up to Windows gives fewer people a really good reason to try out Linux as their daily driver. I personally don't get why any developer would prefer Windows over Linu…
First a developer you don't do only programming: you maybe have to work with documents, do a presentation, a spreadsheet and thus use Office. You maybe have to make some icons or logos and thus you need Adobe Illustrator. You maybe need to connect to a printer like the one that we have at my office that good luck doing that on Linux. You maybe need a CAD software to designa PCB, you need whatever other software that…
> ... other software that is Windows-only.
So, I guess when I use Office365 on my linux laptop, which is connected to a HiDPI monitor, that I can't do what you say.
Ok.
Here's a bit of a reality check. You can do, with very limited corner cases, everything you want to do on windows, on linux (and Mac) today, via the web or similar clients.
One exception to this is skype for business. Which is complete and utter trash anyway. But there is a commercial linux version, not by Microsoft, that works quite well for it. I have it and use it.
Teams for linux from Microsoft is in preview/beta. But, the port using electron was out first. And is fully operational.
For things that just absolutely require windows, I boot my licensed windows 10 home which was installed on a small SSD when I bought the laptop, in a qemu kvm window. Everything works on it.
I am amazed with all the hate on Linux desktops. I've been using Linux machines as my primary desktops, and linux laptops for more than 20 years. My current laptop is a Sager (Clevo) unit with 64 GB ram, 1.5TB SSD, GTX1060. Win10 was installed when I bought it, on an SSD. I changed boot order, installed Linux Mint 17.x at the time, and everything just worked.
Once I realized I could use windows from the qemu kvm session, I set that up. Took about 10 minutes.
Something I've learned from a long and painful life with windows, is that one should never let it touch real hardware. When you have to manage it versus fleets of linux machines, you understand why keeping it virtualized is the best option.
FWIW, I don't think WSL2 is going to change anyone's game. This is my opinion of course, but most of the developers I know are either on Mac books, or linux machines. About 60-40 split. In my field (HPC) its 25-75.
Microsoft's best play at this moment would be to buy Canonical, and offer that as MS Linux.
Re: CUDA on Windows Subsystem for Linux 2
#124Pity. CUDA was/is proof positive that Linux on the desktop is perfectly feasible and that you can use it to both do a UI and do meaningful computation on the same machine without getting tied down into all kinds of licensing schemes. Opening this further up to Windows gives fewer people a really good reason to try out Linux as their daily driver. I personally don't get why any developer would prefer Windows over Linu…
> I personally don't get why any developer would prefer Windows over Linux
I'll offer you one data point, for what it's worth.
We do multidisciplinary work on our workstations. That means electrical engineering (Altium Designer), mechanical engineering (Solidworks+CAM), embedded (Keil, Xilinx, Linux, NVidia Jetson, etc.), FEA (Solidworks Simulation), server-side development (Linux, Python, Django, etc.) and the myriad business documents that can go with all of that.
The traditional setup has been to custom build powerful Windows machines with as much memory as the mobo will support and half a dozen SSD's assigned to specific functions (system, data, library, hardware dev, software dev, virtual machines) and then build a bunch of task-specific virtual machines.
Using multiple (3+) monitors it is easy to live in this multi-OS/multi-paradigm world once you get it all setup.
Not quite using WSL yet but watching its development with great interest.
If all someone is doing is web development it used to be that either an Apple laptop or a dual-boot Windows/Linux machine was the top choice. WSL seems to be displacing Apple in this domain.
Re: CUDA on Windows Subsystem for Linux 2
#125Can someone explain to me the WSL acornym? Isn't WSL really a Linux subsystem for Windows? tiny pet peeve
Yeah, it's very confusing. I've heard it explained but I still think it doesn't really make sense. The core of the argument that I've heard is that Windows has multiple subsystems so they say it's a "Windows Subsystem", but the 'for' in "For Linux" still makes no sense.
The arguments for not calling it something like "Linux Subsystem [for/on/in] Windows" don't seem to match up with the fact that there used to be a similar thing which was called "Microsoft POSIX Subsystem" also.
Re: CUDA on Windows Subsystem for Linux 2
#126Having set this up, this is going to be absolutely huge for ML. A lot of nonsense is getting cut down by this: 1. You don't have to install special CUDA-specific drivers that are behind the normal gaming drivers anymore. You'll soon be able to just use the Regular nVidia Drivers (and even now, all you need to do is install a Beta driver version). That's huge for someone just starting out, they don't have to have "the…
I scanned through the comments. There is no editor war anymore these days ;) For development I wouldn't have issues as I just use VIM and CLI. Neovim currently has linting and auto-complete and works so much better then before. Actually also using the language server protocol same like vscode. So no issues on DPI. The other tool used is chrome and that handles DPI quite nicely on linux.
But I switched to mac long time ago. Because I agree it handles text and HDPI displays much better. Maybe windows improved on this but reading text on it was such a downgrade to a mac. If windows would have as nice text rendering as mac I would switch instantly. Cheaper hardware for better price and all. No have best of both worlds windows and linux all in one.
Re: CUDA on Windows Subsystem for Linux 2
#127Re: CUDA on Windows Subsystem for Linux 2
#128Having set this up, this is going to be absolutely huge for ML. A lot of nonsense is getting cut down by this: 1. You don't have to install special CUDA-specific drivers that are behind the normal gaming drivers anymore. You'll soon be able to just use the Regular nVidia Drivers (and even now, all you need to do is install a Beta driver version). That's huge for someone just starting out, they don't have to have "the…
I scanned through the comments. There is no editor war anymore these days ;) For development I wouldn't have issues as I just use VIM and CLI. Neovim currently has linting and auto-complete and works so much better then before. Actually also using the language server protocol same like vscode. So no issues on DPI. The other tool used is chrome and that handles DPI quite nicely on linux. But I switched to mac long tim…
The only time I see any HDPI issues on Win10 is when running ancient apps. It certainly works great in VSCode.
I'm not sure what you mean by "nice text rendering" - are you referring to ClearType vs macOS anti-aliasing? If so, that doesn't really come up for HDPI, because you can't see the artifacts either way.
Re: CUDA on Windows Subsystem for Linux 2
#129Earlier quoted context omitted.
I believe they meant PC as in PC (Windows) vs Mac. I've encountered a lot of people who use PC Windows Machine interchangeably.
"Personal Computer" has long been specifically associated with Windows machines and specifically excludes Mac and Linux. It started with the "IBM Personal Computer" and its branding caused non-IBM machines (eg Macintosh) to use other branding ("a mac"). When IBM partnered with Microsoft to make home computers, this branding really solidified that "PC = Windows". And then of course, there was the very successful adver…
I have been rather miffed that the lack of corporate branding/identity for Linux at the time when Macintosh decided to "distinguish" itself now means that GNU/Linux machines are apparently not "personal computers" anymore.
But if PC = IBM PC, and those basically always came with Microsoft software, I guess history supports that interpretation.
Re: CUDA on Windows Subsystem for Linux 2
#130Pity. CUDA was/is proof positive that Linux on the desktop is perfectly feasible and that you can use it to both do a UI and do meaningful computation on the same machine without getting tied down into all kinds of licensing schemes. Opening this further up to Windows gives fewer people a really good reason to try out Linux as their daily driver. I personally don't get why any developer would prefer Windows over Linu…
First a developer you don't do only programming: you maybe have to work with documents, do a presentation, a spreadsheet and thus use Office. You maybe have to make some icons or logos and thus you need Adobe Illustrator. You maybe need to connect to a printer like the one that we have at my office that good luck doing that on Linux. You maybe need a CAD software to designa PCB, you need whatever other software that…
A very fair and practical judgement. May use a mac and remote to windows as some linux egpu has driver issues bout not windows. Remote vs code from mac?