> I took action as the primary on-call engineer to lock down the AWS account and prevent any actions by possible attackers.
So he suspected an attack, but did not contact his employer about it or other team members. No action taken to mitigate the attack or to identify what was going on. Just changed the AWS root account password and nothing else.
Even assuming the very best intentions, I don’t think it unreasonable that Ruby Central found that a little bit suspicious.
Maybe I’m just not the target audience, but looking at the front page, I don’t see what actual problems this solves. The claims sound nice, but without examples of what they mean in real world use, it’s not really compelling.
This exceedingly uninformed rant makes more sense when you understand that the author has his own timestamp format he wants to push.
Counterpoints:
- UUID is not random characters, it's a 128 bit number and is stored as such in many databases. It can be presented as a hex-string with dash-separators, but it doesn't have to be.
- There are several types of UUIDs. UUIDv4 is mostly just random bits. Others have time and machine numbering, like Snowflake IDs. UUIDv7 has a combination of time and randomness.
- UUIDv7 was made to address the database index problem, rendering that point moot.
Lots of tools understand and/or support UUIDs.
You can complain about the overhead of storing and indexing 128 bit numbers if you want, but realize that a string like 2025_P5U5_326662 is likely also going to be stored as 128 bits. And the added value of having the year in front (the rest is not going to mean anything to the average user) is not that great.
Will be interesting to see if they can make it stick. Everyone is used to Windows + Office, so there’ll be a lot of resistance to trying something else, and if their IT department is not ready for it, it can quickly become a shit-show.
Everyone likes their mother tongue better, so does Mark Twain. No need to write a whole treatise about it.
Having lived 10+ years in Switzerland and having learned the language (and the local dialects), I really like German. But like many delicacies, it is an acquired taste.
One might hope it’ll cause Tesla to drop the price for their “full” self-driving too. $8'000 for a software feature is just bonkers. Especially in Europe, where there’s no subscription option, so you can’t even try it without paying the full price first, and many of the fancier features are not supported here. Even regular auto-pilot is not very reliable for me, it often fails to recognize city limits signs, and fairly often panic brakes because it misinterprets cars driving on the other side of the road as being on collision course.
You can say that, but on the power flow maps, it was quite clear. At the same time we were paying ~$1.5 USD for 1 kWh, we were exporting power to Germany (and other energy-unstable countries like Italy). Sure, better energy links inside Sweden could have helped, but part of the reason the price was being bid up so high was the exports to Germany.
Hello world might be simple, but you don’t have to build very much before you start to run into problems with the simple “props down, events up” and you start needing to learn about contexts, hooks in general and so on.
Hooks is really one of those things where you need an IDE to tell you that you’re doing it wrong, since there’s a whole bunch of footguns. It’s doing its best to solve a hard problem inside the limitations of JavaScript, but it is essentially a kludge.