Personally, I think that TypedOM could have waited for a second implementation, since one is already under way. But I'm not that worried.
-
-
Replying to @alanstearns @bfgeek and
Waited how? OT? Some other mechanism?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @bfgeek and
You're creating some risk by shipping now instead of waiting to ship until a second implementation reduces the risk. I think TypedOM is a valuable-enough addition to the platform to have merited more caution.
1 reply 0 retweets 0 likes -
Replying to @alanstearns @bfgeek and
Our platform is losing and lack of fidelity is an oft-cited reason. How many more years of inaction are enough?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @bfgeek and
Unilateral action leads to other ways to lose. The second implementation of TypedOM will likely be ready in weeks or months, not years. As I said, I'm not too worried about this ship decision. But I'm not cheering on the process you used to get to it.
2 replies 0 retweets 1 like -
Replying to @alanstearns @bfgeek and
I suggest we discuss in another forum. Pint this week?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @bfgeek and
Only if you want to troop up to Seattle
1 reply 0 retweets 1 like -
Replying to @alanstearns @bfgeek and
Also happy to arrange a VC (but will need an addr for delivery of pints)
2 replies 0 retweets 2 likes -
Replying to @slightlylate @alanstearns and
BTW: ALSO happy to carry on here. May trade timlimess for quality, but we all know my points were low quality to begin with.
1 reply 0 retweets 1 like -
Replying to @slightlylate @alanstearns
FWIW, Alex: I find your points high quality and I'm glad to see a bit more of the approach your team is taking to push the platform forward.
Also see Alan's point. Glad to see smart folks having respectful debates.
This stuff is hard. Thanks!
1 reply 0 retweets 6 likes
The web is out-and-out losing on mobile. I'd like those who are more in-touch with developer concerns to weigh in, but one I hear frequently is "we can't even make pull-to-refresh"...5+ years later. 
-
-
As a stake in the ground, I think it's fine to be 2-3 years behind native. But more than that? Nerp. That's abdication (and everyone is right to treat it as such).
2 replies 0 retweets 3 likes -
...so if you want to preach caution 5+ years behind, you'd better be coming with smth more than "concerns". Alternative design or substantive critique will suffice. But process pearl-clutching? Hrm...
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.