For any job-hunters, it's important you forget this during interviews.
In the past I've made the mistake of trying to convey this in system design interviews.
Some hypothetical startup app
> Interviewer: "Well what about backpressure?"
>"That's not really worth considering for this amount of QPS"
> Interviewer: "Why wouldn't you use a queue here instead of a cron job?"
> "I don't think it's necessary for what this app is, but here's the tradeoffs."
> Interviewer: "How would you choose between sql and nosql db?"
> "Doesn't matter much. Whatever the team has most expertise in"
These are not the answers they're looking for. You want to fill the whiteboard with boxes and arrows until it looks like you've got Kubernetes managing your Kubernetes.
Think it as a bit like GDPR but 1) much more expensive 2) with criminal liability 3) Makes even less sense than GDPR as it does nothing to prevent harm for minors 4) derimental for user experience and users.
"Funnily enough" the companies who lobbied for Online Safety Act, and former Ofcom employees, are now selling age verification check services and compliance services related to Online Safety Act. They have pretty good profit margins there, making even Google and Facebook look poor.
More here:
Original comment follows: They blocked irish.session.nz: "Resources for learning Irish music by ear". This is either a mistake or a very early example of a political abuse of the OSA. Both are wrong of course and prove what a stupid and concerning thing OSA truly is.
isn't this the opposite? Enabling compression will INCREASE the load on your server as you need more CPU to compress/decompress the data.