Hacker News new | ask | show | jobs
by mrkcsc 2890 days ago
To be fair though this exists in Native land too :P but it's sometimes even worse.

EG: In Android in the past there have been bugs in core components like the `RecyclerView` (thing that renders lists) that forced us to downgrade and unlike with React - there is no option there to fork the source and make our own bug fix.
2 comments
EddieRingle 2890 days ago
The support library sources have been published to AOSP for a long time now. And as of recently, they're even developing most of them in AOSP (as opposed too merely syncing changes there occasionally):

https://android.googlesource.com/platform/frameworks/support...

link
mrkcsc 2890 days ago
Thats really cool :D I think getting it to the point where it's not just occasionally synced is really helpful for upstreaming contributions and bug fixes.
link
dagenix 2890 days ago
Maybe a bit pedantic, but, isn't RecyclerView in the support library which is open source? And since the support library is bundled with each app, you actually could fork it and ship a customized version with your app if you wanted.
link
mrkcsc 2890 days ago
It's a valid point :) that probably wasn't the best example - although it would likely be quite a journey to somehow ship the forked support library.

Native iOS would have been a better example as that code is not open source at all.

link
lnanek2 2890 days ago
Embarrassingly, I work for a company that has copied several of the recycler view layout managers out and customized them. And that new Work Manager is unusable right now without in house fixes...
link