Bayor retweetledi
Bayor
146 posts

Bayor retweetledi
Bayor retweetledi

@adedayoagarau This should be printed and distributed in the markets, churches, road side cause these people are the problem
English
Bayor retweetledi
Bayor retweetledi

My dear front-end developers (and anyone who’s interested in the future of interfaces):
I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept):
Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
English
Bayor retweetledi

Many don't get why this is cool. I spent a lot of time optimizing web performance.
It was one of the main things I did at both lovable and spawn.
Here's somewhat simple and thorough explanation:
The browser rendering pipeline goes: Style → Layout → Paint → Composite.
Layout is the expensive step. It calculates where everything goes on the page. Positions. Sizes. Line breaks.
When you read offsetHeight or getBoundingClientRect, you force the browser to run layout. If you wrote to the DOM before that read, it recalculates everything. That's reflow.
A lot of layout work is text measurement. Where does this line wrap. How tall is this paragraph. How wide is this word. The browser is the only thing that can answer these questions. There's no alternative. You have to go through the DOM.
This is the root cause behind a lot of performance problems people deal with daily.
Virtual scrolling exists because you can't know element heights without rendering them first. CSS contain exists to tell the browser "don't recalculate layout outside this box." Batching DOM reads and writes exists because mixing them causes layout thrashing.
Text measurement is a big part of all of these. It's slow and locked inside the browser.
You see it in real apps too.
Slack estimates message heights for virtual scrolling. When the estimate is wrong the scroll jumps. You've seen this.
Google Docs recalculates every paragraph below your cursor when a line wraps. Every keystroke. This is why it gets slow on long documents.
AI chat apps get janky when streaming because each new token can cause a line wrap which changes the height which causes the page to jump.
Same problem every time. Need text measurements. Only way to get them is the DOM. DOM is slow.
---
Over the years people have moved pieces of UI work out of the browser's layout engine. Rendering moved to Canvas and WebGL. Scrolling moved to custom implementations with transforms. Positioning moved to JavaScript-calculated coordinates. Interaction handling was always just JS.
But text was the one thing you couldn't move out. You always had to go back to the DOM to ask "how does this text wrap." Every other piece had an alternative. Text didn't.
---
Enter Pretext. Pure TypeScript text measurement and line wrapping. No DOM. No reflow. You give it text, a font, and a width. It returns exact line breaks, widths, heights. Just a function call. Pure math.
Text measurement was the last piece of layout with no alternative outside the DOM. Now it does.
Cheng Lou@_chenglou
My dear front-end developers (and anyone who’s interested in the future of interfaces): I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept): Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
English
Bayor retweetledi

I’m honoured to be joining 𝕏 to lead design. I believe this is the most important platform in the world, and I can’t think of a more exciting place to help shape the future.
I’m looking forward to working closely with @elonmusk, @nikitabier, and the rest of the team. I’m grateful for the opportunity, humbled to be part of it, and can't wait to get started!

English
Bayor retweetledi

@SkySportsPL LOOOL O'Hara can't see how letting Salah go for free benefits Liverpool.
Maybe that's because he's looking at a balance sheet instead of a football club. Nine years. 255 goals.
Sometimes the best deal is the one where everyone walks away with their legacy intact 👍🏼
English
Bayor retweetledi

i've distilled everything i've written on userinterface.wiki into a single skill file.
119 rules across 11 categories across animations, timings, ux laws, typography, audio, and more.
npx skills add raphaelsalaja/userinterface-wiki

English
Bayor retweetledi

What stands out is how one extreme move forced the whole industry to reexamine how bloated and distant many companies had become.
Whether people liked the method or not, it opened the door for more founders to rethink management layers, technical culture, and speed.
Sometimes one controversial decision shifts the standard for everyone else.
English
Bayor retweetledi
Bayor retweetledi

Bayor retweetledi
Bayor retweetledi
Bayor retweetledi
Bayor retweetledi

this is the demo i shared with the team a couple weeks back.
new 'streaming' plugin is available in today.
Cole@colderoshay
still doing lots in figma...
English
Bayor retweetledi

Calligraph v1.1.1 — calligraph.raphaelsalaja.com
- new number type for rolling animations
- additional animation variants inspired by iOS
try it out — npm i calligraph
English
Bayor retweetledi







