3 ms·

It's everything around baseline development that sucks when using WSL, not WSL itself. WSL itself is really cool. What's not cool is dealing with linters and co

It's everything around baseline development that sucks when using WSL, not WSL itself. WSL itself is really cool. What's not cool is dealing with linters and compiling tools and all the other bric-a-brac that has to cross the Windows/WSL divide. Some of them have been fixed to support WSL, others haven't, knowing which have and which haven't is a crapshoot, and WSL is a third-class citizen at best so good luck waiting on them. On top of that, all of the little things are wrong. MacOS/Linux aren't identical by any means but I expect (say) important configuration for everything, not just my things, to be accessible via my shell. My shell, by which I mean having to bail out into PowerShell (which is a bad acid trip) or into clicking stuff is just not gonna fly. I am not unfamiliar with or uncomfortable with Windows but it irks the hell out of me to have to bail out of my work environment to start clicking around or to `Start-OddCommands -WithSillyFlags` and there's no reason for it. When I ditched MacOS, I instead went to Fedora. (Which, I am told, does run quite well on a Surface Book.) There's a Windows partition on my work machine, but it's mostly just so I can run a DAW (Ardour is bleh, don't @ me) for remotely recording audio.

mattferderer 8y ago
Try Cmder.
- eropple 8y ago
  I've been using Cmder since shortly after its initial release. It doesn't step to either Tilix or iTerm2, depending on platform.
- GordonS 8y ago
  Another Cmder user here - I actually find it to be superior to any terminal I've used on MacOS.
  - raarts 8y ago
    In what way exactly?
owenwil 8y ago
All of those things were fine, as far as I can tell. What did you run into specifically? I could run npm stuff, compile with Gulp or webpack..
- eropple 8y ago
  It's been like six months since I tried, because Fedora does great for me now, but in Visual Studio Code Ruby/Rubocop threw a rod, using a Linux-based .NET Core confused it, and anything Java was a nonstarter. For JavaScript, I do usually run `yarn watch` (workspace-level through oao) in a terminal and that works fine, but stuff like eslint/tslint integrated into VSCode was regularly a real pain. Worse: because VSCode--and if it wasn't a Microsoft product I would be less annoyed, but it's their editor and their OS so they can own it too--doesn't really support per-platform configurations, working around it by disabling stuff on VSCode causes my settings sync solution to break my other machines...
  - rbanffy 8y ago
    > doesn't really support per-platform configurations It would be neat if the config file were JavaScript that's executed on startup like Emacs does. My init.el has a couple functions that behave differently under Mac (it still calls it NextSTEP, how cute) and Wayland (which it nostalgically calls X). After "accidentally" destroying my last corporate issued Windows install, I never went back and ripped the Windows-specific part of "set-perfect-font-size".
    - eropple 8y ago
      Oh man. I like the way you think. Basically everything I write uses a code file for configuration, regardless of language; do-est thou likewise, people! With the pounding I've put on my hands, emacs is mostly a nonstarter, so I'm jealous.

mattferderer 8y ago

Try Cmder.

eropple 8y ago
I've been using Cmder since shortly after its initial release. It doesn't step to either Tilix or iTerm2, depending on platform.
GordonS 8y ago
Another Cmder user here - I actually find it to be superior to any terminal I've used on MacOS.
- raarts 8y ago
  In what way exactly?

owenwil 8y ago

All of those things were fine, as far as I can tell. What did you run into specifically? I could run npm stuff, compile with Gulp or webpack..

eropple 8y ago
It's been like six months since I tried, because Fedora does great for me now, but in Visual Studio Code Ruby/Rubocop threw a rod, using a Linux-based .NET Core confused it, and anything Java was a nonstarter. For JavaScript, I do usually run `yarn watch` (workspace-level through oao) in a terminal and that works fine, but stuff like eslint/tslint integrated into VSCode was regularly a real pain. Worse: because VSCode--and if it wasn't a Microsoft product I would be less annoyed, but it's their editor and their OS so they can own it too--doesn't really support per-platform configurations, working around it by disabling stuff on VSCode causes my settings sync solution to break my other machines...
- rbanffy 8y ago
  > doesn't really support per-platform configurations It would be neat if the config file were JavaScript that's executed on startup like Emacs does. My init.el has a couple functions that behave differently under Mac (it still calls it NextSTEP, how cute) and Wayland (which it nostalgically calls X). After "accidentally" destroying my last corporate issued Windows install, I never went back and ripped the Windows-specific part of "set-perfect-font-size".
  - eropple 8y ago
    Oh man. I like the way you think. Basically everything I write uses a code file for configuration, regardless of language; do-est thou likewise, people! With the pounding I've put on my hands, emacs is mostly a nonstarter, so I'm jealous.