kinlan

26 ms·

211.
by kinlan 10y ago
Funnily, I managed to get this prioristed by eng when we realised it was already backed into ChromeOS by someone tweeting me :)
212.
by kinlan 10y ago
I wrote that demo. I was a little behind schedule and needed a quick example that highlighted the point. I'm not disagreeing with you but there are plenty of good usecases for this and in the case of my blog it's easy to lose tra
213.
by kinlan 10y ago
There are a number of ports powered by Emscripten ( https://github.com/Kagami/ffmpeg.js ) I wrote about some stuff here https://paul.kinlan.me/ffmpeg-ideas/ when building https://paulkinl
214.
Interview with Guillermo Rauch Zeit and Hyper.app(betweenthewires.org)
1 points by kinlan 10y ago|0 comments
215.
Between the wires(betweenthewires.org)
1 points by kinlan 10y ago|0 comments
216.
Sign-in and Payment on the web without Forms(medium.com)
4 points by kinlan 10y ago|0 comments
217.
Google Developers Guide to Web Accessibility(developers.google.com)
4 points by kinlan 10y ago|0 comments
218.
by kinlan 10y ago
Warnings are on all browser versions.. Location was a silly one though, you had to invoke the API to see the error, if you never actaully had devtools open when you called the API then you wouldn't know there was an issue. There has b
219.
by kinlan 10y ago
Yep, so we will likely be breaking our own maps on slow connections... (remember it is not really slow sites that we measure)... but the broader point is, if that script blocked rendering, which it would, then a user on a slow connection wo
220.
by kinlan 10y ago
re: removing document.write completely is a hard balance, soooo much of the web still uses it especially for 1st party script loading that it would be a more impactful issue. I do believe the consensus across all browser vendors is that we
221.
by kinlan 10y ago
You can just do document.write('<script src=" https://example.com/script.js"><\/script>'); and it works
222.
by kinlan 10y ago
There is also some more information here: https://iabtechlab.com/blog/how-to-document-write-better-use...
223.
by kinlan 10y ago
As the person referenced in the article, I am keen to work out how we make developers aware of these changes. We've had the warning on the console for a while now, and it probably still won't be a little while before it roles out
224.
Emojityper(emojityper.com)
1 points by kinlan 10y ago|0 comments
225.
The Building Blocks of Progressive Web Apps(smashingmagazine.com)
11 points by kinlan 10y ago|0 comments
226.
Clousure Compiler now in pure JavaScript(github.com)
2 points by kinlan 10y ago|0 comments
227.
by kinlan 10y ago
They will soon be doing it on Safari on desktop too. https://webkit.org/blog/6589/next-steps-for-legacy-plug-ins/
228.
by kinlan 10y ago
Just one quick one, you mention distribution is a problem. Could you expand on that a little for me?
229.
by kinlan 10y ago
>I think his point is largely that every app maker wants to control the viewport around which content is surfaced, so they can add their own control and bring their own community, auth, ads [3], etc, and we're finally at a point to
230.
by kinlan 10y ago
> That said: the article wanders, doesn't start with or come to a point, and is difficult to follow. It's more a thinking-out-loud exploration than clear draft IMO. I would say that is true, there are a lot of different threads
231.
by kinlan 10y ago
I take your point and to some extent I am certainly hedging on the API fronts, but at this point we know it is technically a solved problem with rough consensus on the path for all browsers modulo deployment. The platform for a broad set o
232.
The headless web(paul.kinlan.me)
91 points by kinlan 10y ago|22 comments
233.
A practical proposal for migrating to safe long sessions on the web(developers.google.com)
101 points by kinlan 10y ago|78 comments
234.
CSS Containment(developers.google.com)
2 points by kinlan 10y ago|0 comments
235.
by kinlan 10y ago
We didn't replace anything, there seems to be a bug in Safari that we have to work around with a translatez() hack.. should be fixed now.
236.
The Lumpy Web(paul.kinlan.me)
1 points by kinlan 10y ago|0 comments
237.
by kinlan 10y ago
We are aware, and it certainly wasn't intentional. Waiting for fix in our impl of Material Design Lite (ironically before we move off it)
238.
by kinlan 10y ago
thanks!
239.
by kinlan 10y ago
It's a very fair point, I chose the word serverless to imply no traditional back-end. One extension that I am looking forward to seeing is the use of DHT in to the WebTorrent that (at least in my head) can eliminate the need for track
240.
by kinlan 10y ago
That is me being lazy and showing a demo/concept experience, not because the web platform can't do this.

More ›