3 ms·
> The painful bit is C++. I did a fair bit of that going back to MFC. I'm sorry but referring to MFC while referring C++ is a telltale sign you don't really ha
by chipdart 2y ago
> The painful bit is C++. I did a fair bit of that going back to MFC.
I'm sorry but referring to MFC while referring C++ is a telltale sign you don't really have any meaningful experience in the field. Developing GUI apps for Windows is a breeze with frameworks like Qt. You only suffer if you're a masochist, but the rest of us prefer to pick things that make sense.
- cjk2 2y agoI have a lot of experience, in the real world, which is somewhat less ideal than "just use Qt - it's a breeze". How do you manage a 15 million LOC desktop app originating from the late 90s which contains chunks of win32 native, ATL, MFC, custom GDI+ wrappers all sorts? Aye you fuck off and work somewhere else that's what you do. Which is why it's still written in win32 native, ATL, MFC, custom GDI+ wrappers. They paid two companies to come in and rewrite it, first in Qt which was a complete failure. Then in Electron etc, which was also a failure.
- chipdart 2y ago> How do you manage a 15 million LOC desktop app originating from the late 90s which contains chunks of win32 native, ATL, MFC, custom GDI+ wrappers all sorts? You're complaining about your personal legacy "chunks of win32 native, ATL, MFC, custom GDI+ wrappers". Not C++. Just your personal legacy projects you didn't managed to maintain or update. C++ doesn't magically rewrite your technical debt. You need to do your work.