2 ms·
Long compile times and bloated binaries do come with the platform for C++, but (with experience) you get pretty good at minimizing both of those with little eff
by yoklov 11y ago
Long compile times and bloated binaries do come with the platform for C++, but (with experience) you get pretty good at minimizing both of those with little effort. This also tends to lead to a fairly clean dialect of C++ (closer to C), and has higher performance code as well. It basically boils down to not really using templates.
That means no stl or boost, but (and this is not a popular opinion at all) this tends to lead to cleaner code, and more productive programmers.
My experience is that templates do allow for more code reuse than you can typically get in other languages, however they do so at a high complexity and maintenance cost -- not to mention binary bloat and long compile times.
- pjmlp 11y agoI use STL and Boost, it seldom goes over 8MB. However stay away from Qt if you don't want over 30MB with almost no mobile support.
- mahyarm 11y agoI've learned long ago that you can't rely on 'good engineers' to keep up good practices over a large amount of people. Eventually the bad practices happen unless it's set as policy by the heads of the C++ platform, and enforced by scripts and management. It comes down to an education thing, since most C++ devs you hire will use boost & STL. And de-templating, removing stl & boost from 300k+ line projects and debugging it all is something most orgs wont swallow.