Rye in webassembly (WASM)

Go-lang can also compile to webassembly (WASM). I was trying to make Rye compile to WASM with TinyGo for a while and this weekend I managed to produce a build. TinyGo is an alternative compiler that uses LLVM and should produce much smaller wasm packages. The compilation passed but I wasn't able to make the full interpreter work in a browser.

I could be wrong but it seems that a PEG parser library that I am using drastically increases the .wasm size (to 6MB) and compilation time to more than 45 minutes. I could be wrong. I will explore this option later but I decided not to take many more 45 minute tries. Consequent compilations can be much much faster, but if I remove and add the dependency it seems I am back to 40 minutes gone. Another option would be to rewrite a loader in a simpler PEG parser generator (not a "library"), but not this weekend.

So I tried the native Go WASM compilation and .wasm in my case was "just" 3MB (without the PEG parser I think it was 1MB). The compilation was immediate as usual in Go, and a very nice error message from Go in the browser console persuaded me to go this route for now.

The goal is not tothink Rye could be used instead of JavaScript in a browser environment, but it could be a Glue/Declarative component and I can think of many interesting experiments with Rye or even Spruce in the front-en.

Below is a minimal demo using a browser based code editor component Ace. It evaluates the code when I press Ctrl+X and displays the output and the result of the code below.

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