News for hackers. Stuff that matters.
Re:Go Creeping In by jstimpfle on Tuesday June 18, 2019 @11:15AM (#20214007)
This is the same reason why I love C, and why I think that, for projects larger than a 1000 lines, it allows me to be MORE productive than more sophisticated languages. Possibly even resulting in a smaller linecount, but at the very least less accidental complexity.

One small red/blue pain point in C is varargs - for most varargs functions I have to make a "..." and a "va_list" version.

Re:Go Creeping In by tracker1 on Tuesday June 18, 2019 @01:11PM (#20215452)
When using a C library, who's code is responsible for allocation objects? Who's is responsible for freeing said objects? That alone leads to a LOT of issues.

Not to be evangelical, but give Rust a look.

Re:Go Creeping In by jstimpfle on Tuesday June 18, 2019 @02:06PM (#20216308)
Seriously, all these language mechanisms like RAII make it a lot harder to write modular code. Look at the mess that C++ got itself in, with its constructors, default constructors, move constructors, rvalue references, exceptions (required as a consequence of constructors), and what not. It's hard to believe Rust could make it significantly less painful.

Programming is mostly not about initialization and deinitialization. If it is, you're doing it wrong, you have too many small objects.

Yes, stack allocated STL containers can be nice for quick "scripting". But I will happily write a few function local deinitialisations to enjoy much less convoluted and interdependent, slowly compiling code.

Re:Go Creeping In by steveklabnik on Tuesday June 18, 2019 @04:16PM (#20217909)
Rust makes it less painful by not having constructors, default constructors, move constructors, rvalue references, or exceptions.