Even Netflix is moving to have levels, however. At great cost to morale it seems, with people who were formerly all at the same title being grouped into potentially different levels.

Warp is a terminal, we still rely on the underlying shell to do the interpretation / execution of the commands. At the moment, we support using bash, zsh, or fish as the shell.

...huh.

Writing a tty which has to support specific shells isn't confidence inducing.

How did you paint yourself into that specific corner exactly?

I'm guessing the auto-complete handling means they need to understand the line editing of the shell. If they've done it well, it'd hopefully be possible to quickly handle others and/or make it configurable.

Ah, that.. almost makes sense? fish at least has its own autocomplete.

I'd be more careful about the messaging then, something like "you can use any shell you want, we provide enhanced features for bash/zsh/fish and are looking to expand that in future".

This. Also the mention of ‘collaboration’ and ‘cloud’ put me off. “Do one thing and do it well”.

The problem with that mindset is that there is a huge difference between leading a greenfield project with very few users and leading an established project that's a major piece of the infrastructure in basically every front-end app. In the former case, the bulk of the work is actually building the functionality, so looking at PRs / commits can make some sense. In the latter case, there are more constraints to consider and a lot of the work is in determining _what_ needs to be worked on, as opposed to actually writing new code. Also in things like project management, fundraising, etc., which don't show up as GH commits.

In addition to the points raised by the other comments, a big reason we decided not to use `engines` in Volta is that `engines` can be a range: One of the design goals of Volta is to allow for reliable, reproducible environments, and a range is necessarily not static (new versions are released all the time).

Semantic versioning was supposed to prevent breaking changes. I guess this is more akin to package-lock.json then.

Yeah, conceptually the setting is intended to be closer to a lockfile than a semantic version.

Additionally, even with semantic versions, `engines` is often specified as something like `12 || 14 || >= 16`, so they span multiple major versions, which is where breaking changes can (and do) show up.

When people make these bets, they are betting against the oddsmakers. So all of the Trump supporters betting that he would win, especially _after_ the election and it was clear he lost, were basically giving the house their money.