With caveats.

TCL & CMake are fully stringly typed. Both pretty terrible languages (though TCL can at least claim to be a clever hack that was taken far too seriously).

It’s an alpha release.

You really think they're going to revisit this? That's not really how software development works.

It’s an alpha release.

I was talking about Flatpak.

That actually hasn't been my experience of programmers' behaviour. There are many developers who can't be bothered to set up tools like IDEs, intellisense, debuggers, etc. which would definitely make them faster after the initial setup. I can easily believe it's the same for AI.

That said, it does seem silly to require you to use it.

Basically it uses bind mounts instead. See this page for details.

I haven't actually used (since Plan 9 is dead) and I doubt it covers every use case for symlinks (e.g. this wouldn't let you commit them to a git repo), but I really think the benefits of symlinks not existing at all would far outweigh the effort of having to think of alternative solutions.

Sadly we don't get to live in that alternative history now... :-/

Your example doesn't quite fit the crime. A better example would be. "I ran and catch upped to him." Or "These clothes are available to be try onned."

To be fair I once asked an Italian what was the hardest part of English and they said compound verbs, so maybe they're just not native English.

That's my charitable explanation anyway. If not I'm joining the hunt!

Yeah there's more stuff that runs in the shell. But pretty much all the things you mentioned would work on a VT100 from the 70s. This is about modernising the terminal itself.

Hell, Linux terminal emulators don't even have a "clear screen & scroll-back" keyboard shortcut like Command-K on Mac. There's no command output history, there are no auto-complete popups, editing commands is still extremely basic (no multiline input for example). The command prompt doesn't even have the text editing capabilities of Notepad.

The liquor store presumably? Just submitting patches is a simple 12 step process. I can't imagine the development and review process is any easier.

I have implemented a Git client from scratch which involved quite a bit of reading the Git source code. It's not bad code but it's definitely the sort of code that would break in all sorts of unexpected ways if you changed something. I wouldn't volunteer my time their tbh.

No tongue-twister or finger-breaker when typing (I had enough of that with 25 years of YaST2)

...

• Zwieback
• Zugezogen

Erm. Yeah. Zap and Pin are good suggestions at least.

I think he meant the idea of shaming companies for not donating to things.

In fairness for the invalid escape sequence thing static linters (Pylint, Pyright, etc.) should be already telling you about it.

We use it for triaging test failure (running tens of thousands of tests for CPU design verification).

That use is acceptable because it is purely informational. In general you should avoid regexes at all costs. They're difficult to read, and easy to get wrong. Generally they are a very big red flag.

Unfortunately they tend to get used where they shouldn't due to lazy developers not parsing things properly.