Twitter | Search | |
Sebastian Markbåge
React JS · TC39 · The Facebook · Tweets are personal
10,396
Tweets
465
Following
51,734
Followers
Tweets
Sebastian Markbåge retweeted
R 'Nearest' Nabors 💙 19h
I’ll be on this super panel about technical writing Monday! Come ask about how we engage the opensource community to write docs on , how I use my comics skills to illustrate complex topics, and how I got my first tech book ( ) published
Reply Retweet Like
Sebastian Markbåge Aug 3
The main reasons for delegation might not be needed anymore after the changes to discrete events and event replaying. It might still be relevant for perf. I think there are other reasons to more drastically take over events of the whole DOM but it's not enough to just do some.
Reply Retweet Like
Sebastian Markbåge Aug 3
Replying to @dan_abramov
What are you wearing?
Reply Retweet Like
Sebastian Markbåge Jul 24
Replying to @sebmarkbage
Ofc no one always acts as any of these fictional categorizations. I was definitely the middle on in this story, although it based on many individuals.
Reply Retweet Like
Sebastian Markbåge Jul 24
Replying to @sebastienlorber
Yea. This is the difference between immediately start working on it vs. explaining how it could be avoided in the future if it keeps happening and how to identify if the same thing happens again. Identify, Prioritize, Implement.
Reply Retweet Like
Sebastian Markbåge Jul 24
A new developer step through code to find a bug and fixes it. A senior developer guesses what the bug is, spreads a word of warning and was wrong. An experienced developer steps through to find the bug and explains what the bug is how to systematically avoid it in the future.
Reply Retweet Like
Sebastian Markbåge Jul 23
If I know Brian, he's very disappointed in himself for not running 3x the world record.
Reply Retweet Like
Sebastian Markbåge Jul 22
Street food is beautiful. It’s what the poor take for granted and what the rich wish they had. I say that in intentional classist provoking terms.
Reply Retweet Like
Sebastian Markbåge Jul 16
The most depressing thought today is realizing how much COVID-19 research isn't "open source" and subject to state hackers playing games with each other. It didn't really occur to me that the health industry isn't past that yet.
Reply Retweet Like
Sebastian Markbåge Jul 16
Replying to @bmeurer
Another key is thinking of biking end-to-end. Not making individual sections more bike safe. There should be bike lanes separated by physical obstacles away from traffic that can take you anywhere to anywhere in a city. That was done in my home town and now everyone bikes.
Reply Retweet Like
Sebastian Markbåge Jul 16
Replying to @bmeurer
Then make entire streets into walking, parking and biking only. Away from the loud killing machines.
Reply Retweet Like
Sebastian Markbåge Jul 16
Replying to @bmeurer
The strangest trend I've seen is widening side-walks and removing lanes on busy avenues. Yet, there are no shops and it's right next to loud killing machines. So nobody walks there. If anything the key is to move parking away from busy streets and get rid of sidewalks...
Reply Retweet Like
Sebastian Markbåge Jul 10
I’m pretty sure this will be the only way to make API reasonable since all components have to consider this case.
Reply Retweet Like
Sebastian Markbåge Jul 8
Maybe it’s better to bring back a timeout on the boundary itself to indicate how long you think this part of the page will take.
Reply Retweet Like
Sebastian Markbåge Jul 8
This would effectively be more like a minimum time to wait on the whole transition regardless of what is loading, rather than just the outer most boundary. Not sure that makes sense.
Reply Retweet Like
Sebastian Markbåge Jul 8
That makes it not quite idiomatic for where you’d normally place boundaries. So I think maybe we can have a different option that works slightly differently. Eg estimated time to load from the server.
Reply Retweet Like
Sebastian Markbåge Jul 8
I think this is referring to the case when the server is really fast to respond, but not cheaply/recent enough that it should’ve been prefetched. In that case you can by-pass a quick loading state. That requires you to not use a regular suspense boundary for that loading state.
Reply Retweet Like
Sebastian Markbåge Jul 8
Pre-lanes it didn’t make sense to do infinite because the processing order was fixed. Really long pending transitions can also be kind of confusing since you can rewrite the timeline way later. But in practice I think it’ll work out we’ll post-lanes.
Reply Retweet Like
Sebastian Markbåge Jul 8
What’s the use case? Been thinking of just removing the option and effectively making it infinite. Because either you want it to be fast and then you can just move the suspense boundary to kick in early, or you don’t and then it’s effectively infinite.
Reply Retweet Like
Sebastian Markbåge Jul 7
The part in the parenthesis is important. "not the JetPack Compose/Kotlin one that looks similar but doesn't support hoisting to variables which is a deal breaker to me" That approach looks like the JetPack Compose approach to me.
Reply Retweet Like