5 ms·

To their credit, the not so junior developers are constantly telling them that they HAVE to learn React. Pick any Javascript forum on the internet, even HN com

To their credit, the not so junior developers are constantly telling them that they HAVE to learn React. Pick any Javascript forum on the internet, even HN comments, if you'd like. The common comment is "Just use React".

egeozcan 10y ago
Not to mention the influx of medium posts telling them if they specialize on one single framework, they can get a job after a few months of training. The interesting thing is they are not lying: You'll get a job which will last until the new library de jour arrives. Maybe this is how the job market answers the high demand. I personally have no idea.
- 6DM 10y ago
  I mean, they'll at least have the job until the project is finished. You're boss probably won't care if another framework comes out. Then there's all of the legacy applications that will need support. There's an entire market for that. In the meantime you can learn something new :)
  - at-fates-hands 10y ago
    >> There's an entire market for that. I can confirm this. I work in a large corporate environment and we're rebuilding a legacy application in Angular 1.4. They have no plans of migrating and even talk of moving to 1.5 or even 2.0 I've been told migrating to either 2-3 years away.
  - wwweston 10y ago
    >> In the meantime you can learn something new :) The problem I've come to have with this as I get older is... I realize that I have a limited amount of time to learn new things. I still love doing it, but if possible, I'd rather spend that effort on learning portable, enduring, and broadly applicable things than ephemeral arcana involved in learning to do essentially the same thing a different/"modern" way. New learning should be for new capabilities, a better quality of insight, and real advantages.
    - 6DM 10y ago
      Oh yeah, I definitely get that. My main point is there's no reason to be outright afraid when a new framework arrives. I would argue there's even time to let it mature and see if it's actually worth learning.
virmundi 10y ago
I had a conversation with my wife, who's training to do front end development, just this morning. Our product is going to have Javascript. It's going to have JQuery. After that, probably not too much. I explained to her the difference between an app and a web site (we're making a web site). There is only one app-like section. Even that is vanilla JS. All that said, I told her to pay attention in the Udacity backbone class. General framework knowledge should let her generalize using JS.
- troncheadle 10y ago
  > I explained to her the difference between an app and a web site (we're making a web site) What did you say here? I've been thinking a lot about this lately -- In my opinion, a websites are a part of an 'app': the client.
  - Spivak 10y ago
    For me the distinction is what the JS is used for. * If you use FE JS to implement any of your sites functionality then you have an app. * If you only use FE JS for just presentation logic then you have a website.
  - virmundi 10y ago
    I used an example. An app, that she's familiar with, is Gmail. I said our product is not a desktop application, like Outlook, but for the web. What we're going to do is mostly display static content, refresh the screen on navigation circa 2002, etc. So there are some parts where we need dynamicity, like our menu builder, but for the most part we don't need anything complex. As a result JQuery is fine.
  - pault 10y ago
    When I have to explain my job to non-technical people I usually say I build apps "like gmail" not websites "like blogs and company websites"
galfarragem 10y ago
> The common comment is "Just use React". Or Vue.
deleted 10y ago
[deleted]

egeozcan 10y ago

Not to mention the influx of medium posts telling them if they specialize on one single framework, they can get a job after a few months of training. The interesting thing is they are not lying: You'll get a job which will last until the new library de jour arrives. Maybe this is how the job market answers the high demand. I personally have no idea.

6DM 10y ago
I mean, they'll at least have the job until the project is finished. You're boss probably won't care if another framework comes out. Then there's all of the legacy applications that will need support. There's an entire market for that. In the meantime you can learn something new :)
- at-fates-hands 10y ago
  >> There's an entire market for that. I can confirm this. I work in a large corporate environment and we're rebuilding a legacy application in Angular 1.4. They have no plans of migrating and even talk of moving to 1.5 or even 2.0 I've been told migrating to either 2-3 years away.
- wwweston 10y ago
  >> In the meantime you can learn something new :) The problem I've come to have with this as I get older is... I realize that I have a limited amount of time to learn new things. I still love doing it, but if possible, I'd rather spend that effort on learning portable, enduring, and broadly applicable things than ephemeral arcana involved in learning to do essentially the same thing a different/"modern" way. New learning should be for new capabilities, a better quality of insight, and real advantages.
  - 6DM 10y ago
    Oh yeah, I definitely get that. My main point is there's no reason to be outright afraid when a new framework arrives. I would argue there's even time to let it mature and see if it's actually worth learning.

virmundi 10y ago

I had a conversation with my wife, who's training to do front end development, just this morning. Our product is going to have Javascript. It's going to have JQuery. After that, probably not too much. I explained to her the difference between an app and a web site (we're making a web site). There is only one app-like section. Even that is vanilla JS. All that said, I told her to pay attention in the Udacity backbone class. General framework knowledge should let her generalize using JS.

troncheadle 10y ago
> I explained to her the difference between an app and a web site (we're making a web site) What did you say here? I've been thinking a lot about this lately -- In my opinion, a websites are a part of an 'app': the client.
- Spivak 10y ago
  For me the distinction is what the JS is used for. * If you use FE JS to implement any of your sites functionality then you have an app. * If you only use FE JS for just presentation logic then you have a website.
- virmundi 10y ago
  I used an example. An app, that she's familiar with, is Gmail. I said our product is not a desktop application, like Outlook, but for the web. What we're going to do is mostly display static content, refresh the screen on navigation circa 2002, etc. So there are some parts where we need dynamicity, like our menu builder, but for the most part we don't need anything complex. As a result JQuery is fine.
- pault 10y ago
  When I have to explain my job to non-technical people I usually say I build apps "like gmail" not websites "like blogs and company websites"

galfarragem 10y ago

> The common comment is "Just use React". Or Vue.

deleted 10y ago

[deleted]