4 ms·

It's a little funny that Javascript haters and Javascript influencers meet in their desire to highlight the new and shiny toys of the front-end ecosystem, but i

It's a little funny that Javascript haters and Javascript influencers meet in their desire to highlight the new and shiny toys of the front-end ecosystem, but if you actually look at the survey results (or work on the front-end) then you know that in the real world, where people are shipping to prod, the story is the stability of favored tools. These things won: React, Webpack, Jest. They've been the dominant tools for years. (Typescript is getting there.) The ecosystem around them is enormous; a million edge cases have already been handled; they're not going anywhere for a long time. It's not really a surprise that as browsers become more like operating systems, people will experiment and find new ways to leverage the available capabilities, but you don't have to play with the new toys, and you definitely don't have to use them for paying work. Just say "risk" ten times if anyone suggests them, and your PM will end up agreeing with you.

whatshisface 4y ago
>The ecosystem around them is enormous; a million edge cases have already been handled; they're not going anywhere for a long time. Sounds like everything that came before them, but they got a foothold somehow. >Just say "risk" ten times if anyone suggests them, and your PM will end up agreeing with you. Please don't overuse this, if you get in your groove then ten years down the line you'll end up being a naysayer to something the company actually should adopt.
- 0xblinq 4y ago
  Yeah, like one of the companies I briefly worked for. An outdated hell of WordPress, with no package.json, no linters, no formatters, copy & pasted / vendored dependencies, lot of NIH home built libraries, no tests, no framework other than jQuery, no automation (we built scss from the CLI because "we don't need to complicate it with scripts", and absolute negationism about any "shiny new tool" if it was less than 20 years old. The only people that stayed there were the ones happy to work in those conditions, or that haven't seen anything better. Those places still exist, sadly.
  - nullfish 4y ago
    Did the company make money? That's the reality of it. You don't need shiny frameworks or any of those tools to make money. Are developers happy with it? Maybe! Nothing wrong with spicing up a site with a little jQuery. Heck, I used Alpine.js on a brand new site and it's great. No build step, just works!

whatshisface 4y ago

>The ecosystem around them is enormous; a million edge cases have already been handled; they're not going anywhere for a long time. Sounds like everything that came before them, but they got a foothold somehow. >Just say "risk" ten times if anyone suggests them, and your PM will end up agreeing with you. Please don't overuse this, if you get in your groove then ten years down the line you'll end up being a naysayer to something the company actually should adopt.

0xblinq 4y ago
Yeah, like one of the companies I briefly worked for. An outdated hell of WordPress, with no package.json, no linters, no formatters, copy & pasted / vendored dependencies, lot of NIH home built libraries, no tests, no framework other than jQuery, no automation (we built scss from the CLI because "we don't need to complicate it with scripts", and absolute negationism about any "shiny new tool" if it was less than 20 years old. The only people that stayed there were the ones happy to work in those conditions, or that haven't seen anything better. Those places still exist, sadly.
- nullfish 4y ago
  Did the company make money? That's the reality of it. You don't need shiny frameworks or any of those tools to make money. Are developers happy with it? Maybe! Nothing wrong with spicing up a site with a little jQuery. Heck, I used Alpine.js on a brand new site and it's great. No build step, just works!