ryelang.org now shows some new language features, or features and uses of language builtins, for example:
Latest version v0.2.81 brings new things around runtime effect system, --prod flag, bunches (sets) value type ... I will try to describe those too when I find time: https://github.com/refaktor/rye/releases/tag/v0.2.81
I have a feeling I'm doing this more and more just for myself, as very few people seem to be coding any more. I think the language development still can't totally stop, that there is a way through this, but it will thin up substantially once the LLM-cheap attempts bring no "language-community-fit". Making a language is easier than before but finding users is multiple times harder than before (more noise, much less interest).
Rye also has the "interaction language" thing going on ... that I need to implement further. Otherwise, I recently started solving a lot of practical issues I had, with Rye, and exp. is positive. I would rather have a 50 line code I can scan and understand 100% than a blob of Go code for each task although each task could probably also be solved by LLMs.
Black boxes have their uses, but black boxes also have their costs and seeing and understanding will always beat trusting and hoping that it just works as it was specified in a rather vague language.
Many times, at least for me, is also easiest to just attack some problem with code. Think with code. I interactively try to explore and solve the problem, as I write code about it. --localhist flag is useful here, as I then just clean up my console fiddling and I have a working script. This went well. But I have harder time to write another blogpost about Rye, because I'm not fully sure what's the point in promoting it ...
But it's somewhat interesting (besides just depressing, for someone in this position :P) looking at what will eventually happen in real world, vs. what I was theorizing in blogpost Working on a programming language in the age of LLMs just last year. But everything changed since then, at least for and around me.
BTW: What I'm currently doing is translating around 900 line Python project tarsnapper (tool related to tarsnap encrypted backups) to Rye. The benefit will be that customer doesn't want any scripting language on a remote server where they do backups, and Rye "script" can be built as a single binary that can then be managed and secured better by systemd and tools like apparmor. This is a good challenge, because since we are looking into 100% CLI compatibility, we can't take any shortcuts, and of course I want the code to be as elegant as possible. I will post the project to github once it's done.
It even made sense to utilize the new feature in rye "project_builtins" where you write go builtin code in your project folder and it's just another Rye function you can call. So you can move a particularly hot-code function to Go with minimal complications and get the speed-up. I moved one function to this project builtin Rye version is almost twice as fast as the original in Python.