Thing is I agree we should make it easier for others to understand.... and for me, declarative -- or more specifically how people use it -- isn't it!

More code is harder to maintain. More code is more likely to break. More code is harder to understand.

But more than that, spreading things out in a spaghetti code manner -- the core concept it seems of declarative programming -- is the polar opposite of making good code that other people can follow.

It is quite literally encouraging spaghetti code!

Also I'm writing up a benchmark about .map vs. operating in place and... I may have underestimated how bad .map is...

The performance differences are also noticeable because if everything you write takes ten times longer to execute, you're harming FCP, FMP,. and other issues of load / interaction time... at least if writing client-side scripting.

But that's JS in general client-side, people obsession over making sure their code is minified, that they're leveraging CDN's, when most of the time they're just using two to ten times the code needed that takes two to twenty times longer to run, then can't figure out why it's slow. See such mind-numbingly asshat rubbish as front-end frameworks.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store