They did it with whips, Rimmer. Massive, massive whips.

This is the correct answer. Pig-headed arrogance is why this cancer of a framework exists.

Got a link?

I was unprepared for this and now I need to clean the carpet.

PSA: My Starbook MK V has great specs but feels cheap and loses charge when closed, so it’s always empty when I need it.

(Tried all firmware updates and different distros, without success and their support isn’t of any help either. Won’t be ordering from them again.)

Totally agree. It’s not the fault of Firefox at all. This is just being trigger-happy on new standards before they are ready and unwillingness to fix a problem in a different way.

If you weren’t so right it wouldn’t be so sad.

His joking?

Am I the only one who finds the title abrasive? Why “rules”? Who are you and why should I listen to you? Will you send the tutorial police around if I ignore you? Maybe “recommendations” would be a better choice?

I am very, very surprised about the competence of the commenters here. I have had many discussions on reddit about the advantages of meaningful instead of presentational class-naming and you’re normally met with great resistance, especially with users of frameworks like Bootstrap and Tailwind.

Here, everyone seems to either ‘get it’ or is willing to hear why classes like .lime are bad. Very cool.

I know! What a mistake of a framework. Glad my colleagues drummed it out of me.

Exactly this. Bootstrap killed the css star.

public function getSecretTrackingCode() { return $this->wifiManager->getNearbySsidsSortedByStrength()->__toString(); }