Writing formal specs, and proving your code meets that formal specs, is very hard, very slow work. Data61 proved that their microkernel implements a formal spec. It took them 25 person-years to implement a 7500 line kernel. Very very few software projects justify that level of expenditure.
I agree that system programming should be moving to languages/environments that make safer programming easier though. Why we're still writing non-performance critical code with buffer overflows in 2016 is beyond me.
Sorry, I see nothing about a Mozilla and Microsoft partnership there. Care to be more explicit?
Can you say more about this Mozilla and Microsoft partnership? Thanks.
Who would have thought that programming a car to lie to the US EPA was a good idea? Dozens of engineers at VW, apparently.
...will not bring it under control
Seems preserving free speech is preferable to protecting the feelings of a bad black actress.
Overflow on /dev/null, please empty the bit bucket.