Gregory's ServerI end up having to apologize for implementing things in ~10 lines of non-React-ish highly performant code, simply because it's not implemented the bloated way React wants me to. And like, I understand why, when you are using a framework, it makes sense to buy in to the framework's way of doing things. But also....... sometimes vanilla JS and the DOM is the actual best way to make stuff happen
 4 comments | Expand all CWs
@jonbro Been thinking about this since you posted it. In our coding guidelines at work our literal first principle is "Clarity, not cleverness", which I love. I think bit twiddling in C# is clever but not clear. I think using the DOM API and vanilla JS vs React's way of doing things is often clear and sort of the non-clever way of doing things. Like my complaint about React is that it's overly clever, like you are always bit twiddling @darius, not just React. I remember the bad ol' days when frameworks/libraries/versions of jQuery saved one the effort of managing a bunch of shims and workarounds etc. But around a year or so after ES6, yeah, they often add a lot of bloat to both the dev and end-user experience. |
@darius whenever my coworker does some unsafe bit twiddling in c# it makes me feel uncomfortable, even though it generally far easier to understand than the surrounding code.