News for hackers. Stuff that matters.
Re:ARM Mac Impact on Intel by TickleSteve on Monday June 22, 2020 @06:12AM (#23598720)
Arguably now, with WSL, Windows is closer to the cloud environment than macOS. Its a true Linux kernel running in WSL, no longer a shim over Windows APIs.
Re:ARM Mac Impact on Intel by H1Supreme on Monday June 22, 2020 @11:02AM (#23600989)
Yep. WSL 2 has been great so far. My neovim setup feels almost identical to running Ubuntu natively. I did have some issues with WSL 1, but the latest version is a pleasure to use.
Re:ARM Mac Impact on Intel by run_the_race on Thursday July 02, 2020 @07:00AM (#23711923)
Do you use VimPlug? For me :PlugInstall fails with cannot resolve host github.com
Re:ARM Mac Impact on Intel by H1Supreme on Thursday July 02, 2020 @12:53PM (#23715233)
I do use VimPlug. Maybe a firewall issue on your end? I'm using coc.nvim, vim-go, and a number of other plugins that installed and update just fine.
Re:ARM Mac Impact on Intel by socialdemocrat on Monday June 22, 2020 @07:08AM (#23598986)
That is just utter pain though. I’ve tried it and I am like NO THANKS! Windows software operates too poorly with Unix software due to different file paths (separators, mounting) and different line endings in text files.

With Mac all your regular Mac software integrates well with the Unix world. XCode is not going to screw up my line endings. I don’t have to keep track of whether I am checking out a file from a Unix or Windows environment.

Re:ARM Mac Impact on Intel by mmm_grayons on Monday June 22, 2020 @09:39AM (#23600048)
Your line-ending issue is very easy to fix in git:

`git config --global core.autocrlf true`

That will configure git to checkout files with CRLF endings and change them to plain LF when you commit files.

Re:ARM Mac Impact on Intel by naniwaduni on Monday June 22, 2020 @10:07AM (#23600340)
Eating data is hardly a fix for anything, even if you do it intentionally.