Doesn't the first edition use K&R style parameter lists and other no-longer-correct syntax?

Actually, it's pretty surprising to me that a small university lab is forcing a specific version of a specific OS on you.

The problem is that most languages with exceptions treat that as the idiomatic error mechanism. So checked exceptions were invented, essentially, to do exactly what you say: add the exception type to the function signature.

Having separate errors-as-return-values and unwinding-for-emergencies is a much more recent trend (and, IMO, an obviously good development).

Sorry, why would you be "boned" if you have UTC time? Are you thinking of the case where the desired behavior is to preserve the local time, rather than the absolute time?

Ehhh, I mean this more strongly. I've never met people more in denial about language design problems than C++ adherents. (Though admittedly I haven't spent much time talking to Lisp fans about language design.)

WASM has no native ability to access most web APIs, including the DOM. JavaScript is literally unavoidable on the front end.

Oh, trust me, Qt is still primarily C++. It's effectively a massive set of C++ libraries.

A language being compiled should be able to support higher-level language concepts than what the target supports natively. That's how compiling works in the first place.

They also changed the wording from "closed" to "on hold" years ago, and I don't think I've ever seen the people complaining about the site take any notice.

I'm sympathetic to the desire for an "install and forget" drop-in Vim replacement, but...don't you think that this runs contrary to the purpose of Vim/NeoVim as a flexible, customizable editor? If you're an advanced enough user to have a nontrivial vimrc, then it's entirely possible that you'd also want different configurations for vim vs nvim, and that you'd want to be able to switch between them easily if you discover something doesn't work in nvim (especially since nvim is not yet at version 1.0). It's also probable that a lot of Vim users wish that more classic Unix/POSIX tools followed XDG, rather than requiring rc files in your home directory. As for Bash, not everyone uses it, there's no reliable way to automatically insert content into a bashrc file without potentially screwing things up, and Windows doesn't even have a reliable way to run a Bash script (assuming some version of Bash is even installed).

I do think it would be reasonable for the neovim installer (on all systems) to have an option to create an init.vim file that reads your vimrc, and possibly even to create a shell alias as you describe. But these should definitely be opt-in, not opt-out.

GNU ls has those features too (except knowing about Git). I'd be surprised if BSD ls doesn't at least have color support.

...not that I'm not going to check out eza and probably switch to it! But it's often worth knowing what features the GNU/BSD coreutils do or do not support...especially when comparing other tools against them.

Edit: I just checked, and this set of options works on both BSD and GNU ls, in case anyone wants better ls behavior on a system where you can't install eza for some reason:

ls -FH --color=auto

F appends sigils indicating executables, symlinks, or directories, and H follows any symlinks in the argument list.

fd saves me so much time. I actually understand find better than I wish I did, and fd is just so, so much easier.