Ok now I'm on the same wavelength. :) I agree platform specific API's will be late to web browsers (if ever) but in a custom web runtime...
-
-
Of course, but why not just using a runtime like
@expo_io ?1 reply 0 retweets 0 likes -
Replying to @Neonsquare @slightlylate and
And in some cases that might be the best solution. I guess it depends on the needs of the app and what you functionality you need. :)
1 reply 0 retweets 0 likes -
Replying to @HeyJonR @slightlylate and
Native and web will more and more merge. Using of webtech in native and native tech in web. I don't believe in putting anything in HTML-DOM
1 reply 0 retweets 1 like -
Replying to @Neonsquare @slightlylate and
I would argue they have already merged? And most apps could be built with pure web tech today as
#PWA without platform specific stuff.2 replies 0 retweets 0 likes -
Replying to @HeyJonR @Neonsquare and
computers only see networks and bytes -- all we have is interpreters for code that is possibly from the network -- "native vs. web" is w/e
1 reply 0 retweets 3 likes -
Replying to @snikhilesh @Neonsquare and
three.js is a "web library" but runs on expo -- the human semantic boundaries we make up limit us, but computers don't see such boundaries
2 replies 0 retweets 2 likes -
Replying to @snikhilesh @slightlylate and
Absolutely! And this is why I think forcing anything eagerly into (often sub par) 'web standards' isn't the best approach to anything
1 reply 0 retweets 0 likes -
Replying to @Neonsquare @snikhilesh and
I feel like this is turning into C# vs Java. There are reasons for writing native yes but there are also a lot of good reasons for
#PWA2 replies 0 retweets 0 likes -
Replying to @HeyJonR @snikhilesh and
#PWA currently is just Google declaring Chrome APIs as standard. This just like MS 'Open' standards like docx. Google is not the web.3 replies 0 retweets 0 likes
This could not be further from the truth. SWs, manifests, push protocol & API -- all designed collaboratively & in the open. Go look.
-
-
Replying to @slightlylate @Neonsquare and
Service Worker effort, e.g., came out of this meeting: http://labs.ft.com/2012/08/fixing-app-cache/ … Designed w/ Mozilla et. al. from Day 1.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @Neonsquare and
We did a lot of the earliest work *in Mozilla offices*
1 reply 0 retweets 0 likes - 4 more replies
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.