Bold idea: when you want to get computers to do something, use a programming language. NOT A YAML FILE. cloud.google.com/workflows/d…
26
91
19
402
Every "declarative" language eventually becomes a (terrible) programming language, just without the aid of actual language design. We learned this with XML 20y ago; it astounds me that people seem to think the lesson of that age was that we used the wrong shape brackets.
21
129
14
386
I don’t really see this for HTML or CSS
1
2
appart for the explosion of javascript?
1
1
2
How is that HTML or CSS?
1
1
js fill the prog game that html/css slow evolution let open regarding the need for programming on top of declarative lang
1
Replying to @fanf42 @BrianGoetz @pchiusano
Which makes them successful in being declarative. You’re not supposed to use them for everything. In fact, they’re rarely used beyond their original purpose, in contrast to JS :)

Sep 2, 2020 · 6:18 AM UTC

1
1
Replying to @stilkov @BrianGoetz @pchiusano
OK, but almost nobody use them "as they should", and so, even with a drastic limitation of their power in standards, people invented a bunch of extensions/workaround to add prog power on top of them, from "less" to js
1
I dispute that almost nobody uses them as they should. Anyway, the original point was that declarative languages inevitably grow into bad non-declarative ones, and I still maintain this isn’t true for HTML and CSS (even though I’ve often see it happen to home-grown languages)
1
more replies