You jest, but it took forever to add somewhat intuitive layout mechanism to css which allowed you to do what could be done easily with html tables. Vertically centering a div inside another was really hard, and very few people understood the techniques you would use, instead of blindly copying them.
It was beyond irony that the recommended solution was to tell the browser to render your divs as a table.
But price elasticity isn't infinite. A large part of the middle class would be priced out of most modern amenities if these would be produced domestically. Import substitution is one of these things that sounds nice in theory but tend to be highly damaging in practice.
It’s your job to tell them if the requirements cannot be met and that something’s gotta give. It’s his job to decide what, and it looks like he’s choosing latency When push comes to shove.
In these situations, malicious and over the top affirmation is the safest and most effective form of critique. See Laibach and NSK on how it’s done. Woke hyperliberalism With all it’s terrible contradiction should be an easier target than The authoritarian Socialism of the 80s.
GET must be safe and idempodent. In the context of http, idempodency basically means that you get the same result for each request with the same url and the same set of parameters.
Toggle should be implemented as post, since it’s neither safe, nor idempodent.
“Toggle” is by definition not idempodent, because you get a different result each and every time. “Open” and “close” are idempodent, but not safe. The result of a GET request should always be idempodent and safe.