I feel half of my life is logging in to things these days. Login to Sentry. Login to Google to login to Sentry. Login to 1Password to login to Google. Use Passkey to login to Google. Accept for Google to login to Sentry...
Where the hell did we go so wrong on this? How about I login to my computer and then I'm logged into every other god damn app and website?
@austin_malerba PM can definitely be challenging at times, been working on a similar kind of situation with PM but in the scope of collaborative editing. I can imagine this is also a fun problem, cool!
@Hertz It should be noted that you guys are _still_ trying to charge me for something that had nothing to do with me, or my actions. It was not even an accident, it was a defective vehicle that you gave me.
@hertz has been awful to me. Rented a car from them and within 2 days the back windshield exploded on me while driving. I returned the vehicle to them as it was unsafe and obviously not my fault, to which they tried to charge me $900 for the windshield.
Hey @Hertz you did this this customer DIRTY! She rented this Kia EV and was given zero tools on how to charge. Found her and the KIA with a 12v that was dead at the Monterey ChargePoint charger. She called @AAA_Travel@AAAnews@AAACares for help and they couldn’t do anything for her.
This is how people end up with bad tastes in their mouths about Electric Vehicles.
She was stuck for over 3 hours. Her phone was on 3% and was hopeless. She’s from Rhode Island and flew in earlier today.
Just a few minutes on which app to use for charging and how to actually plug in the vehicle, would’ve helped this girl.
Hoping I changed her mind about EV’s. I paid for the charge and helped her out.
Glad I asked her if she was ok, it allowed for a conversation that helped her get on her way to her hotel.
> Google has announced that starting in June 2024, ad blockers such as uBlock Origin will be disabled in Chrome 127 and later with the rollout of Manifest V3
Ah.
Merge queues are the wrong way to ensure a stable main branch in trunk-based development.
Merge queues are like eager locking a database: They prevent a scenario that itself is very rare but while doing so slow down the common case all the time
A 🧵 about how to do it right
You inspired me, @cassidoo.
Since hooks and the early conception of the suspense API, I have personally felt that React has been obsessed with just a handful of concepts. While technically impressive and undoubtedly pushing the limits and boundaries of what a single-threaded UI API can do, these new concepts have had very little impact on what I do day to day to deliver value to my users (other than making it more complex to "safely"/idiomatically do the same thing or dancing around experimental APIs that my open source users think are officially ready for prime time).
I want so badly for React to return to the client-side-focused and client-performance-obsessed utility I originally loved (or at least help me know better that it still has my interests in mind). It's painful to see other frameworks continuing to deliver on the same motivations that led me to React from day one.
React Forget has drummed up some of that old excitement, but it's easy to get caught up in a new "feature" that in reality is a reactionary answer to a deeper issue. The most brief I can be on this topic is that I really wish we could just drop this obsession with immutability and address true reactivity. Whether that's through signals (please) or not (still fine), this has felt like the most ignored low-hanging fruit for a while (sorry I've been following @RyanCarniato's signals for much longer than most).
Like Cassidy, I'm still using React very heavily and I'm still reaching for it regularly... but with increasing resentment.