Re:Black Screen After MacBook Pro Update to macOS Big Sur
by tomp on Monday November 16, 2020 @06:23PM
(#25118394)
WSL works, but it's not nearly as integrated as a native CLI in MacOSx. For example, accessing Windows files from WSL is tricky, the other direction as well. Don't get me wrong, it's definitely an improvement over what we had before, but the overhead is such that I still primarily seek out native Windows executables (was just installing JVM and Bison (parser generator) the other day).
[ Parent
| on HN ]
Re:Black Screen After MacBook Pro Update to macOS Big Sur
by sfifs on Monday November 16, 2020 @06:45PM
(#25118595)
My approach is to simply organize work so that anything development oriented is kept in the WSL home dir and keep docs and PowerPoints in the Windows Documents dir which covers 95% of my use cases. The new Windows terminal is also pretty cool. I prefer this because I've sometimes run into weird assumptions that Unix utils make in a Windows environment based on how they've been compiled (eg. If they're built using Cygwin)