Appreciate all the work done by the Elixir team on this. If at some point something makes the type system unfeasible, does it mean it would be unraveled from the compiler or is it safe to say what's been released now is there for good?
Maybe Haxe is an example of another language like this. I wonder if it applies though to languages that are hosted i.e. Elixir is constrained somewhat by what Ericsson decides to do w/ Erlang
I only recently discovered minio and started using it for a project. What are you referring to by “last file system-transparent Minio version” for my own awareness?
One reason also is I believe it has something to do with fault tolerance even at a hardware level. A process has its data isolated somewhere in memory, if something happens to that memory, the process will crash next time it runs and starts causing supervisors to start attempting to recover the system
So neat! I've been thinking of something similar to this where content creators would join their content to form channels in the original sense of the word and users would browse much like how they would on a normal TV
> We don't need the Erlang message bus to be the only message bus. The Erlang message bus is, frankly, not very good
Genuinely curious why it's not very good. Were you speaking solely from the perspective of non-Erlang processes? And also specifically regarding remote messages rather than local?
I think OP was asking whether they were confusing CR for the Better Business Bureau because moving services does not seem to be something CR would review
I'm curious what features this hypothetical modern language would have that would be particular suited for financial institutions. This thought has piqued my interest
This actually reminds me of an idea I once had. Rather than service providers holding onto your data, there could be something equivalent to custodians but instead of having lockboxes for your valuables, it'd be for your data. Service providers would then "borrow" your data from these custodians to provide their services.
This looks sort of like that but marketed from the tech angle using docker as an analogy rather than a custodian. I'll have to take a deeper dive into this!
Very cool! Just a heads up there's a bug with the event control flow example where it requires pressing the "stop pulsing" button the same number of times you've pressed the "start pulsing" button. I figured the behavior should be regardless of how many times I've clicked "start pulsing" the next time I press stop, it should stop.
I don't have much too add, I'm just replying in case Mozilla devs see this. I want this so much as well! I don't mind the VPN though. I pay for it now even though I run mostly Linux