Porting a macOS Clojure Dev Setup to Windows WSL2

Re:Porting a macOS Clojure Dev Setup to Windows WSL2 by diffeomorphism on Tuesday July 28, 2020 @01:01PM (#23977952)

Windows: Still has no package manager. Setting all software up takes time. Hardware was done by the laptop manufacturer, don't know how much work that would be. Works fine for the most part. Keyboard, mouse, wacom etc require a bit of fiddling.

Linux: Software setup is really easy. All hardware worked out of the box.

MacOS: Reading instructions, preparing installer etc. Got it "working" in a VM but without graphics accel, which makes it not really useful.

Time lost: A few hours more for windows, but quite comparable.

[ Parent | on HN ]

Re:Porting a macOS Clojure Dev Setup to Windows WSL2 by boogies on Tuesday July 28, 2020 @01:56PM (#23978692)

There technically is a “Windows package manager” https://github.com/microsoft/winget-cli, though it doesn't manage installed packages yet (that seems to be planned for v1.0 sometime next year https://github.com/microsoft/winget-cli/blob/master/doc/wind...).

[ Parent | on HN ]

Re:Porting a macOS Clojure Dev Setup to Windows WSL2 by jamesgeck0 on Wednesday July 29, 2020 @02:10PM (#23989806)

Windows has like six 3rd party package managers. Chocolatey and Scoop have large repos and have been around since Windows 8. Modern Windows devices ship with the specific drivers required for the hardware and download drivers for unknown hardware automatically. Building my gaming PC from scratch, I didn't have to manually install drivers for anything. I've never even heard of a keyboard/mouse that didn't work out of the box.

[ Parent | on HN ]