News for hackers. Stuff that matters.
Re:Writing Good C++14 by Default [pdf] by kamac on Wednesday September 23, 2015 @06:28AM (#10264233)
> The whole point of this article seems to be to teach people to by default not poke the ball

And it's sad that they have to teach people not to poke the ball and reveal the inner decay, rather than remove the rotten meat itself.

Re:Writing Good C++14 by Default [pdf] by kryptiskt on Wednesday September 23, 2015 @09:36AM (#10264882)
All serious languages have unsafe constructs that you can use as an escape hatch, even Haskell or Rust. Keeping the ability to do dangerous stuff in C++ isn't a compromise, it is vital. Building tools that makes it easier to separate the unsafe parts is a good thing, other languages got there first but having the possibility to clean up those billions of lines of C++ is great.

Also, it's time to lay off your metaphor, it obscures the issues and trades just on disgust value.

Re:Writing Good C++14 by Default [pdf] by greyman on Wednesday September 23, 2015 @06:46AM (#10264263)
It's not inner decay. It just more possibilities C++ allows you to do, which can give you more power if you know what you are doing.