That makes sense to me… You really only want one path for the air flow. E g. In through the front, over the components, and out the back.

Most of the fans in this setup are just fighting against each other.

My sister is a civil engineer in PA and is familiar with this situation. She told me that basically these municipalities did not take care of their pipes, refused to raise any money for them, then, when they got old enough that the situation became critical, sold it off. Now this company comes along, has to make required fixes to the pipes, and has to raise the money to do so. The private company gets to be the bad guy, while the local governments, who neglected the pipes for a decade or more, don’t get heat.

All this said, if they weren’t allowed to sell it to a private company, there would be no “get out of jail free” card and maybe they would have pushed harder to take care of them damn pipes.

Point is, I don’t think it’s quite as simple as it looks on the surface.

Great reads! Thanks for posting.

I think it would be neat if, as something gained popularity, more and more of it were re-written in optimized assembly. I mainly work in .NET, which performs fine for what it is, but there are some libraries like Dapper (which is a micro-ORM) which are written in IL, which is incredibly difficult to do but results in it being insanely fast compared to what you could do in purely managed .NET. I’m sure if it were written in assembly it would be an order of magnitude faster than that.

I would love it if every website change on Twitter/X didn’t result in endless “news articles”. I need to find a way to block this crap. I literally don’t care. Stop using X if you don’t like it. Done. Stop talking about it. This is worse than celebrity gossip.

That could be avoided by using on prem properly, too. People are very capable of making bad infrastructure whether on prem or cloud.