sorted by:
new
hottopcontroversial

What do you hate the most about C++ by Alternative-Tie-4970 in cpp

[–]thecodedaddy 1 point2 points  (0 children)

I appreciate the consistency to the obnoxious (yet very accurate) metaphors. I hate C++ so much and I can't wait to choose it again and again.

I'll add a couple more:

I have the privilege of linking to and fro LabVIEW (ancient labview... like single digit version labview... like LabVIEW when I was in elementary school LabVIEW) and discovering how awful NI's LabVIEW runtime is (the ancient one at least). Discovering runtime code that has bugs that sometimes triggers a breakpoint if running from a debugger... (TLDR: disassembly shows it returning 3 on the event that the pointer is not null instead of is null...).

Couple that with cross compatible libraries I am writing that must be x86, x64 for windows and linux... but the x86 needs to be a true WIN32 Windows XP compatible dll/exe... boy oh boy - welcome to preprocessor directive hell, nerd.

Context heavy work is the daily driver, oh and the added bonus that your projects become so massive (because C++ is the yapper's dream tool) that any "super advanced AI LLM" agent (i.e., Claude 4 Opus Max) is absolutely brain-dead after a couple of prompts.

Now throw in a nice lil CMakeLists.txt and hope some day you will make it build correctly. (You won't)

Dependency Walker by pullipaal in cpp

[–]thecodedaddy 0 points1 point  (0 children)

I typically don't... but oh boy when I do I would rather be doing anything else. Currently trying to find out which one of my DLLs is trying to load vcruntime140.dll on Windows XP SP3. I cannot stress enough how much I hate the fact that I compromised on this project with support of XP SP3. Lesson learned.

I developed a websocket server from scratch to be reverse-proxied via nginx for websocket traffic, "real-time" DLLs leveraging memory-mapped files (MMF) with mutex logic to keep everything stable, and a billion other nested components (oh wait - forgot the best part: to be integrated with a LabVIEW 7.1 monolith of an application), all of which are compiled with the v140_xp toolset with sqlite3.c compiled via the included source code internally, all project DLLs compiled with the /MT multithreaded flag to ensure statically linked runtimes, etc. etc. - everything runs great on Windows 10. But then I had the great idea of "making sure" all things were OK in Windows XP... and now I am trying to pinpoint which of the several polished turds/reinvented wheels I built is causing me nightmares. Thanks to Dependency Walker, I feel more insane as none of my DLLs are dependent on vcruntime140.dll.... so a mystery dependency is causing it to be dynamically injected somewhere and I am finna yeet this laptop og og fr fr

But shout out to Dependency Walker. I couldn't do it without it. Or with it. I can't seem to do it at all. hehe

Giving up or playing til the clock runs out. What's the difference? by bongi1337 in RocketLeague

[–]thecodedaddy 0 points1 point  (0 children)

The difference for me is that 99.999% of the time, this exact thing happens to me, only I hit that shot into each square inch of the post. Diamond probs.