It adds a massive new dependency to the build process for base system. C is itself a massive dependency, but it's already there for pretty much everyone.

This matters more for distros and OSes where building things from source - either everything, as in e.g. Gentoo, or at least the base system, as in the BSDs - is pretty common and expected.

>>> C is itself a massive dependency

the C standard library?

No, the C compiler. Both gcc and Clang are pretty big, even before you account for the standard library. I suppose you could get away with something like tcc, though.

lots and lots of edge cases, I minimal compiler can be kbs

C compiler backend support is pretty broad.

Probably the biggest understatement I've ever seen on HN.

Supported on virtually every OS and embedded platform in existence.

Abstractly, very much yes.

In the context of nano and editors, you also have to contend with POSIX, tty I/O, etc.

It isn't, except for the fact that most people who can code low level programs know it. But what you don't want into consideration is pretty much the important part of shipping a software you want to proliferate easily.

Statically linked C programs are the easiest to ship. Copy and run. No runtime required.

A feature of any AOT compiled language since compilers exist, nothing C specific.

Java and .NET would like a word with you.

When correcting someone on Internet be sure to know what you are talking about.

ExcelsiorJET, JamaicaVM, Aonix PERC, IBM Websphere Real Time, Xamarin on iOS, .NET Native, Bartok.

yes, good idea, let's make a modern console-based text editor that comes with IBM Websphere Real Time

You can embed their runtimes. I'm not saying that's desireable, just that it's possible.

Same with go