Links language: Linking Theory to Practice for the Web

[AstonJ]

So… an isomorphic language for the front and back (but not mobile) end?

What does it offer that other ‘isomorphic’ languages don’t? Some of them (like Ruby) let you make mobile and desktop apps as well as to be used on the front and back end. Also what about scaling and concurrency etc? Will it take 20 years to get as good as Erlang/Elixir on that front?

Links incorporates proven ideas from other programming languages: database-query support from Kleisli, web-interaction proposals from Racket, and distributed-computing support from Erlang. On top of this, it adds new web-centric features of its own.

So very similar to…

@AstonJ

I heard Crystal folk say they want to implement something like the Actor model that Erlang has, but I’ve also heard @joeerl (I think in relation to Java stuff) say something along the lines of that sure, anyone can implement a similar model to Erlang - but then they’ll need 20 years to get to where Erlang is at. Erlang wasn’t just built and then stayed the same - it was worked on, tweaked, enhanced over a couple of decades to get it to where it’s at today