Frontend Engineer. Lover of JavaScript and Vue. Obsessed with the Web.
TX
Joined June 2022
- Tweets1.4K
- Following930
- Followers110
- Likes7.7K
Damian Adams retweeted
The paradox is that once a model is able to oneshot something, it becomes worthless.
Doesn't matter how cool it is, since everyone will produce exactly the same and nobody wants to consume it.
Damian Adams retweeted
There is going to be a bit of a weird hangover where we have the last remaining software developers strongly passionate about languages and frameworks when nobody even touches them hands-on anymore.
Like being passionate about which supplier your car manufacturer uses for wiring.
Damian Adams retweeted
👀 Look at this beauty!
😍 There is no better & more beautiful way to stay up-to-date in the Vue & Nuxt ecosystem.
🚀 Read the latest news, GitHub releases and upcoming conferences at VueDigest
Damian Adams retweeted
Nuxt UI has a new theme editor and a new landing: ui.nuxt.com/theme
Pick a preset or roll the dice, bend the palette curves, swap fonts, icons and radius, preview on real templates, then export only what you changed!
Built with @MikeNewbon 💚
Damian Adams retweeted
It’s fascinating how we still can’t solve this. Every UI system just keeps rediscovering the same multi-threading tension: non-blocking execution vs. synchronous expressivity. You just can’t have both. Forever ever.
Web starts with everything on the main thread → moves scrolling/compositing out → needed worklets
RN moved logic off-main-thread → needed worklets
UIKit moves animation/compositing away from the app thread; SwiftUI merged back
Flutter split Dart from the platform thread, merged back
Lynx splits BTS and MTS → now, if we make the engine more async, we need even more UI-thread-local primitives.
We keep redrawing the thread boundary, then reinventing ways to cross it again.
At this point, there’s literally no right or wrong. We’re all just choosing different points in the same trade-off space.
Fun fact: the creator of CoreAnimation is one of the creators of SwiftUI!
The decision to run animations in the app process rather than the render server (as CoreAnimation does) was one of the earliest and most fundamental decisions we made when designing SwiftUI.
Some of the most distinctive experiences of using an iPhone, like UIScrollView rubber banding and SpringBoard app switching are only possible as client-side animations.
But these experiences aren’t easy to build with UIKit!
This is because if you want a UI to be fully interactive and interruptible by the user while it’s animating, it has to be running in the same process as the event handling.
In fact, in iOS 18 we added new APIs to AppKit and UIKit to adopt the SwiftUI client-side animation model.
There are a lot of valid critiques of SwiftUI. The fact that SwiftUI doesn’t use CoreAnimation for its animations is not one of them.
Damian Adams retweeted
All Laravel starter kits now ship with Vite+.
viteplus.dev/
Damian Adams retweeted
Everything feels more high level… what overall ecosystem/community/platform best helps you achieve your goals
Damian Adams retweeted
On August 19, 2011, Web developers Mark Otto and Jacob Thornton of Twitter began creating the CSS framework Bootstrap in mid-2011. The framework was originally developed to help maintain the HTML/CSS and JavaScript code consistency in Twitter applications.
ALT Bootstrap, from Twitter website in 2011
Damian Adams retweeted
🚨 Solid 2.0 has reached Release Candidate! 🎉🥳
Async is first-class — computations return promises, the graph suspends and resumes itself. Plus optimistic mutations and a reactive core rebuilt from scratch.
The Big <Reveal> 👇 solidjs.com/blog/solid-2-0-r…
1/3
Damian Adams retweeted
The limiting factor of software engineering has never been code production. It is complexity management.
Damian Adams retweeted
Octane is absolutely amazing. I've run performance tests on it and it's right in the zone with Solid, Remix V3, vanilla. The React compatibility makes it super easy to use. Octane is a serious contender.
Happy to announce Octane – the successor to Inferno.
React’s programming model, compiled.
Hooks, Suspense and Actions, compiled ahead of time. No virtual DOM. No Rules of Hooks. No manually maintained dependency arrays. The compiler understands what your code captures and generates the reactivity for you.
Octane supports TSX and JSX, along with TSRX for even better DX and performance.
It includes integrations for libraries such as TanStack, React Three Fiber, Lynx and StyleX, plus a compatibility layer for using Octane components inside existing React apps.
Octane is available in alpha today, with beta coming soon.
![// Counter.tsrx — hooks next to output, no rules of hooks import { useState, useEffect } from 'octane'; export function Counter(props) @{ const [count, setCount] = useState(0); // A hook behind a condition is fine — slots are // assigned by call site, not call order. if (!props.paused) { useEffect(() => { console.log('count is now', count); }); // the compiler infers [count] } <button onClick={() => setCount(count + 1)}>{'Count: ' + count}</button> }](https://pbs.twimg.com/media/HOPoguXXAAAEnKq.jpg?name=orig)
ALT // Counter.tsrx — hooks next to output, no rules of hooks import { useState, useEffect } from 'octane'; export function Counter(props) @{ const [count, setCount] = useState(0); // A hook behind a condition is fine — slots are // assigned by call site, not call order. if (!props.paused) { useEffect(() => { console.log('count is now', count); }); // the compiler infers [count] } <button onClick={() => setCount(count + 1)}>{'Count: ' + count}</button> }
Damian Adams retweeted
I wonder if people think innovation is dead in the frontend? At this point it's just incremental performance gains? That there isn't anything to gain architecturally by changing the formula?
It would partially explain why there is resistance to move past old React and excitement around things like Vinext or Redact. The lower excitement around things like Qwik's resumability.
We're never going to move past React unless we move past React.
Damian Adams retweeted
ECMAScript excitement 😉
Last week @TC39 advanced these proposals 🎉
3️⃣ Await dictionary
2️⃣.7️⃣ Thenable curtailment
2️⃣ Error code property
2️⃣ Fused multiply-add
1️⃣ Intl.DateTimeFormat alignment with other standards
1️⃣ Linear matching
1️⃣ Map.take
Damian Adams retweeted
Happy to announce Octane – the successor to Inferno.
React’s programming model, compiled.
Hooks, Suspense and Actions, compiled ahead of time. No virtual DOM. No Rules of Hooks. No manually maintained dependency arrays. The compiler understands what your code captures and generates the reactivity for you.
Octane supports TSX and JSX, along with TSRX for even better DX and performance.
It includes integrations for libraries such as TanStack, React Three Fiber, Lynx and StyleX, plus a compatibility layer for using Octane components inside existing React apps.
Octane is available in alpha today, with beta coming soon.
ALT // Counter.tsrx — hooks next to output, no rules of hooks import { useState, useEffect } from 'octane'; export function Counter(props) @{ const [count, setCount] = useState(0); // A hook behind a condition is fine — slots are // assigned by call site, not call order. if (!props.paused) { useEffect(() => { console.log('count is now', count); }); // the compiler infers [count] } <button onClick={() => setCount(count + 1)}>{'Count: ' + count}</button> }
Damian Adams retweeted
Nuxt 4.5 is out, and it's a big one. 🚀
- ⚡️ Vite 8
- 🦀 Rspack 2, now powered by Rsbuild
- 🌊 experimental SSR streaming for faster TTFB
- 🩺 a new stable error code system
- 🎨 useLayout + named views
... plus a lot of groundwork for Nuxt 5!
💚💚💚
nuxt.com/blog/v4-5
