The code editor is for the EYG language and implemented in Gleam. So that's a blocker. The editor is probably far enough along to have a crack at it by EYG would need some UI or web library so that EYG was able to build an editor.
1,201 karma · joined October 13, 2016
Not entirely https://eyg.run/
But I guess only time will tell.
So what's important is that the system already has the language installed and so it's not worth considering options you need to install yourself.
I have been using the following stack. - https://gleam.run/ - https://github.com/hayleigh-dot-dev/gleam-lustre
Despite very early days for the lustre framework, the type safety it inherits from gleam makes development very fast.
https://petersaxton.uk/log/ Week 1 & 2 I mostly introduce the structural editor, later updates have been more about language development
The goal is education. People who are newish to programming often don't know why printing to the console is exciting so I hope that this might be a more engaging place for examples.
I saw the await key word for parallel fib but would like a bit more information about what's actually happening to be parallel.
But how do you measure success, we're a messaging app. - Total messages sent - Number of conversations.
Measuring any of this will mean we optimise keeping users on the platform.
We're trying active conversations, where to be active means only at least one message per week. We'd love to find a metric which went up as each individual user spent less time on memo. A "time to solution" metric