Chat-like interface for the terminal in Rye

Rye is at this point focused on becoming a useful tool for use in Linux shell (the server/back-end tasks). So I integrate it with the libraries that make sense there and I also like to improve the whole terminal capability of Rye.

I got some idea (one of many of this kind, we will see how this one goes :P) that I could make a set of interactive tasks, that could teach my two kids (and others potentially) about how the computer works, and how you can work with a computer through Linux shell. For this I would need some sort of interactive terminal based user interface, I imagined something chat like.

See how the "game" looks in action with asciinema.

Above is a small demo of the idea after a day of work on it. It's in form o a very very small text based adventure game :).

To make this work I needed to create basically 2 functions, chat (and chat-lines for now) and choice. I wanted to use short, context specific words to do all this so I created it inside a chat-tui context. And also I use the code by executing it inside that context using the word do-in.

Rye contexts are very malleable, you can string them together, isolate them, join them, extend them etc. Context could be seen (or used) as an Object, but we generally don't want to store state in them, like it is done with object oriented programming.

Rye also got a new function wrap. It takes two blocks of code, it executes first one, then the second one and then again the first one. It seems for now it should return the result of the middle evaluation.

Another such combinator function is pass. It accepts a Rye value (first argument) and a block of code, it evaluates the code by injecting the value, but it still returns (passes) the first argument forward.

The name and ideas for them are very loosely based on Factor's dataflow combinators , which were able to cover many common data or code flow patterns without using stack shuffling words in the case of factor, or variables in the case of Rye.

Visit our github for code: https://github.com/refaktor/rye

or our reddit group if you want to chat: https://www.reddit.com/r/ryelang/

Komentarji

Priljubljene objave iz tega spletnega dnevnika

Less variables, more flows example vs Python

In the last blogpost ( Less variables, more flows ) I wrote a quick practical script I needed. It was an uncommon combination of CGI, two GET requests with Cookies and a POST request with Authorization header. I really like practical random/dirty problems, rather than ideal - made up problems to test the language. To get a sense of comparison I rewrote the example 2 times while removing specific Rye features. But that comparison is meaningless to a person that doesn't know Rye or at least Rebol already. So I went on fiverr and made a request for a Python script with these requirements. I got a nicely written Python script that uses functions for each step. To be more comparable, I rewrote the Rye code to a similar structure. Below is the result ... For a next step, it would be interesting, to extract a little simpler example out and add error handling. With Rye-s specific failure handling, I think the difference would become even greater. You can find Rye on github .

Preberite več

Ryelang - controlled file serving example and comparison to Python

This is as anecdotal as it gets, but basic HTTP serving functions in Rye seem to be working quite OK. They do directly use the extremely solid Go 's HTTP functions, so that should be somewhat expected. I made a ryelang.org web-server with few lines of Rye code 3 months ago and the process was running ever since and served more than 30.000 pages. If not else, it seems there are no inherent memory leaks in Rye interpreter. Those would probably show up in a 3 month long running process? And now I got another simple project. I needed to make a HTTP API for some mobile app. API should accept a key, and return / download a binary file in response if the key is correct. Otherwise it should return a HTTP error. So I strapped in and created Rye code below. I think I only needed to add generic methods stat and size? , all other were already implemented, which is a good sign. Of course, we are in an age of ChatGPT, so I used it to generate the equivalent Python code. It used the ele...

Preberite več

Receiving emails with Go's smtpd and Rye

This goes a while back. At some project for user support, we needed to receive emails and save them to appropriate databases. The best option back in the day seemed project Lamson . And it worked well ever since. It was written in Python by then quite known programmer Zed Shaw. It worked like a Python based SMTP server, that called your handlers when emails arrived. It was sort of Ruby on Rails for email. We were using this ever since. Now our system needs to be improved, there are still some emails or attachments that don't get parsed correctly. That isn't the problem of Lamson, but of our code that parses the emails. But Lamson development has been passive for more than 10 years. And I am already moving smaller utilities to Rye. Rye uses Go, and Go has this nice library smtpd , which seems like made for this task. I integrated it and parsemail into Rye and tested it in the Rye console first. Interesting function here is enter-console , that can put you into Rye console any...

Preberite več

ryelang

Preišči ta spletni dnevnik