4 ms·

Bottom line: consider jQuery before any fancy hot XXX.js framework

• keithwhor 11y ago
  Consider vanilla JS before jQuery. ;) Frameworks are useful abstractions for getting a product shipped in a reasonable timeframe. At some point, in your growth as a developer, you should understand how to implement things in your language of choice from first principles. However, "ship it" is not necessarily a conducive mantra to learning the intricacies of a language, design patterns, et cetera. On top of that, it's really damn hard to find good engineers who can work from first principles that aren't already in highly-paid, competitive positions. This is why frameworks flourish. They substantially lower the barrier to entry for creating product.
  • slippyt 11y ago
    > They substantially lower the barrier to entry for creating product. It goes further than this: a good framework can lower the barrier to writing maintainable, modular code. Sometimes people just need a nudge to follow good practices.
    • keithwhor 11y ago
      Yeah, but this can be a crapshoot. ;) Many JS frameworks enforce their own brand of modularity (complete with boilerplate) that isn't transferrable to other projects, frameworks or languages. They don't necessarily teach you how to write modular code in general, just how to write modules within their architecture. There's a difference. Edit: Not to say there isn't value in introducing a newbie developer to modules. Just not all frameworks are created equal. :)
      • hughw 11y ago
        e.g. Angular