4,418 karma · joined February 1, 2011
[ my public key: https://keybase.io/erikmcclure; my proof: https://keybase.io/erikmcclure/sigs/7L587gG8sECiKPJ7-eL8FW4vCwNQahTkYT60jtaExKE ]
This occurs so often and with such regularity I am now convinced that everything I write is riddled with bugs that I will probably never find without beta-testing in real-world scenarios, plus many more bugs I will simply never find because they never come up.
A much better design would be a test platform that analyzes the assembly structure to pinpoint actual edge cases in the code itself, which could then be used as a guide for finding bugs instead of relying on hundreds of thousands of test cases.
That isn't to say erlang or any other language isn't worth learning (they are), its just that no language can save you from bad programming.
Sometimes, games are the most useful thing one could ever work on.
People keep asking if good security is even practical. Security experts know it is, but nobody else does. If the incentives you describe were actually working, we would be properly assigning blame to bad security, instead of everyone simply asking if good security is even possible.
These terms are not contradictory. Anyone can use and distribute the code for whatever purpose, and any changes made to the code must be made available to the open source community, just like the GPL, except now only that part of the program must be released as source code, and the unrelated portions of the program are free to remain proprietary. This isn't incompatible, and it isn't the GPL.
You are correct in that it is entirely possible for me to do both college and startup at the same time, I just don't want to be carrying a 5 pound rock with me on a marathon if I don't need it.