C changed from the 90’s to now. It got a lot of syntactic improvements, and a ton of semantic madness.

Our C is not the same as the last generation’s.

And before the time people actually talked about the multidimensional clusterfuck that C become.

Ok, you are certainly in one of those languages where plenty of your functions shouldn’t return a value, and you won’t ever let the compiler know that.

On all of the other languages, it’s an error, not even a warning.

The problem is, how do you fix it if you can’t make it break?

The worst thing is when somebody comes to you saying “yeah, I had this problem yesterday, but it’s working now”.

Yeah, that won’t happen.

And if you propose a separable set of functionality that you can mix as you like, you’ll get shut down on the base that it’s not viable (doesn’t matter if you had written it already), it’s too complex to understand (doesn’t matter that everybody keeps doing everything wrong because nobody can understand the current one) and YAGNI (doesn’t matter that keeping the current one running takes most of the time from everybody).

IMO, that’s a clear acknowledgment that this is a specification bug.

And that it has a low priority.

It’s a safe bet that anybody trying that jump over it, through the rails routine is a junior.

Ha. I’ve just got a report of “UnknownError at foo in line 162”.

Line 162: bar();

Of course, there’s a foo() nearby, and yeah the error is there. C# also has a problem with sourcemaps.

Anyway, the “UnknownError” is literal from the problem. And also, nothing has any problem at all, but foo() is from a proprietary 3rd party library…

Debugging.

And most info I can find online feels like elaborate propaganda. I mean there is just nothing against React to be found, really nothing.

It’s just Stockholm syndrome. Everybody that wants to criticize it is too traumatized to say anything, and everybody stuck with it makes a way to think it’s great.

Add to that the fact that it is great in theory, so nobody without direct experience can criticize, and you get only positive reactions.

AWS and Azure are services, not libraries; Elasticsearch is mostly open source; and DynamoDB, well, how many people use it again?

I’m not even sure this is a price increase. It probably is, but I think a lot of people will pay less.

They are just reserving the right to bankrupt you, at random, without any previous warning, because they want. There’s no good reasoning anywhere.

Oh, I don’t think anybody will disagree that Unity is completely unoptimized and barebones compared to Unreal. It is also hard to learn and confusing compared to Godot.

There used to be a huge amount of people that wanted exactly something easier to learn than Unreal and more featureful than Godot. But those two improved in a way that this niche may not even exist anymore. Anyway, currently Unity has that unbeatable marketplace, and I really don’t know if there’s a good enough replacement somewhere, but I don’t see any other reason to use it.

(But then, I’m not really a game developer. I’ve used those here or there, for fun.)

exponentially

Are logging the content of your log files?

A status page that acknowledges service failures?

Is this a new concept? I have never seen anything like it.

Hum… I fail to see any difference to regular C(++)^1.

In fact, I don’t see anything not possible with C(++)^0. Only the syntax changes.

250 MB internet messengers please

Hum… Make them some of those large-sized megabytes if it’s Teams.

It makes no sense at all to distribute the backup generation step, and what do you do with your ledger once the retention period ends?

There may be something you can do with a ledger in the “full - incremental - incremental - incremental …” cycle, but I can’t think of anything that’s actually useful.

So… Is the Basilisk Collection still not explained?

I would say that one should expect a high probability of comments on “Programmer Humor” being sarcastic. But deep down I know you are right.