4 ms·
I've had just as many problems maintaining mature C++ projects as I have maintaining mature Go projects. Ultimately it all boils down to two things: - The pro
by hnlmorg 5y ago
I've had just as many problems maintaining mature C++ projects as I have maintaining mature Go projects.
Ultimately it all boils down to two things:
- The projects being well written and well maintained from the outset
- Personal preference
I cannot overstate that second point.
It really is about time developers stopped pushing their own personal preferences as if it's some kind of fact.
- pdimitar 5y ago> It really is about time developers stopped pushing their own personal preferences as if it's some kind of fact. Agreed, so let's all go to Rust or OCaml because they have very strong static typing systems. ;) Both C++ and Go have plenty of warts, with C++ having way too many footguns and Go allowing you to use it as a dynamic language whenever you figure it's too much work to go through your problem with static types.
- still_grokking 5y ago> Agreed, so let's all go to Rust or OCaml because they have very strong static typing systems. ;) Seems very reasonable. Especially OCaml should get more of the praise it deserves. If you need to stay on the JVM there's Scala which allows (with some discipline) to write "when it compiles it works" code.
- hnlmorg 5y agoYou've very much missed the point of my post. But from the tone of your reply, I sense we'd never see eye to eye anyway.