Interesting comment on the Mac. At my workplace we can choose between Mac or Windows (no Linux option unfortunately, my personal computer runs Debian). Pretty much all the principle and senior devs go for Mac, install vim, and live in the command line, and I do the same. All the windows people seem over reliant on VSCode, AI apps, and a bunch of other apps Unix people just have cli aliases for and vim shortcuts. I had to get a loaner laptop from work for a week and it was windows. Tried using powershell and installing some other CLI tools and after the first day just shut the laptop and didn’t work until I got back from travel and started using my Mac again.

[–] _____@lemm.ee 14 points 9 hours ago

If you don't have access to Linux, MacOS is the closest commercially available option so it makes sense.

Also please take what I said lightly, I by no means want to bash Mac users and generalize them. It just has been my experience. I'm sure there are thousands of highly competent technical users who prefer Mac.

[+] masterspace@lemmy.ca -14 points 8 hours ago (4 children)

Lmao, devs who insist on using the VIM and the terminal over better graphical alternatives just to seem hardcore are the worst devs who write the worst code.

"Let me name all my variables with a single letter and abbreviations cause I can't be bothered to learn how to setup a professional dev environment with intellisense and autocomplete."

[–] zarkanian@sh.itjust.works 10 points 8 hours ago* (last edited 8 hours ago)

Or maybe...hear me out...different people like different things. Some people don't like GUIs and enjoy working in the command line. For some other people, it's the opposite.

It's just different preferences.

[–] expr@programming.dev 13 points 8 hours ago (1 children)

Spoken like someone who knows absolutely nothing about vim/unix.

[–] PlexSheep@infosec.pub 6 points 7 hours ago* (last edited 7 hours ago)

You are making prejudiced, generalized, assumptions and presenting them as facts.

You are at best naive if you think people use vim and a terminal instead of "better graphical alternatives" (which there are none of if you've really gotten into vim/emacs/whatever). And we don't do it to seem hardcore (maybe we are, but that's a side effect). Software in the terminal is often more simple to use, because it allows chaining together outputs and has often simpler user interfaces.

The second paragraph is word salad. Developers should name their shit properly regardless of editor and it's quite simple to have a professional dev setup with 'intellisense' and auto complete in neovim. In fact, vim/neovim and I assume emacs too have much more features and flexibility of which users of IDEs or vscode wouldn't so much as think of.

I assume your prejudice comes from the fact that vim is not a "one size fits all no configuration needed" integrated development environment (IDE) but rather enables the user to personalize it completely to their own wishes, a Personalized Development Environment. In that regard, using one of the "better graphical tools" is like a mass produced suit while vim is like a tailor made one.

Just let people use what they like. Diversity is a strength.

[–] Klicnik@sh.itjust.works 1 points 4 hours ago

I tried using VScode to play around with Golang. I had to quit coding to take care of something else. I hit save, and suddenly I have way fewer lines of code. WTF? Why did/would saving delete code? After much digging, it turns out because the all knowing VSCode thought because I had not yet referenced my variables, I never would, and since my code I wanted to save and continue later wouldn't compile, it must be quelled. Off with its head!

Anyway, I decided to use vim instead. When I did :wq, the file was saved exactly as I had typed it.

[–] velvetThunder@lemmy.zip 4 points 9 hours ago

Why wasn't wsl an option?