News for hackers. Stuff that matters.
Re:One year of C by blt on Saturday June 02, 2018 @06:30PM (#17216754)
I guess you are getting down voted for lack of content, but I agree. Those are all very bad "Java without GC" C++ practices that lead to awful code bases. Thankfully the author seems to have learned that from their experience writing C.

Like the author mentions, C++ leads to overthinking which language features to use. It invites you to seek these perfect abstractions for Python readability with C performance. I think this is a big reason everyone develops their own incompatible style -- not due to passionate philosophical beliefs, just to reduce the size of the solution space.

Re:One year of C by pmarcelll on Saturday June 02, 2018 @08:39PM (#17217243)
I agree with you, mainly from the perspective of writing Rust code. When Rust was new, a lot of people said that thinking about ownership all the time is a burden, but I think it's the opposite, it gives a sort of frame that helps to build the software's core abstractions. I think in this regard C++ is much more unopinionated, which means every codebase is different. In Rust, ownership is part of the type system, so a lot of the times learning a new API can be much faster because API usage is easier to understand and this style of programming is already familiar.
Re:One year of C by blt on Saturday June 02, 2018 @11:35PM (#17217787)
yes. ownership is an extremely critical part of software design, especially for complex interactive programs.