Re:Languages on BEAM, the Erlang virtual machine
by Cyph0n on Friday January 20, 2017 @07:45PM
(#13448136)
What kind of web developer needs to care about cosmic rays and bit flips? Genuinely curious here.
[ Parent
| on HN ]
Re:Languages on BEAM, the Erlang virtual machine
by posterboy on Saturday January 21, 2017 @09:41AM
(#13450190)
at least those like NASA who use space-grade (radiation hardened?) microchips
Re:Languages on BEAM, the Erlang virtual machine
by Cyph0n on Saturday January 21, 2017 @01:37PM
(#13451377)
That's not what I'm talking about at all.
My issue is that the original commenter listed "resistance" to bit errors as an advantage to using Elixir vs. other languages for web dev.
The question then becomes: who the hell needs bit flip resistance when building a web app?
Re:Languages on BEAM, the Erlang virtual machine
by posterboy on Sunday January 22, 2017 @08:42AM
(#13455141)
I'd say it's a metaphor for more likely bugs, the gammaray bitflip being the most meta of them all. What do you think ecc-ram is for?
Re:Languages on BEAM, the Erlang virtual machine
by Cyph0n on Monday January 23, 2017 @11:35AM
(#13463395)
Exactly. ECC takes care of 99.99% of cases, so I don't see what using Elixir has to do with any of this.
Re:Languages on BEAM, the Erlang virtual machine
by angersock on Friday January 20, 2017 @09:50PM
(#13448485)
Any web developer whose software runs on computer hardware. Otherwise, you should be fine.
Re:Languages on BEAM, the Erlang virtual machine
by Cyph0n on Saturday January 21, 2017 @12:50AM
(#13449025)
I still don't see why the parent commenter decided to include recovery from cosmic rays as an upside to using Elixir. I'm sure web devs everywhere are throwing out their current tools for this huge advantage! In any case, commodity server hardware already takes care of SEUs through ECC memory.
Re:Languages on BEAM, the Erlang virtual machine
by nkurz on Saturday January 21, 2017 @02:21AM
(#13449249)
Memory corruption from cosmic rays may be more common than your intuition suggests. This article cites a 2009 study of a large cluster that found single-bit ECC corrections occurring about 1 per minute per TB, and uncorrectable double-bit errors at a rate of about 1 per year per TB:
http://spectrum.ieee.org/computing/hardware/how-to-kill-a-su....
Whether this is frequent enough to warrant consideration depends on your application, but there are definitely people here who care enough about how their systems recover after errors of this sort that it's not an absurd suggestion.