4 ms·

> There are too many good ideas being born right now to risk falling into rigid patterns of thinking. The problem is that there are too many ideas out there, p

by copperx 11y ago

> There are too many good ideas being born right now to risk falling into rigid patterns of thinking. The problem is that there are too many ideas out there, period. It's almost impossible to separate the wheat from the chaff. See: JavaScript libraries.

deleted 11y ago
[deleted]
deleted 11y ago
[deleted]
nkassis 11y ago
Definitely an issue but it shouldn't prevent you from using some tools. For example, I've mostly stayed away from compile to JS languages except for ClojureScript (for personal project) and TypeScript because I see real value in both of them. TypeScript has been a massive boon to help with the largish client side app I work on professionally. Helps keeps the code base somewhat sane and easy to develop in. CSS preprocessors have been similar, cutting down on duplication that leads to potential bugs is hugely useful. Obviously taking small steps and sticking to things as long as there is no major benefit from switching helps. No reason to jump from Angular to React or whatever is new if it's fulfilling your needs.
- omouse 11y ago
  I wish I was using TypeScript right now; we're using babel for ES6 transpiling and I've found a situation where a particular importing of a module doesn't work correctly. It appears correctly when I run it through the eslint tool and babel/webpack don't seem to complain when compiling, but in the browser it doesn't work. When trying TypeScript and CoffeeScript I never ran into issues like that.
  - cnp 11y ago
    OMG, Webpack... you love it and you hate it.... and it never gets easier!
serve_yay 11y ago
But it does not follow from that that the wheat and the chaff are pretty much the same since they came out around the same time.
cnp 11y ago
A pragmatic solution to this problem is to follow certain key developers closely on Github and Twitter, the ones most aligned with the patterns and issues you or your company are addressing. The repos they star and the tweets they forward give you a sort of inside look into where the industry is going; this inspires confidence in decision making.

by copperx 11y ago

deleted 11y ago

[deleted]

deleted 11y ago

[deleted]

nkassis 11y ago

Definitely an issue but it shouldn't prevent you from using some tools. For example, I've mostly stayed away from compile to JS languages except for ClojureScript (for personal project) and TypeScript because I see real value in both of them. TypeScript has been a massive boon to help with the largish client side app I work on professionally. Helps keeps the code base somewhat sane and easy to develop in. CSS preprocessors have been similar, cutting down on duplication that leads to potential bugs is hugely useful. Obviously taking small steps and sticking to things as long as there is no major benefit from switching helps. No reason to jump from Angular to React or whatever is new if it's fulfilling your needs.

omouse 11y ago
I wish I was using TypeScript right now; we're using babel for ES6 transpiling and I've found a situation where a particular importing of a module doesn't work correctly. It appears correctly when I run it through the eslint tool and babel/webpack don't seem to complain when compiling, but in the browser it doesn't work. When trying TypeScript and CoffeeScript I never ran into issues like that.
- cnp 11y ago
  OMG, Webpack... you love it and you hate it.... and it never gets easier!

serve_yay 11y ago

But it does not follow from that that the wheat and the chaff are pretty much the same since they came out around the same time.

cnp 11y ago

A pragmatic solution to this problem is to follow certain key developers closely on Github and Twitter, the ones most aligned with the patterns and issues you or your company are addressing. The repos they star and the tweets they forward give you a sort of inside look into where the industry is going; this inspires confidence in decision making.