5 ms·
And they can typically setup their dev environment without a VM, while also getting commercial app support if they need it. Windows requires a VM, like WSL, fo
by al_borland 3y ago
And they can typically setup their dev environment without a VM, while also getting commercial app support if they need it.
Windows requires a VM, like WSL, for a lot of people, and Linux lacks commercial support. macOS strikes a good balance in the middle that makes it a pretty compelling choice.
- pineaux 3y agoWSL is not a VM. Edit: TIL WSL2 is a VM. I develop on mac and linux computers so should have kept my mouth shut anyways
- worthless-trash 3y agoHey, you learned and corrected yourself, dont be so hard on yourself mate.
- tomcam 3y agoUsername highly inaccurate ;)
- tomcam 3y agoDownloaded for complimenting GP? Stay classy, Hacker News
- ddingus 3y agoSeriously! I agree. They just modeled the best discussion with some of the highest value there is. Being wrong is no big deal. Being unable to be right is often a very big deal.
- shandor 3y agoJust to make sure your TIL is complete, do note that Linux containers are VMs also on MacOS :)
- ensignavenger 3y agoThere are a plethora of companies offering commercial support for various Linux distributions.
- al_borland 3y agoI was thinking more about software like the Adobe suite, Microsoft Office, or other closed source software that hasn’t released on Linux. Electron has made things a bit better, but there are still a lot of bigs gaps for the enterprise, unless the company is specifically choosing software to maintain Linux support for end users. Sure, Wine exists, but it’s not something I’d want to rely on for a business when there are alternatives like macOS which will offer native support.
- rob74 3y agoMost people don't need the Adobe Suite, and the web version of M$-Office is more than Ok for occasional use. Most other enterprise software are web apps too nowadays, so it's much less relevant what OS your machine is running than it was ten years ago...
- seec 3y agoYep, that's pretty much it. Apple fanboys like to talk about how cool and long lasting a MacBook Air is but a 500 bucks Chromebook will do just as well while allowing pretty much 90% of the use cases. Sure, the top end power is much lower but at the same time considering the base RAM/storage combo Apple gives it is not that relevant. If you starting loading it up, that puts the pricing in an entirely different category and in my opinion the MacBook Air becomes seriously irrelevant when compared to serious computing devices in the same price range...
- close04 3y agoThere's still a huge market for people who want higher end hardware and to run workloads locally, or put a higher price on privacy. For people who want to keep their data close to their chest, and particularly now with the AI bloom, being able to perform all tasks on device is more valuable than ever. A Chromebook "does the job" but it's closer to a thin client than a workstation. A lot of the job is done remotely and you may not want that.
- overgard 3y agoIf you mean WSL for containers, macOS needs a VM too. If youre doing C++ macOS dev tools are .. bleak. Great for webdev though
- al_borland 3y agoWSL for normal stuff. My co-worker is on Windows and had to setup WSL to get a linter working with VS Code. It took him a week to get it working the first time, and it breaks periodically, so he needs to do it all over again every few months.
- trimethylpurine 3y agoI'm developing on Windows for Windows, Linux, Android, and web, including C, Go, Java, TSQL and MSSQL management. I do not necessarily need WSL except for C. SSH is built directly into the Windows terminal and is fully scriptable in PS. WSL is also nice for Bash scripting, but it's not necessary. It is a check box in the "Add Features" panel. There is nothing to install or setup. Certainly not for linting, unless, again, you're using a Linux tool chain. But if you are, just check the box. No setup beyond VS Code, bashrc, vimrc, and your tool chain. Same as you would do on Mac. If anything, all the Mac specific quirks make setting up the Linux tool chains much harder. At least on WSL the entire directory structure matches Linux out of the box. The tool chains just work. While some of the documentation is in its infancy, the workflow and versatility of cross platform development on Windows, I think, is unmatched.
- davrosthedalek 3y agoThis. I have to onboard a lot of students to our analysis toolchain (Nuclear Physics, ROOT based, C++). 10 years ago I prayed that the student has a Mac, because it was so easy. Now I pray they have Windows, because of WSL. The tool chain is all compiled from source. Pretty much every major version, but often also minor versions, of macos break the compilation of ROOT. I had several release upgrades of Ubuntu that only required a recompile, if that, and it always worked.
- 3y ago
- forty 3y agoWhat do you mean without a VM? I guess you don't count docker/podman as VMs then?
- BytesAndGears 3y agoLikely that most devs want to use Unix tools — terminal, etc.
- dualboot 3y agoThose aren't VMs -- they're containers.
- Hasu 3y agoOnly on Linux - on MacOS and Windows, you have to do virtualization for containers.
- anticensor 3y agoUnless you do use WSL1 as your container runner. Nobody does this but I do not get why.
- CoolCold 3y agoI hardly can imagine how it works for you, because WSL1 basically lacks any option for containers be it namespaces or cgroups? Netfilter? Bridges? Feel free to correct me and share successfull cases with wsl1 and containers