Deactivated my twitter account to take a break, then twitter deleted it. Had activity within weeks, let alone several years!
Through a connection, asked a VP to reactivate, said they can't. Hard to believe it's not just a status field in the DB @elonmusk
https://t.co/CnMZQ2embB
My interactive guide to SVG paths is now live!
A comprehensive deep dive into every single path command complete with challenges where you get to trace over icons. Huge thanks to @iconists for allowing me to use their icons in this guide!
https://t.co/5tUsR7BeXR
@CompoundKFC@jaredpalmer@pyronaur@chronark@vercel Automated testing frameworks and engines make themselves trivial to be detected. The goal is to automate testing, not to spoof real browsers.
They assume that, if the site you're testing includes bot detection, it gets disabled in your testing environment.
@adamwathan There is no reason to exclude one or the other from your toolbox. Some components are more naturally inclined for Right, e.g. if the component needs to have exactly one of each slot prop. Left is better for components that might have zero, or many, of each slot.
@housecor React is made for building interactive apps. Million sounds like it's abandoning that intent in the name of optimizing for static content. Then why even go through the trouble of keeping react in the mix at all? Just write plain HTML at that point. Or use a static generator, no?
@scrumtuous I've seen this done for I/O bound processes. If you need to populate X hundreds of thousands of records as quickly as possible, the main table only contains the critical columns and indexes, and the detail table gets filled in later asynchronously
@housecor With this approach you never need to create a wrapper. Less code, and the wrappers would show up in the component trace when you're debugging, making it harder to read
@housecor Yeah. Add them for arrays still, but if your component has a subject prop (such as user) then conceptually the state belongs to that subject. Don't want state from the old user to leak to the new user, but you're tracking the subject, not the state. State hook could be in a child
@housecor Sorry if this is too terse of an explanation. Let me know if you need me to elaborate. Some of us still have to operate within a character limit lol
@housecor You should add the key to indicate that "Component belongs to Subject" relationship. E.g. UserForm belongs to user, therefore key={https://t.co/q1RsMetkoW}.
Do this no matter if the component has state or not. Not an encapsulation break, you're describing ownership of the comp
One of biggest myths of serverless functions is that they allow you to “focus more on business logic”
It’s a baseless marketing ploy.
You still must worry about CPU, memory, and which region it’s running in.
Plus, you now have to worry about cold start, code size & duration
@kentcdodds The Toyota Sienna is nice, but it's only a hybrid not all-electric, and it's practically impossible to find one unless you're buying it brand new
@dan_abramov I've had that thought process. Like if two branches made a lot of changes to the same file for different reasons, the merge involves adding code that fuses together the goals that both branches were trying to accomplish. A rebase would have hidden that new logic in your branch
Uhh, what the fish?
Autocorrect. The word I wrote did start with an "F" though. Didn't take you long to completely give up on that Free Speech thing, huh?