Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But what of the newbie developer? Is he/she going to just roll their own dependencies and do so in a way that's tenable? Green developers make up most of the category.

I guess I was trying to approach a few concerns beyond just dependencies: learning curve, conventions/standards, framework volatility, and merit assess-ability of ideas.

The more people involved (popularity), the greater the difficulty to parse the merit of an idea without pre-existing competence. How easy is it for a new developer to find a cogent way of doing things in Javascript land compared to a smaller more specific ecosystem? In the smaller ecosystem the experts are easier to determine due to a smaller population, whereas in Javascript-land there's so many people, opinions, articles, and conventional disparities; a much more challenging exercise.



In PHP people would (often badly) reinvent the wheel on every project.

In JS people would install packages for every small problem they have.

Neither is good.

I always check if I can write it myself in reasonable time, if not, I install a package for it.

I'd install React, but I'd write the navigation myself.

I'd install a video-player, but I'd write a SVG animation myself.

etc.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: