3 ms·
Erlang is slower, and beam is not relevant anymore with kubernetes and the like which are much more powerful and language neutral.
by Thaxll 8y ago
Erlang is slower, and beam is not relevant anymore with kubernetes and the like which are much more powerful and language neutral.
- brightball 8y agoI keep hearing stuff like that but it’s not even close to accurate. BEAM and Erlang give you tooling that you can’t get from any other language, regardless of how it’s deployed. Using Kubernetes doesn’t make up for any of that...it just gives you a way to deploy containers.
- Thaxll 8y agoWhat tooling please give an example.
- edholland 8y agostrictly ordered message queues between processes
- brightball 8y agoFor a detailed example, just see the previous posted. There’s a lot. https://news.ycombinator.com/item?id=13497505 https://news.ycombinator.com/item?id=13497505
- battlebooth 8y agoI dont know whether this is a good thing or not.... The best nuggets of information on HN are at the mercy of a good soul digging up the link and dropping it on a new thread. You'd think that this knowledge retrieval/storage problem could have a more elegant solution built by the HN folks. Example solution: Topic X stored in category, ranked to the top, its next 'commit' or successor is chained on kind of like how unroll works with twitter.. but with long HN threads instead. Think a 'git tree' of knowledge descending down, with merges too maybe... Engh.. maybe thats part of the charm of HN... the old school style message board.
- pdimitar 8y agoThe machinery of the BEAM is in-process (and between nodes when you need it). Kubernetes and the BEAM VM address different levels of the architecture. Apples to oranges.