254 karma · joined January 14, 2020
A lot of the fancy abstractions don't make sense until you have a problem where you'll actually need them. Artificial problems, like some algorithmic assignments in books just don't click nearly as well to many of us.
Just the other day, I don't know if serious or not, I read the Phoenix framework's author say I solve 100% of my dialyzer issues by not using dialyzer on Slack.
Edit: phrasing
Generally, it may not be so common to find an individual who's almost equally as passionate about all of these things. In the end we got limited time on this planet and can't learn everything.
I suppose subscription model makes more sense for apps that basically reside online or at least interact with a web server.
How you make lots of small products solving a single problem well is cool though! I could see some of these kinds of concepts evolving into a decent subscription business.
There's some work being done to overcome this but so far no solution has seen the daylight in practice.
I don't have any first hand experience with such a situation myself, but perhaps studying some successful cases could get you to the next step: https://www.indiehackers.com/interview/how-charging-money-fo...
Haskell's compiler will generate all the logic for serialization and deserialization, leaving me to only implement the actual business logic.
It may be wrong to say we need a better Erlang, but for modern web development we certainly could use a fair bit more compiler enforced type safety for writing more correct programs. Mostly due to the lack of a proper type system, Erlang is not particularly expressive as a language, although its primitives (processes & message passing) are well geared exactly for what it focuses on.
Erlang focuses strongly on fault-tolerance and subsequently on high availability, but I'm not sure this perk is so significant benefit anymore compared to various other runtimes spinning the wheels of your typical web server in a cloud setup. We rarely need to write servers anymore that keep running for many years straight without a restart, only patching code via hot reloads.
Just my take but since you asked, trading some fault tolerance for more correct programs would therefore probably be a fair trade-off for a new kind of Erlang.
Edit: typo
For pure parallel computing it introduces unnecessary overhead because of the message passing. That overhead in turn hurts performance, which really is the only reason you'd want to compute in parallel.