3 ms·
I think it can be bad not for yourself, but when you have to start dealing with other peoples' code. There's little consensus on 'best practices' for some of t
by mgkimsal 14y ago
I think it can be bad not for yourself, but when you have to start dealing with other peoples' code. There's little consensus on 'best practices' for some of the newer features, so it's likely you'll end up having to maintain someone else's code who started using new features (closures, for example) without really understanding how they worked, or how they could best be used.
"goto" in PHP is another example of this. I've heard from many people "well, just don't use it!" but... 6 months from now, I'll be handed a codebase that is replete with goto and other stuff that not only do I not use, but the original author didn't really know how to use either.
Adding more features adds more stuff we all have to be aware of, whether or not you use it.