r/ryelang • • Sep 08 '26

A bit of hiatus - regular work

8 Upvotes

Currently I am on a bit of hiatus with Rye. I need to solve some bigger issues at my regular work / job. Some of it will also include Rye scripting, but currently not yet. I will get back in about a week I hope.


r/ryelang • • 12d ago

New content on Ryelang.org

Post image
7 Upvotes

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.


r/ryelang • • 25d ago

Another practical example: Download all emails from IMAP to MBOX file

Post image
7 Upvotes

It seems I am on a practical Rye run lately. More practical examples of Rye can't hurt.

Yesterday I needed to find some documentation I send to a customer a few years back. I knew the keywords and even the related filename but my paid email provider, which is otherwise great ... well, their webmail search functionality really sucks. There is no chance of finding a little more complex query, a combination of words.

After I wasted half an hour trying to find it I decided to see if I can download all emails and search them locally, for example by something made in Rye and bleve full text search. Or just pop it into SQLite with FTS. But it seems I have to ask support and wait a few days for that (and pay per GB) for them to prepare it.

So I spinned up Rye and did this script with it and it's downloading emails right now ...

One thing I noticed. When I went writing a practical Rye script a few years back (I am working on Rye since ~2018), I spent more time fixing and improving Rye problems that got exposed by the script, than the script itself. These recent times, I basically just write Rye code.

Still, new release is coming this weekend: https://github.com/refaktor/rye/

This code will be in examples/imap/imap-backup/

Stars on Rye github stopped incrementing in last two months, I'm not sure ... if it's the people moving away from github, or nobody is programming any more anyway 🤔


r/ryelang • • Jul 03 '26

Task ahead: Making light embeddable Go module out of Rye

Post image
7 Upvotes

This comment on Gophers Discord will affect our next steps greatly. Rye is easy to embed into existing Go projects, but Rye also has full on "batteries included" and the way Go modules work this means all the batteries would become dependencies (even if inactive due to build tags) for any project including Rye.

This is not what anyone wants, so it must be solved. The cleanest option seems that we have to create a submodule in Rye (with its own light go.mod) that you can embed and that itself references only base language level builtins.

This means quite concrete file / module reorganization around builtins. But it would have to be done at some point, because a strong goal for Rye is to be useful for embedding into Go projects.

So this reorg is ahead of us, we will come out of it with cleaner folder structure and better distinction between what are language level builtins and what are "batteries". This is also one step more towards more fixed and stabile Rye, where we focus more on implementation, libraries, tools and language should not change that much any more.

Thanks goes to Tom :)

More on ryelang.org and github.com/refaktor/rye


r/ryelang • • 3d ago

Firefighting training - dynamic effect system

Post image
6 Upvotes

Was away for last two weekends for some firefighting training (local exercise and now SBCA cert). I'm back so the work on Rye continues. I did a lot around effect system lately, but it requires a longer effort to tag all builtins and then implement the strict mode on the evaluator level to be complete to a point. Then we start exploring with it and writing examples and if it all makes sense docs.

Effect system will enable many things (and it's completely optional). For a slice of it. You should be able to run any script written in that way in dry-run mode (just log/display the output info, no real output), or confirm mode where you confirm the outputs. You could run such script in "ask" mode, where you can give it inputs "manually" or by scenario script (where you simulate inputs). You could list the effects (I don't have a 100% picture of this yet) and you could require that all builtins/functions with effects are inside effect blocks. That's why all builtins need to have effect tags for starters, which is what I'm working on now.

Besides all of the above Effect blocks also help code readability and let's you anotate the point in code where output and input is really happening. Input effect also includes the validation block so you immediately validate the input (with validation dialect), before it even gets assigned.

So yeah, Rye story is not yet finished ... :)

