I use New Relic and I'm not sure I would recommend it. Sure it was easy to install on all the server but now I keep getting alerts every months (on like the 2nd day) that I ran out of some "quota" of 100GB. I thought that's impossible as I almost don't use it but apparently they (used to) send by default list of running processes every second and that gunks things up.

Also I setup alerts - for >50% CPU or >90% disk full. I do get an alert but it doesn't say which volume or how full is it - what was the actual value that triggered sending the alert. WTF.

> shoddy construction

Just today there was a newsletter from Construction Physics about Strap Rail. Literally wooden rails with a iron plate strapped on top put in the mud. Only in the US, 10 times cheaper. But more expensive to maintain and gone in years instead of decades for normal iron rails though.

Young ones can readily replace spinach

This is not clarified on the blog, and is an important point. The mature plant is not tender or tasty.

Not without grumbling though. Recently the cost reached 1 billion euro/year and it drove quite some discussion

But most of these variations were part of the spec (endianness with II or MM, later magic 43 for bigTIFF 64bit extension). I work with tiff and tiff-derived formats in digital microscopy where its very much not historical. And the alternatives (DICOM supp 145, vendor-specific garbage ... and thats it) are worse.

I quite like the format, the only thing I would change is to have the option not to store directory information in a linked list spread throughout the file but in a simple array. Duplicate it at the beginning and end of the file and you've got resilience too (important in the age of floppies)

May you please help me out financially then, friend? ;P Willing to work for it, too!

I cannot express in words how much I hate this mentality.

it's ridiculous only if you compare it with Apple RAM prices

Note that in the 90s EUV was about as mature as fusion that's to say not at all. Not many people believed it could be actually used to make CPUs

I'm a bit confused. The point of this article is that the author used .NET Interceptors and TagWith to somehow tag his EF Core operations so that they make their own busy_timeout (which EF Core devs think is not necessary https://github.com/dotnet/efcore/issues/28135 ) or do a horrible global lock? No data is presented on how it improved things if it did. Nor is it described which operations were tagged with what. The only interesting thing about it are the interceptors but that's somehow not discussed in HN's comments at all.

Sounds like it was a lot more serious for the water than for the worker

Indeed, writing this on a laptop with Linux that cant sleep and gets random crashes with blinking caps lock about once a week. Whether its Realtek ethernet adapter can run at its nominal 5gbps on a 6.14+ or <6.10 kernel without CPU soft lockups is an open question