Ryelang Reddit group and Ryelang org domain, focus ...

After a motivating email by my unofficial handler :) (@otobrglez), I decided to move Rye up another step again. In the past, he also pushed me to put Rye on github, make it more orderly and presentable, able to run on docker, and other such bad things :).

A reddit group was created /r/ryelang. You are welcome to check it out, join, like and comment on things:

reddit.com/r/ryelang/

To kick things off, I've re-posted few more interesting examples from this blog there (with new accompanying text, mind you). And I've also created few original posts that might be of interest to you:

Rye basics: a gentle introduction trough Python examples #1

Rye basics: a gentle introduction trough Python examples #2

Rye basics: a gentle introduction trough Python examples #3

Domain

I also bought the domain, which will be the main hub around Rye language:

ryelang.org

There is not much there yet, just a few lines of Rye that run the webserver. I've never yet tested Rye on a long running tasks, where memory leaks could become apparent. These few lines of Rye have been running for days with no increase in memory consumption, so that's a good sign. You can see the code on the website itself.

This blog will also eventually move to ryelang.org.

I generally try to push content (Rye language in this case) and let the content itself (if/when worthy) push form, logistics, bureaucracy, PR forward ... That's why I didn't do these steps before. There is still tons of things to do on the language, but we are at least at a level, where I think there is something there there, and there is no turning back now.

Forward

These two are not the only changes. If until now was the time to experiment and test the language ideas in all possible and impossible directions and scenarios. We will a get more focused from now on. Focused on fewer areas, we want language to be useful the soonest:

utilities on the Linux shell (mostly server scenario)
webapplication / API servers
bots, nodes (telegram, nats, ...)

So the keywords for future development might be: console, http, databases, networking.

Oto said in his email, "Rye can't be and is NOT a drop-in replacement for Python, the most popular language on the planet with tens of years of development", so let's focus people! :)

I will also make a better protocol around github repository (I will post it in the repo itself) with more regular release schedule and two branches so that main branch always works.

That's it, now let's get to work!

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