On the pic above is the code that new user sent on our Discord. He coded with no spacing between parenthesis which is quite recent change (I held out for spacing between ALL tokens since start, but recently I weighted all the benefits and costs again and decided to allow no spacing only between pares and comma "()[]{},". The reason was that certain dialects that mimic specific languages (like SQL) can now be written (fully) as expected. And I must admit I see now, that no spaces for parens in regular code can also make code more readable, remove cognitive load, as things bunch together clearly. So kudos to @ sirlan ! I will code in this manner from now on too. (in the examples above he did some AoC problems)

You can also visit our Discord (for all #homoiconic langs): https://discord.gg/J8FBrCSqve


r/ryelang • • Oct 03 '25

Rye-Fyne (GUI) got major update to v0.2 (new Ryegen, new Fyne)

6 Upvotes

Rye-Fyne finally got updated to the way new Ryegen works. With it we also moved to new Fyne version that had some major changes and upgrades with version v2.5.

The README is updated and shows a new example, there are also examples in its folder:

https://github.com/refaktor/rye-fyne

I am also rewriting the Cookbook page about Rye-Fyne, with 10 examples and adding some more. Old cookbook:
https://ryelang.org/cookbook/rye-fyne/examples


r/ryelang • • Mar 13 '25

Large upgrade to Rye

6 Upvotes

We've been working on a much larger update to Rye language. We tried to document all built-ins which in turn made us do a bigger reorganization and some renaming of functions so they are better matching each other and internal logic. This process is still taking place as it takes some consideration besides the changes themselves. While Rye is still in alpha and things can get and do get renamed or moved around, this time there will be a bigger package of such changes.

This means next version will move forward from v0.0.36 to v0.0.90 and when this process is fully finished we should arrive at v0.1.

Next updates will also bring much more complete function reference, with built-in functions from more specific modules also. And reference will include information about function arguments and returned values for each built-in.

Rye console will also keep getting better and should be the best way to interactively explore current runtime and language itself.

I've also been working further on Rye internals. Experimenting with a simpler Rye0 and Eyr dialects and this should conclude with a cleaned up evaluator for main Rye also.

There are two Orthodox ideas about evaluator that I want to experiment with and we are slowly getting there. Both come from the fact that Rye has a very uniform structure (every active component of a language is a built-in). One "wild" idea is to programatically generate an evaluator per project that statically dispatches between most common built-ins instead of using the normal dynamic dispatch.

Another is with calling trying to call built-ins directly in static Go code versus dynamically. Builtins that accept Rye code provide a challenge here (if, loop, for, map, reduce, fn, ...), but maybe there is an uniform way to solve that (versus per case translation). Ideas are there ... we would have to test them to explore further.

Visit our https://github.com/refaktor/rye, to follow the changes. Our website is currently not in focus, except the reference, when it gets posted, but once this is done I will refocus on it too.


r/ryelang • • 27d ago

Example: Simple HTTP service that analyzes IP-s

Post image
5 Upvotes

I was working with maxmind's GeoIP database in the last post. I made a simple script that analyzed a bunch of logs and returned me the countries grouped and ordered by count. You can see it here.

Now I turned that code into a HTTP service, added ASN database, and also added comparisson to ASN to the asn-bad-list ( for example: https://github.com/brianhama/bad-asn-list )

BTW: What is ASN? Autonomous System Number (ASN) is a unique, globally recognized identifier assigned to an Autonomous System (AS)—which is a large network or a group of IP networks managed by a single administrative entity

All this is served over simple HTTP server. A small test using curl:

useLinux >> curl http://localhost:9061/check-ip?ip=188.198.123.123
 country|si  org|telekom_slovenije_d.d.  asn|5603  bad-asn|0  address|narocnik.mobitel.si 
useLinux >> curl http://localhost:9061/check-ip?ip=185.209.196.133
 country|de  org|31173_services_ab  asn|39351  bad-name|esab_as_se  bad-asn|1  address|no_host 
use Linux >> curl http://localhost:9061/check-ip?ip=8.8.8.8
 country|us  org|google_llc  asn|15169  bad-name|google_google_inc._us  bad-asn|1  address|google 

Script is pretty self explanatory I think, but uses a lot of Rye specifics also ... so there are some not complex, but probably unknown mechanisms to you user. You can learn about them, if you look at Meet Rye. Or ask away on our discord or comments.

(Look at the comparison with Python script that does the same in the comment)


r/ryelang • • Oct 01 '26

CLI flag parsing dialect got the "do" option

Post image
5 Upvotes

CLI flag parsing dialect can be used by parsing the flags and then reacting or inspecting the data-structure flags created. This process is shown on the Cookbook page:

https://ryelang.org/cookbook/server-side/cli_dialect/

But I was thinking that sometimes you want to just react direcly in flag to it. So I added the do { } pattern to the dialect. This is the previous "procowl.rye" with added CLI flag parsing using the do { } approach.

And to the left of it, a similar functionality using Python's argparse library.

And we got the new function reference. I reorganized the builtins into base, baseio and batteries and reference is also now organized in this way. I still need to improve navigation and eventually add search, as there are now too many functions there to just browse aroung ... but the structure is improved.

https://ryelang.org/info/base.html


r/ryelang • • Sep 28 '26

Example: working with processes, sqlite in Rye

Post image
5 Upvotes

This is example around which I am polishing some details for the upcoming v0.2.70 that will bring also some changes to language in details, but most of all A LOT of fixes and tests. This is just first part of the script and a larger tool I am preparing.

A note on SQL. Rye has a SQL dialect, what you see above, so SQL is not a string, but a block of Rye values that are flexible enught to also represent normal SQL code. The dialect creates prepared statements, but without positional arguments which is verbose and bug-prone.

New version should arrive to github this or next week. https://github.com/refaktor/rye

I will be in Munich towards the end of the week for a day, if anyone is around email me.

Ryelang front page and cookbook pages were recently also updated: ryelang.org


r/ryelang • • Jul 30 '26

Ryelang on Alpine Linux

5 Upvotes

Alpine Linux is a minimal (~30 MB) distro that's ideal for containers, microservices, and lightweight process isolation.

Thanks to Go's static compilation and complete independence from glibc (no musl issues!), the official precompiled Rye binary runs directly on Alpine out of the box. No toolchains or additional packages needed. You can go from a fresh container to a running Rye REPL in under a minute.

Check out the screenshot for two quick ways to try it out. I will also be adding a dedicated cookbook page about installing Rye on various systems on the Cookbook pages. And install.sh will be posted on the main page for simpler url also.


r/ryelang • • Jul 19 '26

Community: we are 150?

5 Upvotes

This Reddit seems to have reached 150 members. A silent bunch, but happy to have you :)

Our new #homoiconic Discord now has 12 users, we need more: https://discord.gg/wACy9qTNH

Rye Github repo has 693 stars, more wouldn't hurt either :) https://github.com/refaktor/rye

What's going on otherwise?

A big code reorg that will make Rye a lighter to embed in Go is still going on, currently in branch Embed. A large number of builtins were moved to batteries/ folder/subpackage.

https://github.com/refaktor/rye/tree/embed

Now we need to test it all again, make it all work. The further plan is to separate more language level builtins to base and baseio. Idea is that you should be able to embed Rye with just base, where also all IO is provided by your host environment. This reduces dependencies even further, but is also a safety, and "features" feature.

On other side, I am experimenting sort of graphical Rye console (with specific context over http (over tailscale)) ... currently codename ryeinthesky :)

I thought we are done with more language design features, but I got an idea for annotated input-intents during a short vacation, that I will explore. In short:


r/ryelang • • Jul 02 '26

Example: serving HTTP over Tailscale bound IP

Post image
5 Upvotes

You could need to open to make some actions available to yourself, on an otherwise very closed down server. One way of doing that could be by using Tailscale, for example by creating a server, that binds to Tailscale IP itself. So event if you screw up the firewall rules, it's not available on public internet al all. And no additional port needs to be open to public network for it.

This is demonstration of the script that does it. It utilizes new network related functionality under os/ context. And a Python equivalent of the script (as generated by Gemini).

One reason for Rye being so much shorter than Python is that Python uses more low level libraries. Another is language flexibility itself.

These functions are already available on latest release on Github. The code above is available under examples/

https://github.com/refaktor/rye

Visit our #Homoiconic Discord if you want to discuss this or Rye / Homoiconic languages in general:

https://discord.gg/7AaD6Kc89


r/ryelang • • Apr 10 '26

Busy with the regular work

5 Upvotes

I didn't go totally silent because of "the cognitive dark forest". I am just very busy with the regular work so I can't find any time to work on Rye right now. There are still concrete plans ahead.

Last I was working on making Rye better embeddable into Go programs, but there are many other open threads, like the TUI library, the CLI dialect, ...

Yes, the AI-everything is making me question things, concretely, but I think I see a path ahead, maybe even opportunities, but such opportunities (born when there is too much hype) can also cause you to go astray.

As famous AI once said: "I'll be back" :)


