I don’t view this ratio as a better/worse thing. Config as code it a good practice already, and once you have that, it’s moving complexity, not creating it.https://twitter.com/springrod/status/1002379190174302208 …
I'm in this camp. I see both sides. To me, there is a big benefit to JS everywhere. By turning JS into a declarative plan can't we get the best of both worlds?
-
-
I don't think so. The JS is what gets checked in to source control, and thus you lose the easy inspectability and language independence
-
It feels a bit like the way Docker/k8s has broad appeal because it takes an existing skill set and upgrades it. There's a better approach out there that provides better and higher abstractions (serverless, declarative cfg), but requires a shift in thinking + new skills
-
One of my arguments is that docker/k8s changes too little for developers
-
That's how I feel about imperative configuration. I'm not big on "developers need CS degrees", but an understanding of the benefits declarative programming provides, and a willingness to learn such languages, is one thing I think we should aim for people to have
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.