> Plus all of these starting points imply the use of new languages, configurations, and programs, in particular, builds.
Oh yeah, true, some people keep saying a language is just a tool trying to convince somebody to use it, but they forget, or omit for some reason, the fact that it's not "just a tool", it's a huge ecosystem that brings additional, enormous mental burden with it - build system(s), libraries popular within that specific ecosystem, language syntax, language quirks, project structure, its own conventions and so forth.
It's much simpler and more efficient (technically and labour market-wise) to write everything in a single language, as much as possible - unless you start going completely against the grain. Like, auxilliary scripts are usually written in cli-centric languages like Bash, as opposed to API-centric like Python, because you get maximum convenience using cli programs and composing them together.
But no, some people casually shoot themselves in the foot by jumping from language to language depending on the task because it's "just a tool". Ripgrep is a just tool. An entire programming language with its ecosystem is not.
MacOS. Project scripts and software are hardcoded for Mac. The alternative is Windows, but making the project dev environment cross-platform takes time. I dislike non-standard keyboard shortcuts for everything, lack of FAR Manager (using Midnight Commander has the same problem as all the different keyboard shortcuts), its constant annoying notification popups that covert part of my windows, its problem with handling non-Apple mice (have to jump through many hoops to make mouse movements sensible, put mouse wheel in the proper direction etc), its windows rounded corners that cut at the application's view area (run Alacritty without status bar, the rounded corners at the left bottom corner will obscure part of the shell prompt), its support for Linux that is significantly worse than in Windows and probably more that I cba to remember.
The other thing that I dislike but can't get rid of is JVM. Mind you, Python, Go, Javascript and so on is worse, but JVM is what I have to work with, unlike the rest of them.
Java was released in 1996. It got generics in 2004, 8 years later. I don't remember anyone panicking and yelling from every corner that the world is ending. Everyone understood the benefits and it was a much awaited feature. And yes, after Java got them, it became easier and more typesafe to use. End of story. And by the way, Java too was a very simple language and generics didn't ruin it.
I’m in a team where every member was forced into macOS against their will, because a lot of project scripts were hardcoded for macOS by a long-gone “architect”. My biggest gripes with macOS, after decades of Windows and Linux:
- Windows has better Linux support than macOS (WSL gives better integration which means Docker is easier to use compared to Minikube via Hyperkit vm)
- macOS doesn’t have the crucial software I need: FAR Manager
- I’ve had terrible experience with Apple’s customer support in the past where they couldn’t fix broken font antialiasing for external monitors
- I’ve been plagued by serious macOS bugs where it would cause 100% cpu load that could only be cured with closing/reopening the lid, and there are still some sleep-related bugs in it, whereas on Windows everything’s fine
- The window manager in macOS lacks basic features compared to Windows: no tiling, but Windows gets it out of the box with Win+arrows
- All hotkeys on macOS are different from the rest of the world (Windows, Linux) for no good reason and it makes switching between computers very difficult. And no, switching Cmd to Ctrl doesn’t solve it
- Rounded window corners make the first character on the bottom line of terminals unreadable