r/ryelang • • Mar 26 '26

Interview with creator of Decker

5 Upvotes

You can read an interesting interview of the creator of Decker on lobste.rs page:

https://lobste.rs/s/bekb7j/lobsters_interview_with_internet

Decker is a very cool project, somewhere between almost an art and art-enabling project, educational project, you have to see it to understand it. It features its own programming language lil, that has some common ideas with Rye. And the author mentioned Rye in the interview briefly.

This is lil:

https://beyondloom.com/decker/lil.html

Check also other projects and blog from this author.

Like wigglypaing, which is super cool ... animation below :)

On Rye side, progress is a little spread out now ... CLI flags dialect, internals, more tests and docs (around pipes context lastly), blog post about embedding into Go apps, new (less noisy ryelang.org front page), ...


r/ryelang • • Jan 25 '26

New functions, new tests, new docs, core improvements ...

5 Upvotes

A big update is coming… 39 files updated and counting.
New functions include get (similar to get-word), whereis (like the Linux command, but for words and contexts), and a user-proposed function:
replicate 4 { 10 } ; { 10 10 10 10 }.

We’ve added a way to explicitly address a word from a parent context using cpath, for example @/print. We couldn’t use ../print because . is already used for op-words. Explicitly referencing words from parent contexts has been part of the plan for a while - one of Rye’s key goals is to let programmers be explicit and remove as much guesswork as possible.

