Jason Miller 🦊⚛

Introducing Preact Signals: a reactive state primitive that is fast by default. ✅ feels like using plain values 🥳 automatic updates when values change ⏱ updates DOM directly (fast!) 🥹 no dependencies arrays preactjs.com/blog/introduci…

Soon you will be able to roll Preact in vite without Babel github.com/preactjs/prefr…

What if a signal on the server could just be a signal on the client? Wrote about @_developit's mixed-signals - it reflects server-side Preact Signals to clients over any transport. Write your state once as a model, decide where it runs. No fetch glue. No cache invalidation. Just signals. jovidecroock.com/blog/mixed-sig…

@wesbos lol yeah. though... I'd lay partial blame at the feet of CSS for that specific one haha

@_developit I feel like every site I visit has accidental horizontal scroll

Has anyone else noticed mobile frontends (native and web) are getting increasingly terrible (as we descend into UX vibe coding?)? I keep noticing I've developed ridiculous coping strategies like constantly copying input to clipboard in case it gets lost when sending.

@jbscript or the copyright that tells you what year the LLM training data was collected rather than the date the page was last updated

@_developit New hobby: pressing End to jump directly to the end of landing pages which look like one of the 5 designs every LLM will spit out, and watching the obligatory scroll fade fall apart as I scroll up

@QuentinMerabet why test when you can RALPH

@_developit 100%. It feels like nothing is even tested anymore. wtf?

@cultheroro @wesbos probably comes from the same vendor on the same boat anyway

@wesbos @_developit the home depot app is so fucking slow it's unusable. I literally wanted to buy something from them. My ADHD wouldn't let me wait. Now my cat 5 cable comes from amazon. This is on them.

@rossmorsali lol maybe that's the shift - I'm using more frontends from the folks building LLM stuff, and that stuff is all rushed

@_developit I've resorted to similar techniques for very popular web frontends too, directly from the makers of LLMs

@ryanflorence its been going downhill for sure, but really feels like it's accelerated

@_developit i've felt this for over half a decade

@fnthawar If you haven't seen it, the Baroness Von Sketch Show is fucking hilarious (I assume this is a clip from it) gem.cbc.ca/baroness-von-s…

Nailed it

@georgeranch both. I routinely set up and steer serious/large PR work on my phone while I wander around the house trying to feel unchained from the desk

@_developit For serious work? I use to code on my phone too but for POCs nothing serious.

I've been coding on my phone since 2010, what are people so confused about

@NFS__21 lol good god no. I built a nice web app at work for agentic development. For personal stuff I suffer through Codex Web and Claude Code Web (bleeeeeeeeeh). Back in the day though: phone with a keyboard and a shitty text editor.

@_developit Termux ?

Figured I'd open source the little preact+signals mastodon client I wrote a few years ago, in case the code is useful to folks. It's called Mastodawn.com - a streaming, offline-first installable Mastodon web app that weighs under 100kb. github.com/developit/mast…

@aidenybai add Preact! same JSX element annotation as React but the tree is live and hangs off `__k` on the render root element.

Introducing element-source Get the source file location of any DOM (or native!) element Works w/ React, Vue, Svelte, and Solid

the fact that you can't even check similarity without fully publishing is absurd.

npm's package name similarity validation for new packages is fucking ridiculous and should be killed

@RyanCarniato @darylbarnes @trusktr fwiw when I use htm I tend to inject my components into createElement (preact vnode hook but you could also just bind htm to an intermediary function that remaps) so that I can do: html`<my-comp num=${myNum} />`

@darylbarnes @trusktr @_developit JSX isn't html it's XML. Representing a component as markup is very convenient. There are a lot of structural similarities so I think it is the right choice for templating. Everyone does that in their frameworks.

I've been looking at `html` tagged template literals again and man the state of things sucks. I'd be so happy if @_developit's "htm" was the accepted format and we could just get typing going, but as usual there are competing standards and in a lot of ways it makes sense. 1. We have WC folks who have a strong voice in standards that don't care about anything beyond WCs (why should they) but unfortunately WCs are severely limited in a universal sense, so can never be the actual complete answer. 2. We have TS that doesn't want to go through implementing a specific thing like JSX again so unless standards forces their hands they probably aren't going to move. 3. The options for representing tags are either untypable slots, inline case sensitive (goes against standard case insensitivity), or bulky beyond reasonable usage(call create element yourself). I would appeal to WC folks to support some exotic syntax. But honestly if I were them I wouldn't want to. But then again they have no issue proposing their own exotic syntax (like `.`, `@`, and `?`) which IMHO should only be included if HTML supports them. So I get this does devolve into people trying to standardize their own framework. But the TS need is real. A real conundrum.

We shipped @tan_stack Preact-Query 🔥 Welcome to Query @preactjs :) Thanks for the help @TkDodo @_rschristian