Re:What every compiler writer should know about programmers ...
by DannyBee on Thursday March 03, 2016 @11:10PM
(#11222000)
Sure, but that's also a fine outcome - everyone decides language X sucks and moves to language Y.
If that language Y guarantees things nicer than language X, you've solved the problem :-)
Re:What every compiler writer should know about programmers ...
by aidenn0 on Thursday March 03, 2016 @10:35PM
(#11221914)
This is a very good observation. The exception is strict subsets though; there are plenty of people using MISRA, and that's an extremely restrictive subset of C. Similarly this would be a dialect of C that is identical in behavior for conforming C programs, rather than C with some extensions.
The solution (for me, anyway) was to create an entirely new language. The changes that nobody wanted in C (not because they were bad, but because they were non-Standard) found plenty of traction and users in D.