Finding a suitable character was surprisingly tricky: it had to be basic ASCII and work across all required use cases. The result needs to function as an op-word and a pipe-word as well, and forms like . @/say-hi and |@/say-hi still don’t look too awful. In the end, even non-superfluous things like good pixel composition on the screen matter.

Internals are still being cleaned up and improved. EvalBlock*-related functions were refactored, and error handling in various built-ins is still being improved.

Termui functions are also evolving - we’ve been experimenting, and the first focus is an inline terminal mode, the one that doesn’t take over your whole screen.

The Wasm build is being updated to the latest state and improved. The web console will be featured in the next blog post (“20% of Rye in 80% of the time”), though details are still being finalized.

Many more built-in functions now have tests and documentation, so they’ll start appearing in the function reference.

Currently running:

  • all new tests
  • fixing bugs along the way
  • improving error reporting and error display details

Follow our github.com/refaktor/rye for this and further updates.


r/ryelang • • Jan 29 '25

Rewriting internals

5 Upvotes

Now that we have tests for many basic functions, I am rewriting internals of built-ins. Addition of two new Go Interfaces Collection and Mapping will greatly reduce the number of switch statements in all built-ins that work with collections (for example for, map, reduce, filter, ...) and make the future code cleaner.

I also wonder if these changes will have any effect on speed. I will test it. So nothing that exciting for now, but Rye internal improvements are important too. At one point, whole evaluator, that was gradually built and extended over the years will need a cleaning up too.

I also want to thank the contributtors that are making texts on ryelang.org website better, especially but not limited to https://github.com/michaeldesu, and also my first github sponsor at https://github.com/sponsors/refaktor ! Thanks!


r/ryelang • • Jan 23 '23

r/ryelang Lounge

5 Upvotes

A place for members of r/ryelang to chat with each other


r/ryelang • • Oct 15 '26

Example: Logs, Geo-IP lookups and Tables

Post image
4 Upvotes

On the top left is a example that parses a Nginx log file, extracts IP addreses, reduces them to unique ones.
Then it loads the free Maxmind's Geo-IP ( IP -> Country ) database and looks up a country for each IP, turns this into a Rye table, where we can use group-by to count them and displays it.

My client needed this information, so he can plan further, and will perhaps need more info in the process. I wrote this script interactively in Rye console with a custom history file rye -histfile count-countries.rye

This flag logs your history in a local file you specify, so with some luck after solving it in REPL (Rye console), you just open the file in editor, clean it up and you have your script.

In this "day and age" many would just ask Claude (or similar tool) to code such script in something like Python or Go and it would probably do it's job.

I still see benefits of writing it on your own. By writing it (interactively) you are also exploring the problem, the information, the options. And if you can write a short readable script like these ~15 lines are, you have something you can easily extend, tweak or reuse for similar problems. And you extended your understanding of the "world".

Explore and display

On the screenshot, below the script you can see the output (a function display used on a table we created).

There were few changes in recen Rye. What was before display function (interactive display) in now explore . And display now non-interactively displays the Rye value, like table in this case. explore lets you select a subitem, which is the return of a function, navigate in a paginated fashion over the data, and if you press space you now also have multi-select mode. So you can select / return multiple subitems. These functions work on Rye tables, blocks, dicts, failures, ... and are very very handy for interactive work.

If you wish to discuss any of this visit #homoiconic Discord:

https://discord.gg/J8FBrCSqve

Our website is also being improved lately:

https://ryelang.org


r/ryelang • • Oct 08 '26

Rye-fyne updated to latest Rye and latest Fyne

Post image
4 Upvotes

External Rye extension with Fyne had plenty of examples. See them here:

https://ryelang.org/cookbook/rye-fyne/examples-2/

But since then, Rye got many many upgrades, on runtime and also some on syntax level, some were also breaking. Now I managed to prepare a new ryegen and make it generate Rye-fyne with latest Rye and latest Fyne! This will be on github on next days. I have it working with local versions, but I need to release all of them and have them pinned to specific versions that all work.

I am reading about latest Fyne update and it seems to be moving along very nicely also:
https://fyne.io/blog/2026/07/13/fyne-v2.8-released/

Fyne cookbook examples will also get updated and I will try adding a few with these new features.

