Mihai-Alin

PHP & Frontend Developer 💻
Learning about stuff 🚀

[Mihai-Alin @mihaialint]

For the last one, we have an asteroids game where ship positions stream over QUIC datagrams instead of a regular connection, powered by WebTransport.

The neat part is how little it takes: an HTTP/3 connection, a writable stream for position updates sent 20 times a second, and a separate reliable stream for things like deaths and scores. No retransmission queue holding up movement when a packet drops — the next update arrives and renders.

Move your ship, and it appears on the other screen almost instantly. Get hit, and the game state updates reliably

[Mihai-Alin @mihaialint]

Built a writing co-pilot that streams Claude continuations directly into your document — word by word, inline after your cursor, powered by Server-Sent Events.

The interesting part is how little it takes: a POST to register the prompt, an EventSource on the client, and tokens arriving over a plain HTTP stream. No WebSocket handshake, no framework, nothing persistent between sessions.

Hit Tab to continue, Esc to throw it away. The AI text sits highlighted until you decide.

#sse

[Mihai-Alin @mihaialint]

@RileyLuup @WorkfxAI Let's connect!

[Mihai-Alin @mihaialint]

Next up, SSE (Server-Sent Events).

I'm thinking about building either a

AI writing assistant ✅

or

Social media feed 📈

[Mihai-Alin @mihaialint]

Built this today with raw WebSockets (no https://t.co/7O3GBoXtjx).

Two users. One shared buffer. Changes sync instantly — no polling, no refresh, no lag.

Up next: building something with Server-Sent Events to feel the difference

#LearningInPublic

[Mihai-Alin @mihaialint]

WebSockets vs Server-Sent Events vs WebTransport — which one to choose:

WebSockets → full-duplex over TCP. The go-to for chat, collaboration, anything bidirectional. 100% browser support, mature ecosystem.

SSE → server pushes only, but don't sleep on it. Built-in reconnection, runs over plain HTTP/2, and it's what powers AI response streaming. Wildly underrated.

WebTransport → the new kid. QUIC over UDP, no head-of-line blocking, unreliable datagrams for games. Chrome/Edge/Firefox only for now (sorry Safari users).

Rule of thumb:
• Server pushing data only → SSE
• Bidirectional comms → WebSockets
• Low-latency games/media → WebTransport

Over the next few days, I'm building one app for each real-time web communication protocol.

Three protocols. Three apps.

Follow along 👇

[Mihai-Alin @mihaialint]

@umyarX Which one pays better?

[Mihai-Alin @mihaialint]

@athcanft How?

[Mihai-Alin @mihaialint]

Experimenting with AI Agents and MCPs.

[Mihai-Alin @mihaialint]

@saidotdev Build a SaaS, but in public #buildinpublic

[Mihai-Alin @mihaialint]

@RajputNikh13836 TempleOS

[Mihai-Alin @mihaialint]

How it all started.

#sublimetext #vscode

[Mihai-Alin @mihaialint]

@visual_adam What about the money?

[Mihai-Alin @mihaialint]

@beswinjoee Always!

[Mihai-Alin @mihaialint]

@FlorinPop17 @andrewzacker Will he follow back? 😆

[Mihai-Alin @mihaialint]

@Mr_Salio Do you know Dreamweaver? Or tutorials from Envato?

[Mihai-Alin @mihaialint]

@Bhavyaztwt I'm not an animated character

[Mihai-Alin @mihaialint]

@isaidmeow_ What was your job title?

[Mihai-Alin @mihaialint]

@skivthecreator You have pee on your slippers 😬

[Mihai-Alin @mihaialint]

@Taniyatweets_ Lazyness