There may be cool cases for extra GenServers or gen_statems but a lot of uses of Elixir and Phoenix don't warrant making any fancy architectural choices. Partly because the runtime is already fancy for you.
3,352 karma · joined December 6, 2016
Podcasting on beamrad.io and regprog.com
There may be cool cases for extra GenServers or gen_statems but a lot of uses of Elixir and Phoenix don't warrant making any fancy architectural choices. Partly because the runtime is already fancy for you.
But it is not necessarily a dealbreaker. Good research, good writing, funny timing, great editing. All of these can elevate the whole. Or being exceptional at one or two can compensate for missing one.
CGP Gray does well without a face and started with terrible animation.
By being unreasonably reasonable in this way I would expect they bring the most members of the community with them if a fork has to happen.
They also leave a door open for Matt to leave this effort alone or even welcome it. A potential road to recovering trust over time.
I think the language and ecosystem are fairly general-purpose but there are definitely a lot more general ecosystems. I think some of the big wins both Erlang and Rails have achieved (that Elixir build off of) have been about constraining the problem to be "a service" or "a web app with a database".
So you are spot on there.
One of the things I've found Elixir to be surprisingly nice for is as a replacement to my Python and Bash scripting. Shelling out is occasionally awkward but Mix.install is glorious and Task.async_stream is hilarious.
There are many dead efforts to implement something like the BEAM or OTP within other ecosystems. Usually not as a VM.
https://github.com/elixir-desktop/desktop
And a different variant driven by the server typically:
https://github.com/liveview-native/live_view_native
Not to say it is particularly ideal. But it exists.
AtomVM is to my knowledge a lot of steps further down since they run a much lighter VM than the BEAM. It is also much less proven though.
Nerves, Grisp and AtomVM all do some of the same things. They make some different trade-offs. Heck, Kry10 (proprietary but targets critical infra) even sort of approaches the same thing. Running Erlang/Elixir for resilient embedded systems.
I am on the Nerves team so you can guess my preference. But all are cool. And we all talk to each other. AtomVM is the most obvious complement to Nerves since they target different device classes.
Especially if you know how easy it can be to accidentally do something that works fine in other browsers but makes Safari kill the tab.
Doesn't actually brick the device but a fairly hard failure in the browser.
From the post I can't tell it's actual reach or impact but it certainly seems to have been a significant piece of work in terms of scope.
I hope to still noodle on open source in my retirement (when it is time) but I could certainly see wanting to get out from under the many expectations.
The interesting part is that the main marketing and sales is by word-of-mouth and quality of product. All the hardware is not even on the website, which was very confusing to my understanding when writing. It makes sense under the resource constraints.
I can spill all the juicy details as the main author and instigator.
Cyanview reached out to me to help find a dev a while back. Hearing about their customers I knew it would be a decently big splash for Elixir. I was surprised that they were unknown and had this succcess with big household name clients.
I like them. I like their whole deal. Small team, punching above their weight. Hardware, software, FPGAs and live broadcasts. The story has so much to it. David and team have been great sports in sharing their story.
Fundamentally I care more about Elixir adoption though, I reached out to the Elixir team and offered to interview them and write something up.
A case study about successful Elixir production deployments is definitely content marketing. But for Elixir. It is a very common question when mentioning a less common language. "Who uses this?" I thought it was a very interesting case. Glad to have it documented. The style of a case study won't suit everyone.
I suppose "without any marketing, before _this_" would have been funny.
I suppose FX30, FX3 and FX6 is in Sony's cinema line and may have all the color stuff that these systems want to tweak but I'm not sure. These cameras do get a fair bit of play on YouTube.
This approach targets more performance-sensitive cases with stuff like passing data frames around and vectors/matrices that are costly to serialize/deserialize a lot of the time.
And it seems to make for a tighter integration.
Chris Grainger who pushed for the value of Python in Livebook has given at least two talks about the power and value of FLAME.
And of course Chris McCord (creator of Phoenix and FLAME) works at Fly and collaborates closely with Dashbit who do Livebook and all that.
These are some of the benefits of a cohesive ecosystem. Something I enjoy a lot in Elixir. All these efforts are aligned. There is nothing weird going on, no special work you need to do.
Every now and then you run into these small-ish expert consultancies that actually are the force behind a lot of open source.
They seem awesome.
Minecraft and Factorio are both simpler productions in terms of visual fidelity and lean on gameplay that is captivating. AAA is not a label for the quality of game, more of a style/level of execution.
Both Minecraft and Factorio started indie to my knowledge which is a separate path and approach from AAA games. Unrelated to good/bad.
DockYard has built out LiveView Native which does a wild React Native style based on the LiveView server-rendered model.
Using Elixir from Gleam can be troublesome due to Elixir macros. I find macros quite important to the Elixir ecosystem but since they don't work in Erlang (and Gleam) they have some drawbacks in terms of of interop.
Bit of a fixer-upper.
Akkoma was a forward and more resource-efficient variant built in Elixir. Last I checked.
There are a gajillion *key forks. Think Misskey was the starting point.
Honk seems fun and is in Go.
Fediverse is not one software package. Mastodon is. Many are Mastodon-compatible.