2 ms·
> I haven't seen much code that uses the bad aspects of JS > The language may encourage it, but given that none of the JS libs I've used mutate anything I give
by sheepmullet 9y ago
> I haven't seen much code that uses the bad aspects of JS
> The language may encourage it, but given that none of the JS libs I've used mutate anything I give them
> If I need to make changes while keeping state instead of reloading (which I haven't really seen a need for)
Speaking as an enterprise JS dev the kind of apps you are working on sound nothing like the kind of apps I work on.
I work with a lot of poorly written JS code, a lot of mutable state, and pages with lots of complex state setup.
In fact the state setup is typically so bad developers rely upon unit tests and only check the UI on feature complete.
- _sdegutis 9y agoSorry to hear that. And that kind of code damage sounds pretty typical from most projects I've seen in open source and heard about through people I've talked to, no matter what language these projects use. It must just be that we all learn the hard way and usually during work hours what works and what doesn't. In cases like this, Clojure can help somewhat by its saner defaults, but I've seen some really terrible Clojure code too, that has many of the same problems.