The last time I remember seeing the same kind of behaviour was when document databases appeared on the scene. Content creators far and wide were writing about MongoDB vs Postgres, stories about rewriting an app to be "web scale", and whatnot. It grabbed reader attention because a lot of people were feeling unsatisfied with products like Postgres (this was before it added a lot of the features we expect today), MongoDB solved a problem for a niche set of users, and so the race was on to read everything they could to try and convince themselves that MongoDB would also solve the problems they have, even where their problems were not within the small area where document databases are appropriate.
The most likely reason for why people are drawn to want to read about Rust for much the same reason. Note again that they are spending their time wanting to read about it, which is different than using it. Rust solved a real problem for a niche set of users. Now everyone who has problems with their existing technology stacks are trying to read all they can to try and convince themselves that Rust will also solve their problems. The heart lusts after Rust on the promise that it will solve all problems, but the mind knows it won't solve all problems. Attention lies at the intersection of those competing interests.
Rust is a big deal, but that isn't a big deal. MongoDB was also a big deal. Look at where it is at now. The good news for would-be language designers is that there is a strong signal in the market begging for a solution to their problems. The only question is whether you can deliver before the incumbents catch up (see: modern Postgres).
Do you see any other examples of where technical excellence is attention grabbing? From my vantage point, when something does a great job at solving a problem better than everything else nobody spends their days trying to read about it, everyone quietly starts using it. It is undeniable that Rust gets mentioned a lot because any mention of Rust brings the clicks. It is a big deal in that sense. But something being used to compel readers into reading content suggests an emotional longing that isn't being satisfied by the technical reality.
What you do need is some kind of boundary mapping layer so that your application isn't tightly coupled to the database. That might be a an RRM instead, but if you are going to all the trouble of adding an RRM, why not an ORM? What's the difference, really?
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".
Equally obvious is that it doesn't matter what you do or don't understand. Nor does it matter if you find something to be rude. The comments, they are not written for anyone in particular. This is a public forum. Comments are there for all.
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.
Remember, CPI exists to attempt to figure out how the value of a currency has changed over time. It's not a cost of living index, a housing cost index, a wellness index, or anything of the sort. It is not trying to measure how you are doing in life. It is not there to determine the value of labour, the value of housing, the value of food, or the value of anything other than currency. It is simply compiled to determine the difference in value between $1 yesterday and $1 today, so to speak. As you can see, you cannot use the currency itself to provide that measurement. $1 and $1 are visibly the same; except we know that $1 and $1 aren't the same over time. That is where CPI steps in.
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.
It is unclear what you mean. It is true that most software jobs were not writing iPhone apps, if that is what you are trying to say, but those were good jobs. Those who didn't have good jobs for a moment were quickly scooped up by investors trying to create the next big app. It was a feeding frenzy out there for tech workers, despite much of the rest of the economy faltering (agriculture also did very well during the GFC, to be fair).
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.
Huh? Housing becoming significantly more valuable than in the past[1] does not imply that wages have dropped.
[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.
The GFC wasn't good? It wasn't good for the general economy, sure, but given the specific industry we are talking about that was one of the best times ever. Money was being printed hand over fist building software that did nothing more than emit a fart sound. The opportunities for us with the 'picks and shovels' were endless with everyone trying to strike gold at the App Store gold mine.
The results of them actually talking to businesses and asking questions that are more than "did you have a job ad posted?" You are hardly the first person to imagine that job ads aren't representative of actual job opportunities. Obviously they are going to put in effort to avoid those weak signals.
Workers taking on new/different roles isn't the same as being replaced. Workers have been taking on new/different roles since at least the advent of agriculture, so that's nothing new. Being replaced would be something new, but the data doesn't support it.
BLS doesn't look at job ads when compiling "job opening" data. Their method isn't perfect (nothing in life is), but far more comprehensive than you give it credit for.
> Whenever you change the structure within that blob, your type checker won't flag that the receiver hasn't been updated to handle it.
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.
The most likely reason for why people are drawn to want to read about Rust for much the same reason. Note again that they are spending their time wanting to read about it, which is different than using it. Rust solved a real problem for a niche set of users. Now everyone who has problems with their existing technology stacks are trying to read all they can to try and convince themselves that Rust will also solve their problems. The heart lusts after Rust on the promise that it will solve all problems, but the mind knows it won't solve all problems. Attention lies at the intersection of those competing interests.
Rust is a big deal, but that isn't a big deal. MongoDB was also a big deal. Look at where it is at now. The good news for would-be language designers is that there is a strong signal in the market begging for a solution to their problems. The only question is whether you can deliver before the incumbents catch up (see: modern Postgres).