I also built the ngrok post in React, and I hadn’t done this sort of work in React before. My personal work is mostly frameworkless, with recent posts using Lit. I like being as close to the browser as possible so I can do fun bespoke stuff.

My friend decided to migrate away from React. Not because it was slow. Because React had “another security thing.” He forwarded a CVE. He didn’t read it. He just highlighted “critical.” And wrote “risk posture” in the Slack thread. They have 312 components. 9 shared packages. A design system held together by hope. He called the rewrite “strategic modernization.” Leadership loves that phrase. They approved it in eight minutes. No one asked what we were migrating to. Including him. He said “anything but React.” That’s not a strategy. But it sounds like one. I asked how we’ll measure success. He said “reduced cognitive load.” Cognitive load is not a metric. So he added a metric. “developer serenity.” He made it up. But it fit in a dashboard. He booked a “migration kickoff.” 90 minutes. 47 attendees. 12 cameras on. One of them was the Staff SRE. He turned it on by mistake. The new stack was “frameworkless.” Which meant: JSX. Hooks. A virtual DOM. But “ours.” They re-invented React. To escape React. He said we’d ship faster now. “2x velocity.” Velocity is already a lie. So 2x is just premium lying. Three weeks in, everything was broken. Forms. Routing. Animations. Error boundaries. They didn’t have error boundaries. Because they were “simplifying.” Simplifying means deleting features you haven’t rebuilt yet. He called it “temporary instability.” Instability means no one can measure the outage. Because nothing is instrumented. So the dashboards stayed green. Green dashboards are a form of truth. Then React Compiler 1.0 dropped. He said this was “the final nail.” The final nail in what? He said “the old paradigm.” Paradigm is a word you use when you don’t want follow-up questions. I asked why we don’t just upgrade React. He said “vendor lock-in.” React is open source. So he clarified: “emotional lock-in.” I scheduled him for a “technical alignment session.” Alignment means I stop resisting. Six months later we shipped. Sort of. The app loads. If you don’t click anything. But we published a case study internally. “Project Phoenix: 38% reduction in UI entropy.” Entropy is not measurable. So we measured: Number of files deleted. We deleted 4,200 files. Mostly tests. But the graph went up and to the right. The CTO loved the graph. He promoted my friend. “Principal Platform Engineer.” Platform means you can break everyone’s week. Next quarter he’s proposing the next refactor. Back to React.

Yo G, I think I can cook a "fastify" adapter for "use workflow" been prototyping a "frameworkless" support for workflow since the last 8hrs (I barely got sleep and I have clock in for in a few hrs 💀) github.com/eersnington/workf…

nitpick that it’s not nextjs workflow - works with any framework (or even standalone/frameworkless :)

1. The ability to ask it to generate components and to be able to add them to design systems and reference them in chats 2. Frameworkless mode: it only generates an index.html 3. A trae.ai-like undo button allowing you to reset the conversation to any past message

What? Trying to figure out what you mean here/are expecting... It's a frameworkless library that can be used as part of any other framework. Huge amount of our testing was actually using it inside Jonathan's huge Vue app. Are you disappointed it wasn't in this list? > It has no dependencies on JavaScript frameworks like React, and works with any modern stack — Rails, Laravel, Svelte, Astro, Next.js, or even plain HTML. Because there's a lot of things not in that list, there's a character limit here 😄 We've maintained a dedicated Vue library for this sort of problem for years, so Vue users aren't the ones who have been wanting this from us either.

you either become an API to an LLM or the architect who guides it the winners will be shapeshifters - frameworkless, fearless, and fluent in what machines can’t yet do

Прикладные книги тоже разные. Есть такие, которые обучают, как использовать определённую версию того или иного фреймворка. И есть такие, которые обучают принципам, например "Frameworkless Front-End Development" или "Build a Frontend Web Framework".

finally a frameworkless rsc primitive ❤️

Frameworkless, btw ;)

Morning dev' - Dungeon Crawler JS From Scratch. Aujourd'hui on "termine ?" notre Dungeon Crawler FullJS et FrameWorkLess twitch.tv/d4rkh0und #javascript #CSS #HTML #PHP

Now available for ACM Members: "Frameworkless Front-End Development: Do You Control Your Dependencies or are They Controlling You?, 2nd Edition," by Francesco Strazzullo. Explore an alt. method of front-end app dev w/o frameworks or 3rd-party libraries. share.percipio.com/cd/azuiS3…

Framework > Frameworkless Unless you want to stay broke forever.

But if you know how to use frameworkless thoroughly, then you can shift to framework It saves time 😀

frameworkless > framework

code from scratch start from an empty file a tabula rasa no click track no reference image tutorial free frameworkless no library no imports no dependencies no docs pure zen dev

POJS (Plain Old Javascript) is still a thing. One of our recent webapps was made that way. Frameworkless has advantages for smaller experimental things if the dev is experienced in it.

I have to submit a web project at school Cooked this up in little time Thanks for the design inspiration @vercel @shadcn Yes, this is frameworkless, and no build It's a school project

The Frameworkless movement: frameworklessmovement.org/

CSS variables are a level of power that we’ve yet to achieve in React Native. Would be a huge unlock. Number of hooks required to toggle light/dark mode would drastically reduce. frameworkless native has this too with colorsets/colors.xml.