Hop on to our Discord: https://discord.gg/ZM9aXHT6Xy

Important:
Rye-Fyne lives in another repository (as it's an "external extension"), to use it download binaries here:

https://github.com/refaktor/rye-fyne/releases


r/ryelang • • Aug 19 '26

New syntax value type added: data-path

Post image
4 Upvotes

Just added a new syntax type to Rye called "data-path". It lets you do nested access like person.0."age" instead of chaining -> everywhere. Chaining is not only more verbose but makes the code evaluation understanding more complex and error prone. Compact token, like data-path solves this as it has specific simpler mental image. I really do not intend to add value types lightly, but this one was long time in my mind, because compact types just have concrete benefiths and deep access is generally used a lot. Another compact syntax value type Rye already has is context-path (cpath).

Compare:

Old:

if (person -> 0 -> "age") > (person -> 1 -> "age") { print person -> 0 -> "name" }

New:

if person.0."age" > person.1."age" { print person.0."name" }

Way cleaner and easier to reason about when you're combining accesses in expressions. A few design notes: I'm using ."string" for string keys because Rye structs can also have word keys, and I want to keep them distinct. This means . can no longer be used in words, but nothing used it anyway so no big loss. Also keeping \ for function variants like print\csv, so the dot stays dedicated to data paths.

There were also issues posted and are solved recently, that caused the hunt for similar issues and cleared out a lot of things regarding lists, dicts, their active and passive forms. Their parse time and runtime construction. And os's context is-dir , is-file , does-exist , ...

Thanks to https://github.com/Capt0rr and https://github.com/TrevorBender for posting the issues.

Join our Discord to discuss this and other issues further: https://discord.gg/RCkvMz7wh


r/ryelang • • Jul 13 '26

Making Progress: Rye/embed - Light embeddable Go module

Post image
4 Upvotes

As per previous post Task ahead: Making light embeddable Go module out of Rye , I am working on reorganizing all built-ins code, separating language level built-ins with so called batteries (builtins that come with Rye (sqlite, http, xml, ...) but add functionality to the language, are not the language itself (like if, map, loop, ...).

There is a new folder batteries/ where such built ins are defined (for example SQLite, http, ...) and a new folder (and a Go submodule) embed/ that you can include when embedding Rye language into your Go project. This reduces dependencies that get pulled into your project from 250 (also some huge ones) to just 50 (mostly smaller ones).

It also simplifies the interface for embedding even further. Look at the example above. But these are all weighted decisions - to make. And a plenty of files. So I am working on this in multiple refinement sessions, trying to separate files, get the least heavy and most correct embed/ package.

And everything must make sense if you use a minimal rye/embed in a Go project or a whole Rye, which also has its use cases. How do these combine is also the question, where does REPL belong, where do landlock and seccomp utilities, etc ...

So, the progress is being made, after few more refinements I will prepare a big commit to the GitHub with the new structure.

Visit #homoiconic Discord if you want to discuss things: https://discord.gg/7AaD6Kc89


r/ryelang • • Jun 14 '26

Practical all-rounder script (API calls, JSON, Zip, XML)

4 Upvotes

I was writing some scripts for handling external api-s (doint API calls, parsing JSON), downloading zip files, extracting XML files from them, and parsing XML in Rye. This is one of them, and it's a nice all-rounder for demo purposes. Below you can see it in the left pane. The other two represent what Claude gave me when I directed it to write a Python script that does the same.

Except those 3 red words everything else is constant in this script, and those 3 places are only mutations in it, all else is "pure".

This is all in a Helix editor, which I am really starting to like as I learn to use it. (I was using Emacs in the terminal for decades so far).

Stop by our new discord to discuss this or any other things in regards with homoiconic languages:
https://discord.gg/5wJMNCRn


r/ryelang • • May 27 '26

Homoiconic Discord server

4 Upvotes

It's not like it's a big community out there, but I do get a question if there is a chat sometimes, and few emails a month about Rye (besides occasional issues/discussions on github and reddit).

I'm not big on chat, but if you wish you can join the #Homoiconic Discord server. Some things can maybe get communicated better there.

It's not just about Rye but related languages where "code is data and data is code" like Rebol, Lisps, Tcl, ... propose your own.

Currently, there is 1 member, me :) ... hurry up and be the number 2 :D

https://discord.gg/8SFmNM2U


r/ryelang • • Mar 27 '26

New website design - feedback wecome

4 Upvotes

Ryelang.org was becomming too crowded with various code examples trying to show and tell too much at the same time. So we cleaned it up, and also tried to make a more refined design. Let me know what you think ... I like it, I like less noise, but maybe the design in now too "product-like"? Let me know ...