Cheng Lou - On the Spectrum of Abstraction at react-europe 2016

This talk is incredible food for thought: On the spectrum of abstraction by Cheng Lou (react-europe 2016) 1 If you've read some of the classics, such as Structure and Interpretation of Computer Programs (1979, Gerald Jay Sussman and Hal Abelson) 2, this talk is a really interesting look at the state of affairs on abstraction circa 2016. 1: link to this video 2: link

For a more visual explanation of the "cost of abstractions" watch this presentation by Cheng Lou (Facebook). link to this video

The spectrum of abstraction: link to this video This is an high level talk. it guides on how to choose between competing solutions to a problem when the commonly accepted answer is "it depends"

React is more like 'Lambda the Ultimate Web Component'. A component is almost a function returns element. Expanding a component is like calling a function and give it the property. So you can have some abstract common behavior in HOC f and g, then you can have HOC `h = compose(f(g))`. A quick comparison with Angular: @Component({template, style}) seems composable if we stretch a lot. But why make template and style in the decorator... They are not something we consider most abstract at all. The function is the simplest yet composable abstraction over the template, Cheng Lou also has a really excellent talk on the topic: link to this video

I know, this isn't a novel concept. There was a good talk about the spectrum of abstractions and the tradeoffs of template languages vs React's approach at React Europe a couple of years ago (in fact, he goes into that this means there are some optimizations that are simply unavailable to React): link to this video The question isn't whether DSLs or "just JS" are more powerful, the question is which tradeoffs they represent and which tradeoffs you prefer. It seems that HTMX is primarily based in the Python ecosystem and as a former Pythonista I see the advantage of having a DSL over having to write JS, especially that the former is much narrower, which is what you want in this situation.

Personally if you're able to easily manage your resources using plain manifests I don't think using Terraform is a good move. Like you're saying - abstractions inherently make things murky; it's a tradeoff you make for power but that tradeoff needs to be worthwhile (and kubernetes by itself is already great at making simple systems opaque!) However, if you're reaching for tools like Helm or Kustomize, I think Terraform is a great alternative - especially if your cluster interacts with external resources that Terraform can also manage (e.g. in AWS, an RDS instance or maybe yanking secrets out of KMS). A specific usecase that Terraform was useful for at my last job (note - we had a pretty…

Interesting that you should mention it. This talk link to this video mentions some arguments why a DSL would not be a good approach for frontend/JS build tools. Namely that a DSL isn't adequate if the underlying best practices or requirements change a lot. That's why operating at a higher level of abstraction (function chaining/piping/composition) would make more sense. Now... that doesn't really favor Webpack. And I still don't quite understand why that tool is so popular.