IMHO the differentiator is deeper yet everywhere engrained in OTP/Behaviours and the famous "Let it crash" slogan. It is the OS-Style process and resource isolation. That is something you can't port with a library into a language that doesn't have it built-in. Lightweight processes, are not the same if they can crash each other, or messup some shared objects/resources/...
You can implement actor behaviours in go or node or even c, but without that lower level support it will never give you the stability guarantees that Erlang process isolation is giving.
To draw a weird comparison Elixir (with Erlang process isolation) brings two world together. First it's a PHP/Ruby level of fire-and-forget productivity because each http request is handled in an independent isolated process, which if it crashes won't affect the system, but instead provide automatically a nicely debuggable crash log. And second it provides natively all distributed tools for long-lived systems. E.g. PubSub , Sessions and database connections don't have to be rebuilt like in ruby/PHP on a per request basis but can be their own long-lived processes.
If there would be a library that could bring this easy to use process isolation+communication e.g. to C programming it would be a game changer. But the best you get in all other languages I'm aware of is to use actual process isolation (fork multiple node/ruby/go processes) and then use some kind of IPC manually or redis or k8s...
I've been using https://remotedesktop.google.com/ for quite some time now with both Linux and MacOS because it provides the best latencies. Anyone knows what protocols it's using? And is this feature set part of the open source chromium distribution as well?
There is something fundamentally flawed in the maintenance cost of the Deutsche Bahn. According to the Deutschen Instituts für Wirtschaftsforschung (DIW) it's costing the Deutsche Bahn 312,000€ per year to maintain a single kilometer of rail tracks. Given that and the already high subsidies of 10 billion € just to keep DB running, any kilometer additional track built is just increasing that hole.
I feel we are in a shit triangle here. Ticket prices are too high <-> quality is too low <-> overall cost is too high. There have been ongoing attempts to fix this by increasing rider amounts but at Germanys population density it's impossible to ever get even near to Japanese levels [2] of low total kilometers built with high usages. After my interpretation of things there is some innovation necessary to bring the per KM cost down before the Deutsche Bahn can play a more important role in the transportation.
On the same coin the cost of public transport for families vs. car ownership is just ridiculous. I've got a family of 5 - For every German intercity route going by car is significantly cheaper than going by train - usually 5x cheaper but often more. Same is true for traveling within a city that isn't your hometown (where you might have a monthly ticket). At this point I'm not even sure whether this is a problem that can be solved socioeconomicly.
I feel electric cars, robotaxis and in the future electric planes are much more likely to solve the larger part of of transportation than that railway is going to do it. Especially given that building another set of rails now in Germany is going to take from planning to delivery 15 years. The change of technology should be planned in.
Anyone having experience with contabo.com? I've got a couple of VPS there and so far pretty happy but didn't yet have any more involved interaction with the team or support to fully judge. No managed DBs but object storage as well.
You can implement actor behaviours in go or node or even c, but without that lower level support it will never give you the stability guarantees that Erlang process isolation is giving.
To draw a weird comparison Elixir (with Erlang process isolation) brings two world together. First it's a PHP/Ruby level of fire-and-forget productivity because each http request is handled in an independent isolated process, which if it crashes won't affect the system, but instead provide automatically a nicely debuggable crash log. And second it provides natively all distributed tools for long-lived systems. E.g. PubSub , Sessions and database connections don't have to be rebuilt like in ruby/PHP on a per request basis but can be their own long-lived processes.
If there would be a library that could bring this easy to use process isolation+communication e.g. to C programming it would be a game changer. But the best you get in all other languages I'm aware of is to use actual process isolation (fork multiple node/ruby/go processes) and then use some kind of IPC manually or redis or k8s...