It was enclosed in scare quotes, a sort of acknowledgment that the author knew it was non-standard, but was too apt for the purpose to resist. I remember reading it and trying to think of the “real” word that would be employed there, but could not find a satisfactory alternative. Since then, I’ve found myself unable to resist using the word when appropriate, due to its utility!

Poetry and children both have many interesting warpages and torsionings of language, all legal but serving to make the brain choke slightly, as the lungs do with a sudden whiff of ammonia or other unpleasant gas. 'Disprefer' is another good one!

On lackey, more or less following up on Mark Liberman's comment above: except in period references (where it refers to 'a footman, esp. a running footman; a valet' — OED2, citations from 1529), the word now comes with a sneer.

average level of "information", "surprise", or "uncertainty"

einwärts ge­wand­ter Spitze

Gänsefüßchen

Regex can do many things, but unbaking a cake isn't one of them.

I invite even the most cantankerous among you to review it.

Roughly speaking, a category may be thought of as a type theory shorn of its syntax.

The cars handling can be best explained as "its like steering a drunk sailor on a boat."

They likely won’t have any content, making them a sort of structural filler to spackle over the gaps in Grid’s capabilities.

Content is like water

Misleading vividness is a kind of hasty generalization that appeals to the senses.

Svelte’s aesthetics feel like a warm cozy blanket on the stormy web.

Making UIs with Svelte is a pleasure. Svelte’s aesthetics feel like a warm cozy blanket on the stormy web. This impacts everything — features, documentation, syntax, semantics, performance, framework internals, npm install size, the welcoming and helpful community attitude, and its collegial open development and RFCs — it all oozes good taste. Its API is tight, powerful, and good looking — I’d point to actions and stores to support this praise, but really, the whole is what feels so good. The aesthetics of underlying technologies have a way of leaking into the end user experience.

It is hard to appreciate how important really fast (and reliable) hot reload can be during development, unless you have experienced it yourself. Developers report that it changes the way they create their apps, describing it as being like painting their app to life.

Long ago, the standards deities gifted us <style scoped>, before removing it in favour of the arguably less-useful shadow DOM encapsulation mechanism.

In the real world — the time to pay off technical debt is scarce — in most of the time fueled by the fear of the unknown. The management loves to milk the cow but not to change the litter. The developers on another hand avoid modernizing legacy code — to avoid trouble in case anything breaks.

It’s ‘consent’ by the spotlit backdoor.