Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don’t mean to be snarky but: have you ever worked at a company where that would be acceptable?

“Hey Boss, I know this looks like shit today and is missing a ton of features but maybe one day we can enhance it”

That wouldn’t fly and since I make components to wrap just about anything we use (third party or custom implementations) so I’m not beholden to it, I can always rewrite that component to use data list (or whatever built-in) if and when it grows up. Also some code gets written once and practically never touched again so my chances to go back and enhance data list as browsers progress is kind of a fairy tale, at least at all the companies I’ve worked at,



The parent advocates extending functionality of native until no longer required, rather than coding your own and having to maintain it indefinitely.

Not using native as-is.


The issue is that you literally cannot extend the native functionality in many cases.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: