Is that what really happens though? EU countries usually don't immediately punish violations unless they're particularly egregious. You're more likely to get a warning and a grace period to meet the requirements. So the rational approach would be to not bother with consent banners, GDPR and whatnot until you attract the attention of the regulators, at which point you should definitely hire a legal team that can tell you what exactly you need to do to comply.

Urban Dictionary might be a better place for recent internet slang: https://www.urbandictionary.com/define.php?term=Cracked

I'm not the person you're replying to, but here's my take: even though the two look conceptually similar, Unix programs are just a lot simpler. All programs run on the same machine, they read their input, execute, produce output which is piped to the next program, and terminate. Want to change something? Change one of the programs (or your command line), run the command again, that's it.

Microservices are a lot more complicated. You'll need to manage images for each of the services, a fleet of servers on which the services will be deployed, an API for services to communicate together, etc. In many (most?) cases, a monolith architecture will be a lot simpler and work just fine. Once you reach the scale at which you'd actually benefit from a microservice architecture (most companies won't ever reach this scale), you can start hiring devops and other specialists to deal with the additional complexity.

What actually gets hate, I think, is not microservices themselves, but the fact that microservices are often used in contexts where they are completely unnecessary, purely because of big tech cargo culting.

This was a very enjoyable read. Thanks for sharing.

Very cool and fun project! Thanks for sharing.