Spry Performance

Tue, 24 May 2016 00:00:00 +0000

When writing Spry I am so far mainly ignoring performance. The general execution of Spry code will be a regular interpreter (although stackless I hope) and not a JIT. But that doesn’t prevent us from playing around and learning something!

In this article I do some silly experiments around interpreter startup time and fooling around with 40 million element arrays. As usual, I am fully aware that the languages (Pharo Smalltalk, NodeJS, Python) I compare with a) have lots of other ways to do things b) may not have been used exactly as someone else would have done it. A truck load of salt required. Now… let’s go!

Evothings + Phoenix = Neato

Mon, 14 Dec 2015 00:00:00 +0000

I have just started working at Evothings !

It’s a fun gang making slick development tools and libraries for building mobile IoT apps. Evothings is pushing the envelope on really easy mobile development focused on all the new nifty IoT-devices flooding us over the next few years.

In my last article I predicted Elixir to become big and now that I am learning the Evothings tools I wanted to make an Evothings example that uses Phoenix , the Elixir web server framework, as a backend, using its channels mechanism for websocket communication.

Coinciding with the release today of Evothings Studio 2.0 beta 2 (yay!) I will show step-by-step how to:

Install Evothings Studio locally. It’s just unpacking a zip :)
Make sure we can run the “BLE Scan” example app and modify it.
Get a Phoenix server up on a Debian/Ubuntu server on the internet.
Modify the app and server to use Phoenix channels for publish/subscribe of scan data.
Verify it all works!

Since not everyone has a Linux server up on the internet you can skip step 3 and just use my public server :)

Let’s go!

JavaScript on Roads Less Taken

Spry Performance

Evothings + Phoenix = Neato