Twitter | Search | |
Surma
Web Advocate . Internetrovert 🏳️‍🌈 Craving simplicity, finding it nowhere.
16,641
Tweets
1,056
Following
17,791
Followers
Tweets
Surma retweeted
Aaron Turner 9h
Excited to share my new project I *think* is ready! 🎉 Wasm By Example! 📚 A set of hands-on tutorials for the concepts and applications of Wasm with multiple language support! 👫 Accepting new examples, languages, and contributions! 📦
Reply Retweet Like
Surma 10h
Replying to @ag_dubs
Sounds like you wanna manage people.
Reply Retweet Like
Surma 10h
Replying to @majido @argyleink
“master plan”
Reply Retweet Like
Surma 10h
Replying to @ScottKellum @argyleink
That demo is JS-based on a scroll event, tho, which is inherently low-fidelity. Especially on low-end devices the effect can lag behind significantly, as scroll events are not dispatched in real-time. That’s the whole reason why ScrollTimeline was made
Reply Retweet Like
Surma 12h
Replying to @JamesLMilner
O______o
Reply Retweet Like
Surma retweeted
Chrome Developers 13h
🎥 New HTTP 203! Can we do better than "Update available. Click here to reload"? and look at some alternatives for offline-first apps. Watch here:
Reply Retweet Like
Surma 13h
don't you mean "get off my loops"?
Reply Retweet Like
Surma 14h
I strongly discourage from using microbenchmarks to decide which for loop pattern to use
Reply Retweet Like
Surma 15h
Replying to @janl @jaffathecake
I agree with Jan ;)
Reply Retweet Like
Surma 17h
and that's also fine! I have a weak spot for functional programming :D I just think people need to adopt a more pragamatic mindset every now and then. Choose what's more readable and more expressive 🤷‍♂️
Reply Retweet Like
Surma 17h
Replying to @maxlynch
To be honest, the CSS-only solution was motivated by the same frustration, that everyone says scroll events are bad. So we set out to find a solution that doesn't use them. But let's be real, that solution is fairly unpractical
Reply Retweet Like
Surma 17h
Replying to @maxlynch
That native has a very desirable capability there. That's why we've been standardizing animation worklet, which allows you to build fully imperative scroll-linked effects!
Reply Retweet Like
Surma 17h
Replying to @maxlynch
The problem with scroll events is that they are inherently async and can be a couple frames late, so your effect will be desync'd. Unless you force scrolling to happen on the main thread, which is horrible for performance, especially on low-end devices. But I agree, ...
Reply Retweet Like
Surma 17h
that video is just about technicalities of for-loops in JavaScript and let/const. For-loops are not bad. Who's claiming that? Did that someone read about loop invariants?
Reply Retweet Like
Surma 17h
Replying to @codehitchhiker
Out of curiosity: would the tweet be okay if it was posted without the "unpopular opinion" bit?
Reply Retweet Like
Surma 18h
Actually, would know, he wrote
Reply Retweet Like
Surma 18h
IIRC, you only get a list of DataTransferItems that tell you whether it's a string or a file, and if it's a file you get the MimeType. I think you only get the contents on drop.
Reply Retweet Like
Surma 21h
Replying to @tjmonsi
no, they mean they were produced without funding animal cruelty.
Reply Retweet Like
Surma Jun 24
Replying to @steveklabnik
Is this a chrome pun?
Reply Retweet Like
Surma Jun 24
That is very unlikely. It might not be a forged fishing email.
Reply Retweet Like