Frontend
Discussions about frontend development, HTML, CSS, JavaScript, browser APIs, web standards, component frameworks, rendering libraries, UI/UX patterns, and tools and technologies used to build websites and web apps!
Darryl Yeo 🛠️ pfp

@darrylyeo

Chrome for Developers: CSS Wrapped 2025 https://chrome.dev/css-wrapped-2025
2 replies
4 recasts
34 reactions

Darryl Yeo 🛠️ pfp

@darrylyeo

80% of the type of frontend engineering work I do is taking a giant soup of one-off UI coupled to particular expressions of application logic, and distilling it into generic, higher-level reusable UI components, with clearly enumerated input variables describing the exact range of styles and behaviors I want, and iterating on these properties as a prerequisite to supporting the unique features I want to add. Without this underlying structure of a design system, you and your agents will be stuck fixing inconsistencies and edge cases for every possible instance and variant of a particular pattern or behavior, across every possible page or screen. Which means adding or changing a feature becomes a tedious O(n) task that scales with the literal amount of features and UI surface area involved, rather than ≈ O(log n) which scales only with the number of unique UI patterns and behaviors that you introduce. In the age of software abundance and one-off vibe-coded UIs that no human software engineer would ever want to maintain, this is the kind of skill that is glossed over and which I think will become a bit of a lost art (which makes me a bit sad). But it’s what makes the difference between an average UI and a scalable, well-maintained UI. Or at least, one that a specialized UI dev or design engineer (increasingly endangered specimens) would be willing to steward for you.
0 reply
1 recast
5 reactions

Darryl Yeo 🛠️ pfp

@darrylyeo

Just discovered that `.getOrInsert()` and `.getOrInsertComputed()` for `Map` / `WeakMap` were made Baseline 2026 "Newly Available" in JavaScript this month. Now my lazy-caching helper functions are beautiful and declarative compared to the imperative and long-winded `.has()` / `.get()` / `.set()` I was doing before 😌
1 reply
0 recast
8 reactions

Darryl Yeo 🛠️ pfp

@darrylyeo

An x86 CPU emulator written in CSS (yes, really): https://lyra.horse/x86css/
3 replies
0 recast
9 reactions

jake pfp

@jklb.eth

Feeling tempted to return to x to stay more connected with fe land @darrylyeo stop me
1 reply
0 recast
4 reactions

Darryl Yeo 🛠️ pfp

@darrylyeo

“There is a growing sentiment that ‘React is the Last Framework’ simply because the AI is so good at writing it. But if we stop innovating because the AI can handle the complexity of the Virtual DOM, we are effectively building the future of the web on top of a frozen mental model that no longer matches how browsers, networks, or users actually behave.” https://youtu.be/wkXvv0iJffg
4 replies
0 recast
9 reactions

C. R. Leovido 🍃🟡 pfp

@leovido.eth

Daaamn, they really hardcoded this into the React types library 😂
25 replies
9 recasts
154 reactions

Darryl Yeo 🛠️ pfp

@darrylyeo

Ladybird’s new User-Agent string. Turns out browser devs are still living with the consequences of the Browser Wars and they have to do funny things like this to get websites to send them modern webpages.
2 replies
0 recast
21 reactions

matt pfp

@matthewmorek

made this little guide for those of you struggling to set up tailwind v4 styles for uploadthing react components in next.js ps. you need a few custom directives in css to get it going https://matthewmorek.com/journal/styling-uploadthing-with-tailwind-css-v4-in-next-js
1 reply
0 recast
3 reactions

matt pfp

@matthewmorek

spent an entire day debugging why my tailwind v4 styles weren’t working in a pnpm monorepo. no errors, no warnings, just vibes from 1997. two config options fixed it. saved you a day: https://matthewmorek.com/journal/fixing-tailwindcss-v4-in-a-monorepo-with-next-js
0 reply
0 recast
2 reactions

typeof.eth pfp

@typeof.eth

. ☀️ ✨😎 👉👕👉 @darrylyeo 🌵👖🌵 🌵 🌵 🌵
1 reply
1 recast
9 reactions

pugson pfp

@pugson

if you want to be great at frontend, you should think of everything as composable layers like in Photoshop. positioning, stacking, scaling things correctly is like 80% of the job.
5 replies
7 recasts
58 reactions

typeof.eth pfp

@typeof.eth

Docusaurus runs a "CSS optimizer" on build which literally moves your rules around. This is so unsafe, it's like they forgot what the C stands for
0 reply
0 recast
1 reaction

v1rtl pfp

@v1rtl.eth

Personal website slight design refresh check at: https://v1rtl.eth.limo
1 reply
0 recast
7 reactions

matt pfp

@matthewmorek

we used to do this with nunjucks templates ten years ago. now nextjs parallel routes let us do the same thing in react, and honestly? love it https://matthewmorek.com/journal/building-a-context-aware-admin-toolbar-with-next-js-parallel-routes
0 reply
0 recast
0 reaction