News for hackers. Stuff that matters.
Re:Checked C: Making C Safer by Extension by emilfihlman on Sunday September 09, 2018 @06:50AM (#17945309)
Do you see the difference between "Here's a very small change, easy to implement and add." and "Let's just rewrite the whole thing and buy new devs" ?
Re:Checked C: Making C Safer by Extension by saagarjha on Sunday September 09, 2018 @06:59AM (#17945336)
Yes, I do. But the unfortunate reality is that your "small change" makes your code much harder to work with for other people, since you are now writing a C derivative instead of standard C.
Re:Checked C: Making C Safer by Extension by stefano on Sunday September 09, 2018 @08:48AM (#17945664)
This is the same argument that was used when Microsoft launched Typescript. As it turns out, their strategy of extending an existing language to make it safer worked great, while brand new languages that are safer than Typescript are now miles behind it in terms of adoption. So it seems to be a pretty solid strategy, and if it brings people closer to a safe language, even if not 100% safe, it's still an improvement on the status quo.
Re:Checked C: Making C Safer by Extension by vmchale on Sunday September 09, 2018 @11:56PM (#17949283)
> As it turns out, their strategy of extending an existing language to make it safer worked great, while brand new languages that are safer than Typescript are now miles behind it in terms of adoption

Did it? Adoption seems to me to be a pretty silly metric given all the politics of language choice.

Re:Checked C: Making C Safer by Extension by pjmlp on Monday September 10, 2018 @02:08PM (#17953702)
Given that the goal is getting C developers to adopt best practices, adoption is the most relevant metric here.