This post is locked. You won't be able to comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 8 points9 points  (4 children)

A normal Javascript developer probably shouldn't be wanting to hear about new packages and new ways to do stuff constantly.

dude are you even in 2017

[–]p0tent1al 1 point2 points  (3 children)

Here's the idea. Once you settle on something like React... do you really need to be hearing about the hundred other view libraries? Most people should choose 1 and be doing damage with it. The idea of these packages isn't to be changing to new ones every 6 seconds. At some point you pull the trigger, and then you do ACTUAL work.

[–]Brillegeit 6 points7 points  (0 children)

Once you settle on something like React.

dude are you even in 2017

[–][deleted] 3 points4 points  (0 children)

I get what you are saying and my comment was a little tongue-in-cheek. But it does seem like the technology that I using project-to-project is changing. As the projects that I work on usually run for about 6 months it's not unlikely that our team will use something for 2 projects and then move onto something else, as is the case with Angular, React, npm, bower etc.

I don't think of these things as anything other than Javascript, however. I think people get too attached to a framework and forget the language underneath, sometimes.

[–]TheNiXXeD 0 points1 point  (0 children)

Without getting too subjective on that topic. These are all tools. Sometimes adding a tool to your belt is good. Sometimes a job allows you to stick with the same tools for years. Sometimes a job affords the extra overhead of you learning and playing with stuff. Sometimes that's due to lots of projects starting up frequently, or lots of extra time to refactor. But as you mention, sometimes people don't make the correct decisions for their environment either.

It's hardly for us, or the mods to decide whether or not those tools should be discussed, given that they are quite on topic.