Wouldn't it be better when all those big CDNs just switch off IPv4 and force the sleeping ISPs to enable IPv6? Maybe we should introduce some IPv6 only days as a first step...
Do I understand that correctly? When I have to create a spreadsheet like this, there are 2 options. Option 1 I write a table zipcode to state and use this table to generate my column. If I carefully check my table my spreadsheet would be okay. Option 2 I ask GPT3 to do my work. But I have to check the whole spreadsheet for errors.
About 2 years ago I believed the same. Then I used BTRFS as a store for VM images (with periodoc snapshot) and performance went down to really really bad. After I deleted all snapshots performance was good again. There is a big performance penalty in btrfs with more than about 100 snapshots.
I don't think this makes it any better. Imho "any changes you make will be lost" would mean to move the files back to where they were before and not delete them.
All true until it comes to outlook.com and your sent mail just vanishes without any error. It just accepts the mail but doesn't deliver. Not in Inbox, not in Junk.
RANK is a good example of a useful less known window function. Please also consider dense_rank and row_number. All 3 have their advantages and disadvantages... (Rank leaves holes after rows with the same order, dense_rank gives consecutive numbers, row_number just numbers the rows.)
We use the old REST a lot and call that what you name "new REST" Json-RPC. What's so difficult about naming things what they are? I mean Devs do have some brain. That's why we are able to write cool software. But then why are some of us too stupid to get that REST thing right?
Here in Switzerland healthcare is pretty much broken when it comes to prices. Everything is pretty expensive. But is it broken like in the US? No way! Our healthcare works very well and its prices are okay ;-)
I think it's much easier to begin with x86. Especially when the assembled code is being run the way it is on this website. x64 is a little harder because just the switch to x64 mode alone almost fills the boot sector.
Synology is a bad example. Many of their custom syscalls are related to filesystem things like btrfs raid5 self repair and carefully removed from their gpl source code. Ianal but imho this is a gpl violation.
Cloudflare, the solution for no problem... I don't believe in DDOS without any proof. Imo they just have some performance problems to solve. I think the DDOS would magically stop after Database Maintenance on Jan 25.
That's the problem with btrfs. Raid5/6 still isn't production ready and loses data with cheap consumer ssd which could to disappear/reappear in a running system. On the other side raidz/z2 works rock solid. Of course I could use btrfs with mirrors instead but that's the reason why I use cheap consumer ssds. I can't spend that much money just to use btrfs so I stay with zfs.