quang

[quang @itsquang]

I used to wish I'd have "f*ck you money". Now all I wish is Fable 5 money 😭

[quang @itsquang]

@hieuSSR will try hydration 🥹

[quang @itsquang]

@hieuSSR searched on reddit and some people do have this side effect 🥲

[quang @itsquang]

Most answers to this question won't be honest 🙈

[Jonathan Wilke @jonathan_wilke]

Be honest:

are you still reviewing every line of code your agents generated?

[quang @itsquang]

@_trungpv oldest trick in the book 🤣

[quang @itsquang]

So they extended access to the same 50% promo end date 🥹

[quang @itsquang]

Fable 5 becomes usage-based by Jul 7, but don’t forget there’s an ongoing 50% higher weekly limits until Jul 13. Life’s gonna suck after 13/7 😭

[quang @itsquang]

@_trungpv 🤣

[quang @itsquang]

Fable 5 becomes usage-based by Jul 7, but don’t forget there’s an ongoing 50% higher weekly limits until Jul 13. Life’s gonna suck after 13/7 😭

[shadcn @shadcn]

OH: "Instead of AI taking my job, I now work two jobs to pay for Fable" 🙃

[quang @itsquang]

Question: do senior dev really read AI generated code? I’m an amateur so even thinking about having to read all that code is unpleasant 😅

[Theo - t3.gg @theo]

How much better do the models have to get before you'll stop reading the code?

[quang @itsquang]

@_trungpv 🤣

[quang @itsquang]

It’s funny how Opus is being down but no one cares because they are busy having fun with Fable while it lasts 🤣

[quang @itsquang]

This. It keeps writing self-aware UI copy that confuses users 🤣

[Josh @joshmanders]

I'm begging you @bcherny stop claude from doing this shit everywhere, it's annoying.

[quang @itsquang]

X is great because I can learn UI/UX thinking from the best 🤌

[shadcn @shadcn]

What Makes a Great Streaming Chat Experience

Start here: Never move the reader against their intent.

1. Move only when the reader asked to move.
If someone is reading, don’t pull them somewhere else. Auto-scroll should never be the default.

2. Follow only while they’re following.
If they’re at the live edge, keep the stream in view. If they scroll away, leave them there.

3. Every interaction is intent.
Scrolling is not the only signal. Selecting text, using the keyboard, opening a link, searching should all stop the interface from moving.

4. Start a new turn near the top of the viewport.
This gives the new turn somewhere it can be read from the beginning.

5. Then stream in the answer.
The streaming answer can then grow into the available space.

6. Keep part of the previous conversation in context.
Enough of the previous turn should remain visible so the reader knows where they are. Context.

7. Let new content arrive offscreen.
The conversation can keep streaming without changing what the reader is looking at.

8. Show what’s happening out of view.
Make it clear when a response is still streaming or when new messages have arrived.

9. Make it easy to return to the latest reply.
A "Jump to latest" action should bring the reader back and resume following.

10. Let people jump anywhere in the conversation.
Long threads need message links, search, unread markers, and direct navigation.

11. Reopen where the reader left off.
A saved conversation should open at the last meaningful turn. This is usually the last user message. Not the absolute bottom.

12. Keep the reader’s place when layout changes.
Images load. Markdown expands. Code blocks render. Older messages appear above. None of that should make the reader lose their place.

13. Handle interruptions without stealing position.
Stopping, retrying, regenerating, branching, or errors should not unexpectedly move the conversation.

14. Stay responsive in long threads.
Streaming text, markdown, code, images, and long history should still feel responsive.

15. Be accessible without the noise.
Keep the transcript navigable, preserve keyboard focus, and announce important events at a comfortable pace.

It’s all about the scroll. Scroll Engineering.

[quang @itsquang]

Must be nice having all the compute in the world 🥹

[Guillermo Rauch @rauchg]

Something that I love about working at @vercel is just how enjoyable it is to use our technology. From using the platform to ship new products, to the agents you find in our workspace that make life easier. It's like experiencing the future while building the future 🔁

[quang @itsquang]

Sums up my night 😩

[Vercel Developers @vercel_dev]

WebSockets are now supported on Vercel.

Build realtime apps using standard Node.js libraries, including socket​.io.
https://t.co/DyJI8lxFIU

[quang @itsquang]

@hieuSSR "sometimes"? all the time* admit it, sire 😂

[quang @itsquang]

@jRausell Then it might be fine 😅 Though I'm actually on Golden Gate Dev Beta now. Apparently I never learn, LOL!

[quang @itsquang]

Don't, if you use an external monitor through USB-C for both display and power source.

[Jordi R. @jRausell]

I haven't upgraded to macOS Tahoe yet,
and my Mac keeps reminding me about it.

Is it worth it, or should I just wait as long as I can?