Just this week, I had to perform some maintenance programming on an application written C++ in the mid- to late 1990s.
Just this week, I had to perform some maintenance programming on an application written C++ in the mid- to late 1990s. It required Visual Studio 6.0 (!!!) to build. I do not know what features were supported back then, but the application only made use of classes (no inheritance, though, except for GUI stuff derived from library components) and new/delete. (I was really lucky, the code I had to look at was highly readable.) C++, where it goes beyond those simple basics, always gives me mixed feelings. On the one hand, C++ has its good sides (Qt rocks, or at least it did the last time I used it (around version 4.8)), but every time I approach C++, I seem to succumb to the temptation of making things overly complex. I sometimes think the biggest problem with C++ is not learning the language but developing the discipline to use it properly (where "properly" might mean different things to different people).
Posted by krylon on Jun 20, 2015, 12:44 PM
Tags
Related issues
- I mean that's the problem though.
- I've always believed the opposite: get conditionals deep in your code so that the higher level control flow is regular.
- The biggest problem with AI isn't being able to do things.
- I am a 3D printing maker type nerd (I make my own tools for other creative tasks, rather than as their own outcomes) and I saw an incredi...
- Of course not, those are clearly scams.
- Claude makes more detailed plans that seem better if you just skim them, but when analyzed, has a lot of errors, usually.
Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments
hackernews (EdTech)
I mean that's the problem though.
I've always believed the opposite: get conditionals deep in your code so that the higher level control flow is regular.
The biggest problem with AI isn't being able to do things.
I am a 3D printing maker type nerd (I make my own tools for other creative tasks, rather than as their own outcomes) and I saw an incredi...
Of course not, those are clearly scams.
Claude makes more detailed plans that seem better if you just skim them, but when analyzed, has a lot of errors, usually.
Effectively everyone is building the same tools with zero quantitative benchmarks or evidence behind the why / ideas … this entire s...
> creating and operating a small company in Germany is a nightmare To be fair, I think the problem operating in Germany is its federated...
Just this week, I had to perform some maintenance programming on an application written C++ in the mid- to late 1990s.
Just this week, I had to perform some maintenance programming on an application written C++ in the mid- to late 1990s. It required Visual Studio 6.0 (!!!) to build. I do not know what features were supported back then, but the application only made use of classes (no inheritance, though, except for GUI stuff derived from library components) and new/delete. (I was really lucky, the code I had to look at was highly readable.) C++, where it goes beyond those simple basics, always gives me mixed feelings. On the one hand, C++ has its good sides (Qt rocks, or at least it did the last time I used it (around version 4.8)), but every time I approach C++, I seem to succumb to the temptation of making things overly complex. I sometimes think the biggest problem with C++ is not learning the language but developing the discipline to use it properly (where "properly" might mean different things to different people).
Comments (0)
No comments yet. Start the discussion.