rockerest’s avatarrockerest’s Twitter Archive—№ 16,588

          1. A small collection of my takes: - you NEVER need Flux-style state management. Period. - every "modern" framework has been obsolete since late 2018 and arguably around 2015 - related: if you're choosing a VDOM or a compiler in 2021 you're half a decade behind the state of the art
        1. …in reply to @rockerest
          - every web app needs: message bus, Web Components, FSM. You can get 80% of the way with nothing else. - 10kb of good HTML and CSS would PROBABLY be better than a huge chunk of your JS app - understanding regular expressions is required for any dev
      1. …in reply to @rockerest
        - REST is terrible, GraphQL is too complicated. We haven't gotten there yet, but something like GQL-over-sockets is more likely the future. - VC is bad. There's nothing else to this point. - exceptional products do less, not more
    1. …in reply to @rockerest
      - Unit tests are purely developers self-pleasuring. - TDD is an actual cult. - Strong types are completely unnecessary if you are able to write defensive software
  1. …in reply to @rockerest
    - virtually every single common whitespace "best practice" is wrong: eyes should be drawn AWAY from the language keywords and syntax, not to it. - functions & methods should have a single exit; not zero, not more than one - Classes in JS were a mistake from their conception
    1. …in reply to @rockerest
      - identifying - and then understanding - patterns is literally the most foundational skill to software development, and it seems like maybe a huge percentage of developers don't have it. - == in JS is completely safe
      1. …in reply to @rockerest
        - using the const keyword in JS is almost always objectively incorrect, despite how your feels feel about it - JS should focus on reactive & functional programming tools like the pipeline operator and Observables