⚡️ The first Vite 8.0 beta is here! - Powered by Rolldown, bringing significantly faster production builds and more consistency - New features such as tsconfig paths or emitDecoratorMetadata support - Bumping browser targets aligned with Baseline Widely Available Read more in our announcement post!

how many all-in-one toolchains should i have in my project

Announcing Oxfmt: Oxc Formatter Alpha oxc.rs/blog/2025-1...

Has anyone tried actually running experiments on how they develop with LLM-assisted workflows? I see many subjective takes (pro and negative) but think it'd be neat to record a significant stretch of: - no AI usage - "moderate" usage (e.g. autocomplete, lite chat) - heavy usage (IDE + agentic)

Got asked at Thanksgiving by a family member how to get hired in tech. Like many juniors I've interviewed, their resume/github is all toy projects, which is good for learning but not hiring. I tried to think about what I would do if I had no experience, but knew what I know now.

wlls.dev/blog/on-tail... Every so often I get into a debate on tailwind (mostly yakshaving, IMO). It goes back and forth, usually with people speaking past each other. I finally sat down and put my experience into words on why I like tailwind (and where I don't).

Frontend is failing. 75% of devices with browsers are smartphones, but not even half of sites pass Core Web Vitals on them. Why not? Too much JavaScript, added to indulge SPA fantasies the data is falsifying in real time: infrequently.org/2025/11/perf...

Gleam seems like a much softer entrypoint into the BEAM than Elixir or Erlang for frontend engineers more used to Typescript/C-derived languages. Has anyone made a component/JSX-like templating framework for it? Lustre is elm-y, which I like but is likely foreign to the average React dev.

Alright fine I'll try Gleam

A couple of weeks ago at @perfnow.nl I gave a talk called "Fine-grained everything". It's about @svelte.dev (obviously), and the new frontiers of framework-land, but it's also about some stubborn misconceptions in web performance circles Gift link: conffab.com/presentation...

Some reflections on emergent technology discourse: wlls.dev/blog/rethink... How can we have less polarizing discussions on new technologies/ideas in software? So often it seems we speak past each other, often oversimplifying problems in order to rep "our camp".

👀 Navigation API will be available in all browsers soon 🎉 Completely redefines the APIs used to build client-side routers / SPAs 🫤 History API: popState, link click.preventDefault() ... ✅ Navigation API: clean, centralized way to intercept navigation events 👌

last chance to take the State of JS survey if you haven't already, it closes in a day or two survey.devographics.com/en-US/survey...

The State of JS 2025 survey is now open! survey.devographics.com/survey/state...

Someone explain Elixir / Phoenix LiveView to me. What do you like about it? The model reminds me of sync engines, except Phoenix LV is attacking the problem from the other direction: "what if server side rendering was reactive?" vs "what if client reactivity, but with server state as src of truth?"

Anybody managed to get a SvelteKit app in a Deno monorepo running on Deno Deploy? It can't seem to figure out that the root isn't where the dist is, and there doesn't seem to be any obvious way to override the build directory. Tried many things/am abt ready to throw my hands up and go back to CF.

I want to love @deno.land (as I think their vision is the right direction), but it feels like adoption is slow despite their advances since 2.0. Are there any medium - large companies / projects using Deno that can speak to it?

The duality of wanting to try every new sync engine on the block while also absolutely not needing a local data model for anything I'm currently building.

Was scratching my single brain cell over here trying to figure out how to turn streaming on on my new blog... which is a static site. I think I may have spent too much time "optimizing" SPA architecture lately y'all 🫠

So the joke goes "a platform engineer walked into a React conference..." infrequently.org/2025/06/conferen…

what the fuck is this contrast?

One of the bigger challenges I have had promoting @solidjs.com is assuming developers have a general idea of how their tools work. I'd show off fine-grained rendering, and be met with "Isn't that how React works?" I'd find myself educating them more about their existing tools.

I can't believe it's out, I hope you like it as much as I do, I put a lot of care and effort into that thing. Massive thanks to all my sponsors, small and big, I couldn't have done it without them ❤️

In @syntax.fm 889 they discussed instances where a media query would be preffered over or alongside a container query. I just ran into one such instance while designing a dynamic Search component... syntax.fm/show/889/pla...

2015: > "you just can't do native-like page transitions without a React SPA" 2023: View Transitions API released > Pfft React already lets me do this... 2025: Next.js adds support for "React's 'new' View Transitions API" > "Nextjs View Transitions make page transitions so easy omg!!" 🙄

as people look back on the 70s and remember "everything was brown" will we look back on the 2020s and remember "everything was gradients"

The speed with which companies are abandoning DEI is a clue about how shallow their commitment to it ever was.

Imagine what we could build with AI if we stopped pretending it was going to replace everything

I wonder how many people I can annoy at once: React Compiler is to Signals as NextJS is to Astro

Vitest 3.0 is here!

The next #perfnow video has been released: @mandymichael.bsky.social with Font Performance Strategies youtu.be/P4378iO4oBI

Interesting parallels between modern game and web development. High end hardware enables fancy tech (e.g. DLSS) Fancy tech goes mainstream. Developers get used to this, think less about optimizing. Users on older, lower end hardware are gradually locked out as simple games require the hardware.

People will say that "a few hundred milliseconds" doesn't matter to users (as an excuse to permit slow web dependencies), and then in the same breath will complain that [flavor of the month local dev tooling] is too slow.

It is wild to me how divisive the debate on React STILL is. Was reading through the HN debate [1] on @infrequently.org 's "If Not React, Then What?" [2]. The core, repeated-to-death argument is dead simple. Users before developers. The data is out there! Go look for your own use case!

alexwells.dev/blog/on-ai-a... Having fun is integral to my work. When I can play, I am energized. It is both the act of creation and the creation itself that fulfill me. Without either, the end-result is hollow. Lately I've been reflecting on whether AI is enlarging or diminishing that.