I don’t quite understand the concerns in the comments here. The original blog post seems reasonable: https://www.waterfox.com/blog/15-years-of-forking/#what-waterfox-is-in-2026

I like the trend of refining existing tools. You take tried-and-true commands and shave off the rough edges and quirks. I use ripgrep instead of grep, fd instead of find, scm_breeze on top of git, dust instead of du, duf instead of df, z over cd, and xh instead of curl

They posted a series of other AI-related blogs in July, August, and October:

• https://www.rsyslog.com/rsyslog-documentation-enters-a-new-era-with-ai-first-strategy/
• https://www.rsyslog.com/clarifying-ai-first-what-it-really-means-for-rsyslog/
• https://www.rsyslog.com/shipping-better-docs-with-ai-restructuring-module-parameters-for-clarity-and-consistency/
• https://www.rsyslog.com/introducing-the-rsyslog-commit-ai-assistant/
• https://www.rsyslog.com/new-rsyslog-ai-assistant-powered-by-digitalocean-gradient/

I’d recommend looking at Hedy. It was created to teach kids programming, with a smooth ramp from simple English-like statements all they way to full python, with formal syntax introduced very gradually.
https://hedy.org/
As a bonus, it also allows non-English speakers to use keywords in their native language.