Goroutines and channels in Rye

Many "scripting" languages, Rebol included, have or had somewhat problematic handling of concurrency. One of the reasons I started writing Rye in Go was my naive reasoning, that because Go has very solid concurrency support Rye will be able to have it also. Rye is meant to be good at backend tasks and here concurrency is not unimportant. My naive assumption so far seems to be true.

Yesterday I re-implemented web-sockets in gobwas and they work now. But to work with them in any meaningful way I need some additiona concurrent mechanisms. And in Go-land they all start with goroutines and channels. Goroutines are like green threads or coroutines and channels are used for communication between them. Unlike some green thread implementations that still run on one core, goroutines enable you to utilize multiple CPU cores.

First example uses gorotine and a channel, second creates a parallel http downloader with goroutines. Function go-with runs a function (with one argument) as a goroutine.

Note: pipe is just a function with one anonymous argument

This is all "alpha" level and can change. Next I need to add support for different number of arguments. I also need to implement some other mechanisms like WaitGroups, think about different kinds of channels, etc ...

I also need to get to know Go channels and goroutines better in the first place. So there is a lot of interesting "work" ahead.

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 elegant

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