6 ms·

>they're gonna be around for a long time how many months does that translate to in frontend dev time?

gherkinnn 6y ago
This meme is tedious. Typescript is here to stay. No question. React has been a thing now for what, six years? And it feels like 80% of FE job opening require React. And no major shift on the horizon.
- tilolebo 6y ago
  Six years, roughly the time it took Angular to rise until version 2. Sorry for the sarcasm, I've been trying to learn web development for some months, starting with the basics (HTML, CSS, plain JS) and slowly adding more modern frameworks (Bootstrap, NodeJS, ...). The course is a few years old already and it feels like 80% of what I learn is now completely irrelevant. I just wonder how frontend developers keep up with that pace. If I'd write a blog, I wouldn't want to spend half of my time into refactoring and migrating to newer versions, frameworks, etc. But maybe that's just me.
  - TeMPOraL 6y ago
    > I just wonder how frontend developers keep up with that pace. It's a full-time job. I have a cynical theory that this pace is beneficial to webdevs, because as long as they can keep convincing their employers and customers that they need bleeding edge frontend tech, they can enjoy their absurdly high salaries (as compared with the rest of the industry).
  - mcguire 6y ago
    "I just wonder how frontend developers keep up with that pace." Leapfrog. You learn the newest hotness right now (and hope you're right), evangelize it like a Southern Baptist at a tent revival, ride the wave for a few years until it's obvious the wheels are coming off in one of the three or four predictable ways, then pick up the new, new thing and pretend the past never happened. It helps to change jobs every nine months or so; otherwise, someone will ask you to do something to that ancient archaic legacy stuff. Nobody wants that.
  - jupp0r 6y ago
    "I just wonder how frontend developers keep up with that pace." Understand the principles behind these frameworks, see that they hit just some point between conflicting tradeoffs, understand problem domains and how they interact with these tradeoffs. It's not like jQuery is accomplishing something fundamentally different than React, it's just that they make wildly different design choices that have implications on composability, maintainability, etc. After you've learned a few of these (and the principles they are built on top of), you'll understand that it's going to be pretty easy to learn the next 10 of them.
  - jagannathtech 6y ago
    Are you taking colt Steele's web dev course on Udemy?
    - tilolebo 6y ago
      Ah ah yes, that's the one. Did you take it too?
      - jagannathtech 6y ago
        I have that but I'm currently doing the webdev course by Angela yu. Heard that colt steele has planned for an update.. no one knows when. As far as I can see the big difference is colt doesn't cover react.
- runawaybottle 6y ago
  When did you start web development? Serious question. We went through all the ‘here to stay’ a few times over already. Cordova, Bootstrap, Backbone, Coffeescript, Angular, Grunt, Gulp, Require.js/AMD, I think we already moved into and out of React Native lol, that whole Mongo thing, everyone had to be a D3 expert almost at one point, isomorphic apps almost became the thing - Meteor, they were all here to stay.
  - cableshaft 6y ago
    I think TypeScript is about as standard for Javascript as it's going to get, I feel. I can't imagine writing Javascript without it anymore. But then again it took TypeScript coming along that made writing JavaScript something tolerable outside of having to use it for work. I don't think there's going to be any new typing system that's 5% better that everyone is going to shift to just because it's the new hotness anymore. Or at least I hope not. TypeScript is good enough, let's just stick with it for the foreseeable future if you want to write type-safe Javascript, please. I'm still using Angular at work, and I rather like it. If I needed to make an SPA outside of work I'd probably use it over React at this point. But that's a web framework, and those seem to come and go with the wind.
    - runawaybottle 6y ago
      Well, if it’s that standard it could be put into the ES spec, and if that ever happens, Babel will deprecate Typescript. That’s all it would take before Typescript will become another relic. I am not opposed to Typescript, but I am trying to show that we’ve been here before many times.
    - purerandomness 6y ago
      Have you been around last time, when CoffeeScript definitely was here to stay? Or that other time, when Dart was almost here to stay, and on its way to replace JavaScript?
      - gherkinnn 6y ago
        Coffeescript was here to stay? I always saw it as a seki-esoteric language people sprinkled their CV with. Dart was a push by Google but went nowhere. TS drives Angular, has first-class support on React and soon in Vue. Most libs have TS typings. Nextjs (amongst others) provide easy TS integration. It’s being pushed by M$, C# and Java like seem to like it and Enterprise (tm) adopts it. It’s an entirely different beast.

This meme is tedious. Typescript is here to stay. No question. React has been a thing now for what, six years? And it feels like 80% of FE job opening require React. And no major shift on the horizon.

tilolebo 6y ago
Six years, roughly the time it took Angular to rise until version 2. Sorry for the sarcasm, I've been trying to learn web development for some months, starting with the basics (HTML, CSS, plain JS) and slowly adding more modern frameworks (Bootstrap, NodeJS, ...). The course is a few years old already and it feels like 80% of what I learn is now completely irrelevant. I just wonder how frontend developers keep up with that pace. If I'd write a blog, I wouldn't want to spend half of my time into refactoring and migrating to newer versions, frameworks, etc. But maybe that's just me.
- TeMPOraL 6y ago
  > I just wonder how frontend developers keep up with that pace. It's a full-time job. I have a cynical theory that this pace is beneficial to webdevs, because as long as they can keep convincing their employers and customers that they need bleeding edge frontend tech, they can enjoy their absurdly high salaries (as compared with the rest of the industry).
- mcguire 6y ago
  "I just wonder how frontend developers keep up with that pace." Leapfrog. You learn the newest hotness right now (and hope you're right), evangelize it like a Southern Baptist at a tent revival, ride the wave for a few years until it's obvious the wheels are coming off in one of the three or four predictable ways, then pick up the new, new thing and pretend the past never happened. It helps to change jobs every nine months or so; otherwise, someone will ask you to do something to that ancient archaic legacy stuff. Nobody wants that.
- jupp0r 6y ago
  "I just wonder how frontend developers keep up with that pace." Understand the principles behind these frameworks, see that they hit just some point between conflicting tradeoffs, understand problem domains and how they interact with these tradeoffs. It's not like jQuery is accomplishing something fundamentally different than React, it's just that they make wildly different design choices that have implications on composability, maintainability, etc. After you've learned a few of these (and the principles they are built on top of), you'll understand that it's going to be pretty easy to learn the next 10 of them.
- jagannathtech 6y ago
  Are you taking colt Steele's web dev course on Udemy?
  - tilolebo 6y ago
    Ah ah yes, that's the one. Did you take it too?
    - jagannathtech 6y ago
      I have that but I'm currently doing the webdev course by Angela yu. Heard that colt steele has planned for an update.. no one knows when. As far as I can see the big difference is colt doesn't cover react.
runawaybottle 6y ago
When did you start web development? Serious question. We went through all the ‘here to stay’ a few times over already. Cordova, Bootstrap, Backbone, Coffeescript, Angular, Grunt, Gulp, Require.js/AMD, I think we already moved into and out of React Native lol, that whole Mongo thing, everyone had to be a D3 expert almost at one point, isomorphic apps almost became the thing - Meteor, they were all here to stay.
- cableshaft 6y ago
  I think TypeScript is about as standard for Javascript as it's going to get, I feel. I can't imagine writing Javascript without it anymore. But then again it took TypeScript coming along that made writing JavaScript something tolerable outside of having to use it for work. I don't think there's going to be any new typing system that's 5% better that everyone is going to shift to just because it's the new hotness anymore. Or at least I hope not. TypeScript is good enough, let's just stick with it for the foreseeable future if you want to write type-safe Javascript, please. I'm still using Angular at work, and I rather like it. If I needed to make an SPA outside of work I'd probably use it over React at this point. But that's a web framework, and those seem to come and go with the wind.
  - runawaybottle 6y ago
    Well, if it’s that standard it could be put into the ES spec, and if that ever happens, Babel will deprecate Typescript. That’s all it would take before Typescript will become another relic. I am not opposed to Typescript, but I am trying to show that we’ve been here before many times.
  - purerandomness 6y ago
    Have you been around last time, when CoffeeScript definitely was here to stay? Or that other time, when Dart was almost here to stay, and on its way to replace JavaScript?
    - gherkinnn 6y ago
      Coffeescript was here to stay? I always saw it as a seki-esoteric language people sprinkled their CV with. Dart was a push by Google but went nowhere. TS drives Angular, has first-class support on React and soon in Vue. Most libs have TS typings. Nextjs (amongst others) provide easy TS integration. It’s being pushed by M$, C# and Java like seem to like it and Enterprise (tm) adopts it. It’s an entirely different beast.