3 ms·
This is the question I was going to ask. It seems like porting many of the poor decisions that were made in creating the web to native desktop.
by evinism 11y ago
This is the question I was going to ask. It seems like porting many of the poor decisions that were made in creating the web to native desktop.
- marcus_holmes 11y agoBut that's the point of React - providing an abstraction layer over the poor decisions that were made in creating the web. Apart from Javascript, of course. But that particular "bad decision" is getting modified with every version into something more acceptable ("now with classes!"). I guess the endpoint is that React + Javascript (+ Redux) becomes the defacto language for developing UIs in, and what implements that abstraction layer is immaterial. React-native all the things!
- IshKebab 11y ago> But that particular "bad decision" is getting modified with every version into something more acceptable True, but it definitely seems like they're only fixing the low-hanging fruit. They're never going to fix the insane type system.
- marcus_holmes 11y agoI know I'm a nutter, but I like the type system :) I like that there's "==" and "===", because that's exactly how I think. It fits my use case of "is this the same value as that?" or "is this really equal to that?" exactly. I like that types are fluid, flexible and never get in my way. But there's a religious war here that I think got won by the static type side, so I'm not going there again ;)