Re:Ask HN: Best things happened to you just because of HN?
by bbcbasic on Monday November 14, 2016 @04:24PM
(#12953508)
> Yesterday's anti-patterns are today's best practises and best practises of today will become tomorrow's anti-patterns
I'm not sure where you are getting this information, but I'd ignore the labelling of things as best practice and anti-pattern and delve deeper into the reason why some design is a bad fit or good fit for the problem you are trying to solve.
A made up example to illustrate:
It may be seen as an anti-pattern to have a site that requires JS and cannot function without it. Tim Burners Lee would not be impressed with you.
On the other hand if you are developing a paid-for web app and you know the users are happy to have JS enabled to use it then this may be less of an issue.
Re:Ask HN: Best things happened to you just because of HN?
by happycodework on Monday November 14, 2016 @08:32PM
(#12954900)
4 real examples to validate op
Goto considered harmful
Jquery .show ()/.hide () is now biggest performance drain in some SPAS
Node callbacks now harmful, async/await or promises could be next... possibly
React is so slow it cannot render > 10 fps for some SPA
Indirectly, a lot of good things have happened to me because of HN as well. Things change very quickly in tech space. Yesterday's anti-patterns are today's best practises and best practises of today will become tomorrow's anti-patterns. I owe a lot to HN which keeps me updated with ever changing tech ecosystem. Being a full-stack developer, I've to keep up with both frontend and backend changes happening everyday. Without HN, I'd not have found out lots of things for sure.