The platforms have different ways of exposing various attributes about list and list-items. The API designers then must focus on the trade-off of user friendliness vs control and performance. Thus far it's been about user friendliness, but now they are wading in the waters of control/performance.
That's the reason why there are multiple list views being added, instead of just a single one.
Lists (e.g. UITableView on iOS) are one of the most complex UI components on mobile and might be hard to wrap nicely across iOS and Android, so my guess is they just didn't have time to do it right.
https://github.com/necolas/react-native-web
If you're doing cross-platform prototyping, it can actually be easier than writing the app in React (or vanilla JS) and then porting to React Native, because the React Native elements are at a slightly higher semantic level of abstraction than stock DOM elements. The markup it generates is pretty atrocious, but if you just want to get something up on the screen, you can work out your design compromises first and then optimize it.
But yeah seriously, some pretty basic stuff is neglected and this is a reassurance that there are people at Facebook who are working on it. Listviews are complicated, but pretty much a prerequisite for mobile apps.
