4 ms·
I'm cautiously optimistic about Singular; they've "gone dark" and are implementing it internally, which is kind of disappointing. But for someone (e.g. me) who
by stephen 11y ago
I'm cautiously optimistic about Singular; they've "gone dark" and are implementing it internally, which is kind of disappointing.
But for someone (e.g. me) who:
a) thinks the skill set reuse of React Native is genius (reuse the UI framework/mental model, and purposefully not the widgets), but
b) doesn't like Javascript, I think Singular has the best chance at winning my personal mind share.
Of course, "doesn't like Javascript" is a minority mindset these days, so in terms of community/etc. I'm sure React Native is going to be very strong.
In terms of Flutter/Singular, Flutter trying to play the "write one app for N devices" is interesting...AFAIK, that's something React Native/Singular are explicitly trying to avoid, since historically it's resulted in sub-par UIs on each device.
But it would be an interesting coup if material design meant developers (and users) really did want/expect the same exact L&F on both Android and iOS.
- invalidname 11y agoI am never basing architecture on small Google projects again. We use app engine which has horrible support and billing. We used to use GWT which is no longer maintained. I just don't trust Googles commitment to anything it releases. They throw stuff against the wall to see if it sticks and I ended up with sludge on the floor one time too many.
- stephen 11y ago> We used to use GWT which is no longer maintained I understand where you're coming from, but FWIW this is incorrect: Google has a team of ~4-5 engineers still actively making changes to GWT, and even currently prepping/testing a new release.