9rx

But you could. There is no law of the universe that is going to stop you. Words are something randomly made up by humans.

> it's just plain wrong.

Again, words are completely made up, so it can't really be wrong in the traditional mathematical sense. It could be misinterpreted, perhaps. Of course that is dependent on how you've chosen to randomly make up "wrong".

All good things must come to an end, I suppose.

There isn't someone at a keyboard typing content. It's still just search, repeating quotes from other websites. The difference is that the algorithms have turned lossy, so the quotes are not always preserved in their original form.

If you want to understand something else, use the measures and data that are focused on that something else. Right tool for the job and all that.

Maybe you are trying to say that there was some grey beard Atari programmer out there who refused to start writing iPhone apps and couldn't find their dream job banging bits on the old 2600? That is likely, but it is equally likely that they never found that job since either.

[1] Mostly thanks to computers/software making housing a more compelling proposition. Historically, people couldn't wait to get outside or over to the pub and would allocate their spending to support that, but now that they prefer to stay in to look at screens, they deem that place where they spend time worthy of greater spending instead.

And the link echoes that there is a job crisis. But not an AI job crisis; rather a COVID frenzy fallout job crisis.

The relevant type is "blob". There is no further structure. If the function that accepts void* is trying to extract structure out of the blob, there is a bug in that function and the type checker should already catch you trying to extract structure from something that isn't there.

> I mean WHY are you making an API that takes such a pointer to an unknown type to begin with?

It's not unknown in any meaningful sense. It is known to be a sequence of 'arbitray' datums of a given length, which is the exact type of input required for the scenario given.

As the article explores, some argue that you should define that sequence with a concrete type, but the article states that it doesn't offer any additional value as is posits that void* already communicates the same. In other words, it suggests that void* is the concrete type for that type already.

Yup. Most everything we need was already built in the 1970s. Programmers have been kept busy because we've kept introducing incompatibilities into the mix, like DOS programs needing to be rewritten for Windows, and then the web, and then mobile.

And now they're being rewritten for AI platforms. It may be giving the squeeze due to being the first platform that will also help with the rewrite effort, but it is also the thing that kept the industry going. As you point out, there wasn't any work left to do until AI showed up.

But it is a term that definitely exists. We can find it used often in the literature. Hell, we can find one of those instances in your very own comment... How on earth did you reach the conclusion that it doesn't exist? You didn't give that one any thought at all, did you?

The relational model is superior as complexity grows (although arguably the deductive model is even better), but the tablational model is superior for simple line-of-business stuff, so pick your poison. Like with all things engineering, there is never one perfect solution that satisfies everything. If, like the earlier comment suggested, you keep your SQL simple then you'll be fine.

While it is true that words often have multiple meanings while remaining meaningful, they do not have multiple meanings within the same context as is the case here. I am surprised that wasn't obvious to you. Hey, on the bright side, at least you got to learn something new today.

Exactly. Terms that are meaningful have one generally accepted definition. When everyone and their brother are coming up with their own pet definitions, that is when a term is considered meaningless.