thinking about how there's a nontrivial set of programmers who are gungho about both "if you use after free that's your fault for not programming better you inept clown" AND "no i need the computer to tell me not to call an integer like it's a function", simultaneously

according to hacker news, the ideal programmer can keep the entirety of a massive complex system in their head all at once and instantly analyze all possible data flow paths, but is a total fucking idiot when it comes to basic local tasks like adding numbers together

once again fondly recalling the guy designing a DSL who insisted on static types because how can you possibly program without them, but refused any kind of static null checking because c++ doesn't have that and it works fine so it must be unnecessary

@eevee still amazed that most people don't consider null a violation of static typing

@unascribed that drives me up the wall but honestly the explanation seems to be that c++ programmers think "static typing" is literally "whatever c++ does", similar to how they define OO

@eevee @unascribed tbf try to use an uninitialized std::unique_ptr and it will casually scream at you about it tho. Also, new and delete do not exist. They do not. No.

@Archivist @eevee @unascribed ah yes and every programmer must learn all of the many disguised ways of calling constructors, like "list::emplace_back"

Follow

@Archivist
sorry I just learned that one this week and any perceived hostility was directed at C++, not you :)

Β· Β· Web Β· 1 Β· 0 Β· 1

@fraggle Don't worry haha, I don't take things against myself. You have several ways to actually construct stuff in C++ and most courses are outdated or given by people that did Java for their entire life

Sign in to participate in the conversation
Octodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!