Roads Less Taken

Work on Spry continues… in small spurts. :) One thing that I have pushed ahead of me for far too long is error handling.

Back in 2018 I got into crypto currencies.

I have already written three different articles explaining how CORE floor price can be calculated.

In the previous two articles I explained the principles behind CORE’s floor price, the lowest price that CORE can reach and ended it all by explaining the “q method” that works for any number of CORE pairs.

In the previous article I explained the principles behind CORE’s floor price, the lowest price that CORE can reach.

The last month I have gotten involved in a fairly new crypto currency project called CORE , or cvault.finance .

After a period of slower progress I got reignited regarding Spry .

I have always entertained thoughts of making my own programming language.

Since learning Smalltalk at KTH in around 1994 - we used VisualWorks 1.0 IIRC - I have been deeply in love with both the language, its mindset and the community with all its diversity.

In 2014 I discovered the programming language called Nim , earlier named Nimrod, created by Andreas Rumpf.

I have followed Dart from the corner of my eye since the inception - after all, Lars Bak , one of the creators is a very well known man in the Smalltalk/Self/OO world, so it had to be interesting!

I am Göran Krampe and this is my blog where I mainly write about software development.

Slides Link to heading http://krampe.se/kth-messaging-2018.pdf - These are my slides I showed at the lecture.

In the eCraft2Learn project which Evothings is participating in we were looking at various ways Nim is an awesome programming language and this article is a whirlwind-copy-paste-into-your-terminal-as-you-read-thing to show how you install Nim, write a sma…

Nim is an awesome programming language and this article is a whirlwind-copy-paste-into-your-terminal-as-you-read-thing to show how you install Nim, write a small program, compile it and package it in a very short time.

Spry is evolving quite nicely during my night hours.

I love Smalltalk and I have been in love with it since approximately 1994.

In my quest making Spry I also learned about other efforts in the Nim community to construct Smalltalk-like dynamic languages.

When writing Spry I am so far mainly ignoring performance.

Allen Wirfs-Brock wrote down a bullet list of what he thought actually made it possible for the Alan Kay team to create Smalltalk , and many other ground breaking things, at Xerox PARC in the 70s.

In the last article I outlined a simple model of modules and that is kinda implemented but needs a few fixes.

As discussed in the previous article I want Spry to have a trivially accessible persistence mechanism enabling something similar to the Smalltalk image model, but based on a database.

In developing Spry - renamed from Ni - I am getting closer to the Really Fun Stuff.

When I started out implementing my own language in Nim I named it “Ni” without that much thought actually.

I now work as the Team Lead at Evothings and our open source product is a Workbench for creating mobile HTML5 applications focused on IoT, by editing and running them live on the mobile device inside our spiced up Cordova based “Evothings Viewer”.

I have just started working at Evothings !

It seems like the “damp cloth of Java” that has been plastered all over the programming landscape the last 20 years is finally being lifted.

So… Ni has almost reached the point where I can see objects appearing.

So… my little Ni language got some attention since it was first on Hackernews , then TheRegister , all over Twitter and also Reddit .

The language formerly known as “Ni” is now called Spry .

This article describes some core parts of the current implementation of the Ni (now known as Spry ) language.

Ni is my own little language heavily influenced by Smalltalk but also other sources like Rebol, Forth, Lisp, Self and Nim.

As I described in the earlier posts Nim didn’t support “super calls” when using methods instead of statically bound procs and generics.

Yesterday I had the pleasure of presenting the programming language Nim at the Stockholm GTUG .

Having been a die hard Smalltalker since 1994 I have finally found a new language and community that I am investing myself in.

One of the most important aspects in a language is how powerful and easy it is to use its collection/container types.

As I described in the earlier posts Nim didn’t support “super calls” when using methods instead of statically bound procs and generics.

In my exploration of Nim the turn has come to see how we can use Nim together with Squeak .

So previously in Nim and OO Part II we saw how we could solve the “super call” issue using only procs and generics in Nim .

In the previous article when I explored OO mechanisms in Nim I felt I dropped the ball a bit in my Fruit example.

A friend of mine is having a less optimal experience with Linux, and I realized I could jot down my experience for the last few years.

Nim is presented as an imperative language.

In learning Nim I decided to implement a trivial Socket server, very small, as an example.

A year ago I wrote an article trying to round up new languages since year 2000 and what I think of them by just… glancing at them, or otherwise playing with them.

Nim has all the language mechanisms needed to smoothly interoperate with C and C++.

Technically Nim is still called Nimrod up to and including upcoming bugfix version 0.9.6.

I just posted an article comparing some silly benchmarks between Cog Smalltalk and LuaJIT2.

In the open source Smalltalk community we have a pretty fast VM these days - its called Cog and is written by the highly gifted and experienced Eliot Miranda who also happens to be a really nice guy!

It starts off with Cincom, Arden Thomas presenting their roadmap.

Day three blurred a bit for me - lots of mingling and hacking intermixed with some nice presentations, but I missed quite a lot, I admit, like the presentation on new native UI stuff in VisualWorks and the tODE stuff from Dale Henrichs.