3 ms·
> 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
by bbcbasic 10y ago
> 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.
- happycodework 10y ago4 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
- bbcbasic 10y agoHa! These things prove my point. "considered" "promises could be next..." ... think for yourselves! don't let Mr/Mrs famous blogger dictate how you solve problems.