davad

It’s powerful, lightweight, and ubiquitous. If you do sysadmin work, remote into a random machine, and need to update a config file, it probably has vi installed already. It’s also extensible enough to use as a full IDE.

Personally, I like it because of how fast it feels and because I can do everything while keeping my hands on the home row of the keyboard.

I’m about at that point. I had to set up a Windows VM last year to do some testing. It was more of a struggle to install than I expected.

I don’t know how dead it is, but it’s pretty straightforward to set up your own gateway (public or private). Even if you don’t have a tech background, there’s the “IPFS Desktop” app that stands up the IPFS service locally.

The only one I think is reasonable is GraphQL. But that isn’t rest, and HTTP is just one of the transport layers it supports.

For anything claiming to be RESTful, it’s a crime.

Two different concepts.

You’re talking about work slowing because of increased overhead from more people needing to communicate and make decisions.

The OP is talking about the"bus factor". How many people can leave the project unexpectedly and still have the project survive. E.g. if only one person has access to merge changes, the bus factor is 1 regardless of how many people actively contribute.

(another pet peeve of mine is “rest” APIs that use 200 response codes for everything)

Yup, also some APIs use GET for everything. It’s a pain. And it means that filtering by verb only helps if you’re intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you’re developing the API yourself.

What is “shutting down”?

I think they did say that in the older thread. But for proper security, you shouldn’t have to trust them. You should have build tools that will re-fetch everything to create an identical build. That gives a clear chain of custody, which proves that morning has been tampered with.

It sounds like most, if not all, come from upstream projects.