I'm an happy owner of a #remarkable 2. What I liked the most about this device (obviously apart its calm OS and features) is its theoretical hackability. Since I bought it, I already did some experiment on it. At first, it was pretty easy given that the base OS image provided a python environment. However it’s no more the case, and with a very basic default curl, networking scripts became harder to craft.

1/3

Being a ruby developer, I knew about #mruby, without never taking care to really try it out. I finally thought it was the right time do it and… voilà : I wrote an mruby build config for my remarkable 2. Everything being statically compiled, by cross-compiling it against curl and the mruby http stack give me again a light and efficient runtime to execute my ruby scripts, without having to dealt with complex openssl bash wizardery.

2/3

If you want to try it out, I also wrote a rake file to automatize all the build.

Have fun :)

- #mruby build config for #remarkable 2: https://git.umaneti.net/various/tree/remarkable/remarkable_rm2.rb
- Rake file to build: https://git.umaneti.net/various/tree/remarkable/mruby.rake

remarkable_rm2.rb « remarkable - various - Various pieces of code in a monorepo