5 ms·
I had this to say about c++/go recently: Working on a c++ project: I feel stupid... and nothing works. Working on a golang project: go is stupid... but everyt
by justinsaccount 11y ago
I had this to say about c++/go recently:
Working on a c++ project: I feel stupid... and nothing works.
Working on a golang project: go is stupid... but everything works.
My issue with c++ is someone needs to write a "c++: the good parts" I may end up with rust, but right now I look at the documentation and some rust code and it's a bit overwhelming.
Go may be stupid in a lot of ways, but for the most part it's pretty obvious how to accomplish something.
- philbo 11y agoIt's not exactly the same, but the closest thing to a "C++: The Good Parts" is Scott Meyers' "Effective C++", imho.
- bloodorange 11y agoUnfortunately, there are no updated versions of his books for C++14 or 17. I owe a lot to the books though.
- santaclaus 11y agoEffective Modern C++ covers C++14, and specifically points out where it differs from C++11 (I'm thinking about the discussion of decltype, here).
- lmedinas 11y agoTrust me even though it's not updated everything he mentions in the book is still valid. If you want to really know more about specifically modern C++ there is always Modern Effective C++
- saboot 11y agoThe C++ standards committee has started a guidelines document which encompasses the latest features of C++11/14 https://github.com/isocpp/CppCoreGuidelines https://github.com/isocpp/CppCoreGuidelines
- ricksplat 11y agoIs this the same site linked in the article?
- ricksplat 11y agoI think Scott Meyers' "Effective C++" may be the "good parts" book you're looking for. As well as telling you how you should write "good" C++ it's also pretty good at explaining when you should break these rules too.