Live data from Hacker News

The other kind of JavaScript fatigue

chrismm.com

41–50 of 99 posts

Re: The other kind of JavaScript fatigue

#41
Remember Google’s Polymer? Angular 1? Express? Perhaps the organizations and individuals which cause these abrupt termination events should carry a stigma.

A fantastic idea. There should be some social consequences for these sort of faithless and feckless types.

Re: The other kind of JavaScript fatigue

#42

"Embrace change, and it will make you a better developer." I don't agree with this at all. I think a good coder has complete mastery of their code and tools which is only possible by putting significant time to use one thing instead of jumping one thing to the next ever so often. Imo the best way to become a better developer is not by using what others have created but trying to create libraries and frameworks yourse…

And you are wasting huge amounts of time by rewriting stuff that's already out there tested by thousands of people.

Also collaborating with others becomes much more challenging because you invendted everything.

With experience I can minimize self written code and I can skip plugins and libraries, but I feel better if I can rely on something solid.

It does not apply to all field of programming per se, but web developent is a perfect example.

Re: The other kind of JavaScript fatigue

#43
This sounds pretty much the same as the original concept Javascript fatigue. Too many libraries.

That's an interesting example cited by the author considering the behavior he desires isn't standard. There are multiple possible approaches to serializing an object tree to a query string (and reasons why, conceptually, you might not want to do this in the first place). Incidentally, when I searched for this on StackOverflow, the Q&A I found has a top answer that does deal with nested query strings [1].

[1] http://stackoverflow.com/questions/1714786/querystring-encod...

Re: The other kind of JavaScript fatigue

#44

"Embrace change, and it will make you a better developer." I don't agree with this at all. I think a good coder has complete mastery of their code and tools which is only possible by putting significant time to use one thing instead of jumping one thing to the next ever so often. Imo the best way to become a better developer is not by using what others have created but trying to create libraries and frameworks yourse…

I think you're on to something with the process of becoming better at development. Building the hard/arcane/boring things and understanding them leads to a much larger mental tool set. The solution for problem A could apply to shiny new thing B in a novel way, but you'd never know because A was boring and you have never done it.

That being said, there's practicing your craft and getting shit done. I'm going to be VERY unhappy with a developer that is writing their own take on an MVC framework from scratch for a production project. Unless of course the situation needs it.

Re: The other kind of JavaScript fatigue

#45

"Embrace change, and it will make you a better developer." I don't agree with this at all. I think a good coder has complete mastery of their code and tools which is only possible by putting significant time to use one thing instead of jumping one thing to the next ever so often. Imo the best way to become a better developer is not by using what others have created but trying to create libraries and frameworks yourse…

[deleted]

Re: The other kind of JavaScript fatigue

#46
post #28
post #18

I blame Github, in particular its "stars" feature. It makes putting out code a popularity contest. "Why should I make someone else's project more popular? I'd rather spend my free time making myself popular."

Github seems to want to be a social media site first and a git host second. Which is why I exclusively use Bitbucket now.

Why is socializing with other programmers a bad thing? They manage the core repo hosting quite well. They also act like a solid CDN.

Re: The other kind of JavaScript fatigue

#47
post #41

Remember Google’s Polymer? Angular 1? Express? Perhaps the organizations and individuals which cause these abrupt termination events should carry a stigma. A fantastic idea. There should be some social consequences for these sort of faithless and feckless types.

Polymer is still very alive. I know a bunch of people who work on it full-time.

Re: The other kind of JavaScript fatigue

#48
post #41

Remember Google’s Polymer? Angular 1? Express? Perhaps the organizations and individuals which cause these abrupt termination events should carry a stigma. A fantastic idea. There should be some social consequences for these sort of faithless and feckless types.

Angular 1 is a shame, and it's absolutely right that it shouldn't have been abruptly replaced (though not terminated).

But polymer was and still is barely an alpha, and was practically not used for any real usage (which isn't basically a showcase).

Express is 7 years old and still running strong, continuously being updated and was not terminated or abandoned. Kue.js is just an extension of Express.js with new ideas to accommodate the changes underwent in these 7 years in the node.js ecosystem.

Re: The other kind of JavaScript fatigue

#49
post #24

Earlier quoted context omitted.

> What this article is about? Snippets from SO answers are not as good as battle-tested code? It's obvious and it's same in all languages. It's much harder to ship SO copypasta in say, Java or C#, than in Node. JavaScript is a much easier language to grasp and it is also a lot more forgiving and loose. Combine that with NPM and can suddenly be immensely "productive". But the ability to write and push a lot of code ve…

It only depends on programmer. Somebody copy-paste from SO to production, somebody write tests and run them before deployment. There is a lot of dynamic ("forgiving") languages, so JS is not unique here.

I've seen people change Java code in production to fix a bug and recompile it.

This is hardly a behavior that exists only in dynamic languages.

Re: The other kind of JavaScript fatigue

#50

"Embrace change, and it will make you a better developer." I don't agree with this at all. I think a good coder has complete mastery of their code and tools which is only possible by putting significant time to use one thing instead of jumping one thing to the next ever so often. Imo the best way to become a better developer is not by using what others have created but trying to create libraries and frameworks yourse…

And you are wasting huge amounts of time by rewriting stuff that's already out there tested by thousands of people. Also collaborating with others becomes much more challenging because you invendted everything. With experience I can minimize self written code and I can skip plugins and libraries, but I feel better if I can rely on something solid. It does not apply to all field of programming per se, but web develope…

"Trying to build a framework to understand frameworks" is not the same as "use you own frameworks on your professional projects"

I have written my own Forth, my own filesystem, my own Mvc etc. etc. and I would say they have improved my skill more than learning a new Algol derived language but I would never advocate their use in production.

Post reply on HN