Ah, that’s great to hear. Missed that from your presentation at TPAC.
-
-
My concern with the quantitative results is their equally weighing the input from a hobbyist working on a pet project and the architect of a top 10 website.
3 replies 0 retweets 0 likes -
I'd much rather hear from the bulk of web developers who are between these two rhetorical poles.
1 reply 0 retweets 1 like -
Well I guess it depends if you’re focused on making a web for developers or for end-users. I posit we should focus on the latter.
2 replies 0 retweets 0 likes -
-
Oh absolutely. The study is focused on the former. The point I’m making is that we’re not looking at the latter. Not that we should only look at the latter.
1 reply 0 retweets 0 likes -
I was under the impression that all browser vendors have folks who speak directly with those top 10 site architects regularly and feed that back into the roadmaps
1 reply 0 retweets 1 like -
...HAHAHAHAHAHA....
.... HAHAAHAHAH....
. Well, maybe @slightlylate does. But generally, no.1 reply 0 retweets 1 like -
this1 reply 0 retweets 0 likes -
We (Chrome) have support from Google's Partnerships and BD teams, which has helped us learn a ton about those needs, but even that is not widely undestood in our team. Fugu, e.g., is *massively* partner/developer need focused, but other teams/projects are more speculative.
2 replies 0 retweets 2 likes
I know that MSFT has been responsive to key developer requests too. Excited to have this survey evidence to counterbalance intuition and anecdotal prioritisation.
-
-
Replying to @slightlylate @marcosc and
That's precisely my concern. Unless this data is weighted by developer reach (which it can't) it risks mixing up what the average dev want vs. what's needed to serve end users well.
1 reply 1 retweet 0 likes -
There's a bigger sampling bias at work: this survey reached web developers, not folks who either left the web or wrote it off. So it's good, but we need multiple sources of input. This is a valuable contribution, but not sufficient to chart a course by.
1 reply 0 retweets 1 like - 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.