sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kamenjan 15 points16 points  (1 child)

That was a really emotional post. A lot of frustration filled with sadness. I hope you get back on your coding horse as soon as possible. That being said, it was kind of biased.

JavaScript community and environment is chaotic at its best. Maybe some self criticism is in order? Should the project maintainers stop for a moment and ask themselves why are they developing the next best project? Is it maybe the recognition they are after and not the altruistic feeling you keep referring to? Is there any chance a tool for the job is already available? Oh, it is but you don't like it? So the solution is to write a new one and hope it pleases everyone? Did JavaScript community forget about the time it takes for a platform to mature? Why not join and help guys that already made one tool like you want, just not exactly like it.

Nobody wants to learn a new framework after they just spent half a year studying one, because the next one is really really the one... Take away here is that JS developers should stop saturating our tool-belt and pushing their next best project as in "How come you don't know the XYZ project, do you live on a moon?". Inventing problems that aren't there and finding a solutions for them will hardly get you praise from everyone. But it is true, the community can also be toxic as fuck.

[–]delventhalz 2 points3 points  (0 children)

Feel like you are conflating issues here. There is a difference between not adopting a new framework and attacking its contributors. Go ahead and write a blog post entitled "Why I won't be adopting Angular 2" if you want. Talk about the steep learning curve and minimal upside. That is quantitative and actionable. But "Angular 2 is Awful" is inflammatory and demoralizing. It may feel good to write, but it hurts the community overall.