misterbassman

I have no insight into why it's being done in this instance, but object storage is typically used when you want to move away from storing things on your web server with "fixed" storage, and instead store it in an "infinitely" expandable storage system. It is also much easier to manage when you have multiple servers as it's separate and shared.

Here is a post by the creator of Bruno explaining the differences: https://dev.to/helloanoop/launching-bruno-local-first-opensource-api-client-2ipc

One of the main issues with OSX is that docker sucks, it's so slow even using the new fixes virtfs etc.

It may be better than a 6, but it's terrible compared to a 5.

Is this based on an F1 car with slicks and an FE car on this standard "inters"? Because that hardly seems fair.

Also FE cars don't have active aero, was the F1 car using DRS?

Best bet is to check out the GitHub repo

That's exactly what is happening now. Lemmy is a very young codebase and up until very recently only had a tiny user base, so optimisation wasn't that important.

Over the last few months the Devs have been working hard to improve things, but there is a lot of ground to cover

Possibly not ideal for you as a data engineer, but you could try skimming down the GitHub database issues?

Sadly not, it's mostly focused on comment ordering.

All the tracking code is in the ads library which isn't loaded after paying to remove ads.

This caused major issues with Google before, so I don't think so.

Just pay to remove the ads then, this disables all of that