Twitter | Hanapin | |
Alex Russell
Dragging the web into the mid-naughties. "Probably not wrong about everything" -- Named PWAs '15 w/ ; likely making her ☕
39,114
Mga Tweet
2,711
Mga Sinusundan
20,846
Mga Tagasunod
Mga Tweet
Ni-retweet ni Alex Russell
YIMBY Neoliberal 🥑🌐🏙️ 21 oras
Here's your periodic reminder that the unelected central planning commission in San Francisco is almost entirely made up of wealthy landowners. In a city thats 65% renters, there are more Commissioners who own *second* homes than Commissioners who rent.
Reply Retweet Gustuhin
Alex Russell 10 oras
Sumasagot kay @MylesBorins
Ebisu
Reply Retweet Gustuhin
Ni-retweet ni Alex Russell
Tony Arcieri 19 na oras
Reply Retweet Gustuhin
Alex Russell 11 oras
Sumasagot kay @stubbornella
Also, this list was not current in 2010 🤷🏽‍♂️
Reply Retweet Gustuhin
Alex Russell 11 oras
Sumasagot kay @davidbrunelle
Reply Retweet Gustuhin
Alex Russell 11 oras
You'd scarcely believe the set of things we tried to add that Safari didn't want.
Reply Retweet Gustuhin
Alex Russell 15 oras
I like and subscribe to this view.
Reply Retweet Gustuhin
Ni-retweet ni Alex Russell
Monica Dinculescu 16 na oras
Make sure to send all your and good thoughts to our darling friends at , who’ve been getting DDoSed for like a week now. But you know, one hug at a time, ok? 😭💕
Reply Retweet Gustuhin
Alex Russell 16 na oras
Sumasagot kay @groby @anildash
Also, if you're interviewing in a meat grinder org (>10k people, many touch points in hiring process, blind interview slate, etc.), there's literally no point in sending it. You'll only have recruiter contact and it won't be part of the packet.
Reply Retweet Gustuhin
Alex Russell 16 na oras
Sumasagot kay @awbjs @bradleymeck at 3 iba pa
It's weird this history elides all the stuff we'd learned in Dojo, YUI, Closure, etc. around module loading.
Reply Retweet Gustuhin
Alex Russell 19 na oras
Sumasagot kay @justinfagnani
AMD came directly from our experience with the sync require() mistake I made in Dojo early on. Such a lost opportunity.
Reply Retweet Gustuhin
Alex Russell 20 oras
Sumasagot kay @ljharb
Great thought experiment; teases out what makes these different. For instance: - browser (DOM is largest, most widely used std lib, so relationship priority may be different - node/browser API overlap is left to developers, whereas browser/lang integration is one team
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @AdamRackis @parceljs
"hello world" is ~40KiB of JS on the wire and a reasonable budget is 130KiB of JS *total*. Boxing with two hands tied behind your back. The tools don't even help you enforce reasonable budgets by default! Disaster automation.
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @brianleroux
I'm gonna buy you a phone, Brian.
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @brianleroux
SSDs really saved node's bacon ;-)
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @snookca
We tried designing an element element multiple times; probably time to try again!
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @AdamRackis @parceljs
CRA's default output is...not compatible with the reality of mobile device physics. We need something much better.
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @brianleroux
I guess node programs hide the main thread responsiveness implications behind one-time startup and process pools?
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @AdamRackis @parceljs
I'll be happy for anything that reduces mean-time-to-cursing-compilers-fighting-compilers
Reply Retweet Gustuhin
Alex Russell Abr 6
Sumasagot kay @brianleroux
Do you mean that a graph has to be resolved to allow execution of the importer to proceed? If so...that's wildly different to sync require()
Reply Retweet Gustuhin