937 karma · joined March 3, 2011
[ my public key: https://keybase.io/alind; my proof: https://keybase.io/alind/sigs/2pdcFkwnKpwh7sTJFAMZISSpzDDxKc5sOCjs46kAeY8 ]
I wonder how the extreme wealth distribution today will affect this. Although looking at statistics [1] it seems it was even worse in 1922 (no numbers for 1918).
In the end, I feel it's quite comparable to software running on layers of layers of abstraction being maintained by the respective experts in their fields (testing, CPU designers, driver implementers, OS maintainers, etc.).
2. In Erlang it usually only make sense to care about errors which you can actually handle in a sensible way. Everything else you usually "let crash" and let the supervisor tree deal with recovering. Defensive programming is another anti-pattern in Erlang in my opinion.
4. Not sure what you mean with "not great". With Erlang, if you have a completely parallelizable problem you should see close to linear scalability. If it drops of after that it's either because the problem is not parallelizable enough or because of your architecture.
Yeah, I'm not arguing Erlang over Java either. I'm just pointing out that blanket statements like this are usually because of architecture or design rather than shortcomings of the language itself.
Since I absolutely need a cross platform password manager, especially on mobile, I felt this to be the most logical solution.
In the end, Microsoft will get bad reputation for having an insecure OS (not to even mention Valve here, and in the long run it will hurt them as same as it did Adobe with their Flash stubbornness).