Previously: AR, Physical Web, WebApps, Startups.
Autodidactic Geek, Woodworker, Sailer. Proud Father of 3 boys.
More useful would be "desired JS didn't have a chance to run" but that's much harder to define. We won't have single perfect number for that.
But I'll see if I can get some insights on Monday.
More useful would be "desired JS didn't have a chance to run" but that's much harder to define. We won't have single perfect number for that.
But I'll see if I can get some insights on Monday.
Interesting stuff this signal graph...
Interesting stuff this signal graph...
My 2cents: It's not really what LLMs could do, its: why might developers choose to specifically constrain LLMs to a specific tech stack?
My 2cents: It's not really what LLMs could do, its: why might developers choose to specifically constrain LLMs to a specific tech stack?
Sure, if I just ask a chatbot to hallucinate a demo it might pick a random popular option-- but I could also frame my requirements.
Sure, if I just ask a chatbot to hallucinate a demo it might pick a random popular option-- but I could also frame my requirements.
I think that LLMS only need *sufficient* context to become good at writing in particular style, not necessarily *the most& context.
Like humans, LLMS can become expert developers at many frameworks regardless of which is most popular in the training set.
I think that LLMS only need *sufficient* context to become good at writing in particular style, not necessarily *the most& context.
Like humans, LLMS can become expert developers at many frameworks regardless of which is most popular in the training set.
Seems there are two use cases in particular (right from the docs)
- prerendering hidden new content
- Keep rendering hidden old content
Pre-re-rendering you might say :)
Seems there are two use cases in particular (right from the docs)
- prerendering hidden new content
- Keep rendering hidden old content
Pre-re-rendering you might say :)
HTML swap I think is default, but you can opt to persist nodes (component islands, or dom nodes with state). The default might change...
HTML swap I think is default, but you can opt to persist nodes (component islands, or dom nodes with state). The default might change...
It put into clear terms patterns we were struggling to articulate.
It put into clear terms patterns we were struggling to articulate.
Where are these slopes?
Where are these slopes?
Or maybe optimistic + route changes are a bad idea and you should only use it for simpler things?
Or maybe optimistic + route changes are a bad idea and you should only use it for simpler things?
- transition to a new state
- route change at new state
- useOptimistic (eager state update)
In most of the guidance for transitions they recommended integrating route changes after successful render, not at start.
I think useOptimistic means eager URL update?
- transition to a new state
- route change at new state
- useOptimistic (eager state update)
In most of the guidance for transitions they recommended integrating route changes after successful render, not at start.
I think useOptimistic means eager URL update?
I could really use() an answer! Could you kindly route() me, so I can start to Transition?
I eagerly await your Promise to resolve my query. Please don't reject.
(Why yes, I am dad joke levels of vibe today :)
I could really use() an answer! Could you kindly route() me, so I can start to Transition?
I eagerly await your Promise to resolve my query. Please don't reject.
(Why yes, I am dad joke levels of vibe today :)
Therefore, you are obviously a magician.
Therefore, you are obviously a magician.