So perfect that everyone uses TeX, and no successors to it were ever developed.
Pretty huge. Going to have to give this another try. I wonder if this will become as successful as Blender.
Also they need to cut the Apple-style quips for every item ("It's written in bold", "Dock your heart out" etc.). It even says "teamwork makes the dream work" at the end. 100% cringe.
How are those namespaces getting on?
Using a function is strictly worse than figuring out the formatting at compile time (something Zig also does).
The derives are just shortcuts. You can write everything out long-hand like you would in C++ or Python too if you really want.
Honestly both of these complaints are essentially "why does Rust use macros to make writing code better/easier?".
Honestly this looks like it sits in the useless middle ground between "proper CI that has all the features you expect" and "just write a Python/Deno script or whatever". I can't see what you gain.
Also you say "no painful YAML pipelines" but it uses YAML??
That's not a network effect.
Maybe slightly, but it's still way on the helping side.
They're clearly not going to be able to afford $100m/year in free CI.
Relatively minor for source code forges.
The reasons everyone uses GitHub:
- Free, even for private repos. No ads.
- Free CI - this is huge. Nobody else does this because it costs Microsoft around $100m/year to provide.
- It's quite good.
If anyone can ever compete with that then I doubt network effects will keep people there.
Terrible title. The article is about the risks of everyone using GitHub. That doesn't mean GitHub is destroying the open source ecosystem. In fact it's the complete opposite - GitHub massively helps the open source ecosystem. That's why everyone uses it in the first place!
I wouldn't expect the UI/UX to magically improve, in the same way that e.g. Audacity's is, or Blender's did back in the day.
LibreOffice is ancient and enormous. It would take a decent sized team several years to overhaul its UX.
code often contains backticks
I've never seen code contain three backticks though.
I guess your heading logic kind of makes sense but tbh I still hate it.