OMG useEffectEvent is still expΓ©rimental πππ
Why can't we have Nice things
OMG useEffectEvent is still expΓ©rimental πππ
Why can't we have Nice things
Optimizing performance is a cornerstone of engineering. Over the past 15 years, I've enhanced performance across various mobile apps. Performance is challenging, but here are my top tips to develop a performance-oriented mindset
A thread π§΅
"Nice to have: As a user I shouldn't be able to enter the password using my keyboard so that I'm not encouraged to use a generated password and a password manager"
"AS A USER I want to be forced to choose a password containing only numbers SO THAT I can type a birthdate more easily" #shittyuserstory
But don't worry this is just a website to invest money β¦ nothing important
Hmmm non je passe mon tour pour cette fois π€£
New blog post: I learned React Native as a web developer, and I got everything wrong fernandorojo.co/mistakes
π’ TypeScript 5.7 is here! Now with
β
Better checks for uninitialized variables
β
Smarter tsconfig lookup in editors
β
Improved startup time
β
Stricter checks for JSON imports
β
Extension rewrites for relative imports
and more! Try it today!
devblogs.microsoft.com/typescript/a...
BIG UPDATE: Our 2.0 release candidate is almost fully stable, and we just published a ton of new docs at arktype.io π
Still more to go, but we hope you find them helpful if you're interested in trying ArkType!
Let's look at Bluesky performance on Android!
I managed to build a release build of the app and ran some traces, let's see what we can find...
I have ~hour, will add to this thread as I investigate
For all the JS/TS devs around here, what do you think about IIFE ? Do you use them ? Is it considered bad practice ?
I found them super useful to mimic kotlin if (or try.catch) expression or simply avoid nested ternaries, but I don't see this pattern as often nowadays
I'll remember the world before and after this PR: github.com/microsoft/Ty...
The new era of conditional types checking is coming in TypeScript 5.8!
βοΈ The React Compiler is not just about memoization
β‘οΈ Platform to build more optimizations π
3 cool upcoming things:
π₯ Type config: help the compiler with extra info
π₯ JSX Inlining: jsx('div') => {type: "div"}
π₯ JSX Outlining: extract subcomponents (see πΌ)
if youβre familiar with event sourcing, itβs basically that but instead of an internal microservice, itβs how the entire network composes. writeup for backend brained folks: atproto.com/articles/atp...
sneak peak of what just landed on main (should go out in one of the next releases)