3 ms·
> "Non-native" is not always a bad thing. Setting aside the non-native look and the non-native feel, one reason it's almost always a bad thing in practice is b
by CharlesW 6y ago
> "Non-native" is not always a bad thing.
Setting aside the non-native look and the non-native feel, one reason it's almost always a bad thing in practice is because developers who re-invent everything rarely match the accessibility support of the native platform.
- ex3ndr 6y agoSure, if you lazy.
- ByteJockey 6y agoWe're all lazy. That's why we got into this profession.
- KronisLV 6y agoI believe that this applies not just to the front-end development, but also the back-end frameworks and libraries. I've seen people attempt to create their own (oftentimes poorly documented and poorly tested, as well as poorly supported) web frameworks even in large projects far too often. It seems that for any project that needs to be supported and maintained for years if not decades, the argument could be extended to: "Non-native and non-standard is usually a bad thing." Of course, there's nothing wrong with using bleeding edge technology and writing your own frameworks and libraries, however that should only be done when and where it makes sense.