4 ms·
I worked with c++ for many years and it has lots of warts. Slow compilation, lack of decent build system (no cmake isn't that great), mistakes made in the stand
by bnolsen 2y ago
I worked with c++ for many years and it has lots of warts. Slow compilation, lack of decent build system (no cmake isn't that great), mistakes made in the standard library (iostreams), weak cross platform standard libraries were always a headache.
But I always loved the power that <algorithm> and the like provides, although attaching allocators (and other template things) kind of sucks.
When I looked at and test drove rust all I saw was heaps of complexity stacked up yet again. Probably didn't help that I smacked headlong into the Arc Mutex and lifetimes mess. I'm really more inclined to go for something like 'zig' which does so much with simple syntax (and awesome comptime) and still gets excellent performance.
- marssaxman 2y ago> no cmake isn't that great Nor is cmake even really a standard: after thirty-odd years writing C++, I've yet to work on a project which used it!
- PittleyDunkin 2y agoThat's pretty damn impressive! How did you manage to avoid codebases with CMake? Or are you just saying you personally chose not to use it for your own?
- marssaxman 2y agoIt simply hasn't come up: none of the teams I've ever worked on have chosen CMake. I've certainly encountered & compiled libraries which use it, but I've never had any reason to edit a CMakeLists file myself. Of course CMake has only really been a practical tool for 20-ish of those 30-odd years, and "Modern CMake" was only published twelve years ago; it's definitely gained a lot of popularity over the last decade, but the idea that CMake is the default C++ build system, not just one among many, still feels to me like a recent change.
- funny_falcon 2y agoIt seems meson is gaining traction and will overpass cmake in near future.
- scotty79 2y ago> lack of decent build system At one point I was using gulp.js to build my small C++ experiment.