The frustrating part of #Erlang is that the language is so well designed that I always want to go back to it even though the ecosystem is a huge PITA. I should probably start to extend what I already wrote on the build part to handle more complex systems with dependencies.
I finally finished my article on how to build #Erlang applications from scratch. If OTP applications and Erlang releases are still opaque to you, this should help.
Y’all: I have been wrestling with kbin on the fedia.io instance, but I want to take a step back and give some perspective. Kbin is new, it’s growing crazy fast, and it really wasn’t in a place to support the migration from Reddit. Despite that, @ernest has been working his tail off knocking down issues and helpings instance admins.
Reddit certainly seems to be tripling down on their position and I think kbin is shaping up to be a worthy alternative. If you like kbin (on whatever instance you use it on) and want to see it grow, may I ask that you throw some money Ernest’s way? (https://www.buymeacoffee.com/kbin)
I want to publicly thank Ernest for kbin and for his contributions to our growing fediverse community.
I'd still recommend something like #Erlang to handle that sort of horizontal scaling sanely, but having something currently working (however efficiently) is still good.
#CommonLisp type declarations are a life saver, but they are fundamentally limited: you cannot use them to express that a list contains elements of a specific types. Frustrating given how ubiquitous lists are. #Erlang type specifications are much more flexible.
You know, I like #erlang, but one has to seriously consider wtf is going on when +0 being equal to 0 is considered a bug and then, they double down on it and write code to enforce it.
I'm sure there's some logical reason, but still w.t.f. a) positive and negative zero are nonsensical ideas b) no reasonable person wants 0 to not equal 0.
One of the things #Elixir helped me remember, is how cool it is to create complex systems without the overhead of microservices. At first, it was even a bit confusing because I constantly had the feeling that I'm forgetting something ("What? How come that's all I have to do and not a single line of YAML had to be written").
Not exactly #smallweb but definitely medium-sized blobs of developer happyness :).
It seems like it is a rewrite/alternative server to the mastodon server. Looks to be written in Rust. It is a fork of #misskey, which seems to be written in typsescript
But since it uses ActvityPub, it's interoperable with Mastodon
Seems like you can't migrate your Mastodon account over.
So basically an alternative microblogging interface to the fediverse with different server software.
After 4 years on the board of the #erlef foundation volunteering to help various things in both the #erlang and #elixir communities (and 1 year before then in the IEUG to bootstrap the EEF), I'm finally stepping down and leaving my position to @Amos -- Long live the Amos King!
(I'll still be around the foundation's build & packaging working group and reviewing stuff for #otel for the observability group—no I'm not fully out of the picture)
Right, #Erlang people, where can I read about generating parsers for binary formats?
I've got something BNF-like; I'm thinking I could (at compile time) turn that into an Erlang module that uses a bunch of binary pattern-matches to parse it efficiently.
tfw you find a script that you wrote a few years ago, and you want to write it up as a blog post, and you can't figure out how you wrote it in the first place.
This post brought to you by the Erlang compiler's +to_pp option, which seems to be undocumented, and I don't remember where I found out about it.
The recording is now available of my talk “How Little Languages Shape the Future” from Orlando Code Camp (#OrlandoCC) on Saturday. A little bit of ranting about language popularity, a little #Elixir, a little #Erlang, and a lot of feeling good to be back speaking after a long pause.