tjoekbezoer

Just trying to be helpful by making an adequately coined term more palatable to a critical audience, thereby expediting the end of a fruitless discussion on an otherwise excellent article. Compliments.

Regarding the critique on the title: perhaps an analogy can be made to propeller cavitation on ships. Water influx rate, propeller design and operational parameters all influence the detrimental effect of water bubbles forming — deteriorating the system's efficiency.

The GPU would be the propeller, the influx is the work, and the operational parameters is what this article's about.

Well, above the fold in the chapter 'What is PlanetScale for Postgres?' the second paragraph mentions custom operator. That makes me assume it is kubernetes.

When jq came out about a decade ago I fell victim to a nerdsnipe and decided to try and mimic its syntax by building a parser in javascript: https://github.com/tjoekbezoer/jsq. Never completely finished it, nor used in a professional context but I learned a fair bit and it works quite well.

It's old code — still using google's java-based compiler — so be gentle please :)

There's also a live editor to try it out: http://tjoekbezoer.github.io/jsq/parser.html

I'd say a good start would be:

* Stacking context [1] — how individual layers interact with eachother to form a layout.

* Box model [2] — the most important properties that give an individual element its dimensions.

[1]: https://tiffanybbrown.com/2015/09/css-stacking-contexts-wtf/

[2]: https://css-tricks.com/the-css-box-model/

Judging from the source code, it appears to be a webflow site — https://www.webflow.com