Monday, June 24th, 2019
Replying to a tweet from @simonrjones
Oh, that’s gonna be good! James Burke and Helen Sharman!!
It isn’t even July yet, and I’ve already got Apollo fever:
Next up: the new Apollo 11 documentary @DukeOfYorks this Wednesday:
Reading Other Minds: The Octopus, the Sea, and the Deep Origins of Consciousness by Peter Godfrey-Smith.
Replying to a tweet from @brucel
Thanks, thanks, thanks, Armitage Shanks:
Sunday, June 23rd, 2019
Replying to a tweet from @sil
To take selfies with. Duh!
Saturday, June 22nd, 2019
Replying to a tweet from @carolstran
Thank you both for helping make my dream a reality.
Replying to a tweet from @otakuchick
Friday, June 21st, 2019
Replying to a tweet from @gablaxian
Oh, wow! That looks great! …But I’m going to be out of the country. 😢
Replying to a tweet from @smashingmag
Replying to a tweet from @philnash
I feel like we need a word or phrase to encapsulate SSR + rehydration; just saying SSR doesn’t cover it, in my opinion—it puts the emphasis on the part that isn’t causing the problem.
Replying to a tweet from @slightlylate
For clarity: is the problem with server-side rendering or is the problem with rehydration?
(e.g. if I serve up HTML+CSS and then don’t subsequently dump a bucket of JS on everything, is it fair to say that’s good for performance?)
Thursday, June 20th, 2019
Replying to a tweet from @girlie_mac
On Wall Street, no one can tell that @iamcal is wearing shorts.
Replying to a tweet from @jamesernator
Web standards aren’t like software development. When something lands in a browser, it’s forever. That should not be taken lightly.
Replying to a tweet from @discodavey
Whoops! Looks like an unencoded ampersand slipped in there. Should be all fixed now. (Thanks for letting me know!)
Replying to a tweet from @nekrtemplar
I 100% agree that Apple are the worst at making up proprietary crap behind closed doors.
That in no way absolves other browser vendors from being held to account (especially the browser with the largest market share).