This works really well btw, at the end of your query ask your LLM to "structure your response as HTML", then view the generated file in your browser. I've also had some success asking the LLM to present its output as slideshows, etc.
More generally, imo audio is the human-preferred input to AIs but vision (images/animations/video) is the preferred output from them. Around a ~third of our brains are a massively parallel processor dedicated to vision, it is the 10-lane superhighway of information into brain. As AI improves, I think we'll see a progression that takes advantage:
1) raw text (hard/effortful to read)
2) markdown (bold, italic, headings, tables, a bit easier on the eyes) <-- current default
3) HTML (still procedural with underlying code, but a lot more flexibility on the graphics, layout, even interactivity) <-- early but forming new good default
...4,5,6,...
n) interactive neural videos/simulations
Imo the extrapolation (though the technology doesn't exist just yet) ends in some kind of interactive videos generated directly by a diffusion neural net. Many open questions as to how exact/procedural "Software 1.0" artifacts (e.g. interactive simulations) may be woven together with neural artifacts (diffusion grids), but generally something in the direction of the recently viral nitter.siddz.com/zan2434/status/2046982…
There are also improvements necessary and pending at the input. Audio nor text nor video alone are not enough, e.g. I feel a need to point/gesture to things on the screen, similar to all the things you would do with a person physically next to you and your computer screen.
TLDR The input/output mind meld between humans and AIs is ongoing and there is a lot of work to do and significant progress to be made, way before jumping all the way into neuralink-esque BCIs and all that. For what's worth exploring at the current stage, hot tip try ask for HTML.
Process vs. Thread
What is a Process?
- A process is an independent program in execution.
It has its own memory space, resources, and state.
- Example: Running Chrome and Spotify → 2 separate processes
Process vs Thread -Key Differences
Memory:
Process → Separate memory
Thread → Shared memory
Communication:
Process → IPC (complex)
Thread → Direct (easy)
Performance:
Process → Slower
Thread → Faster
Crash Impact:
Process → Isolated
Thread → Can affect entire process
Long Polling vs Webhooks — explained simply 👇
Both solve the same problem: “How do I get updates from another system?”
🔁 Long Polling (Client keeps asking… smartly)
Instead of repeatedly hitting the server every second, the client sends a request and the server
👇
Scales better
❌ Cons:
Requires public endpoint
Need to handle security & retries
⚖️ Key Difference:
Long Polling = “Ask and wait”
Webhook = “I’ll notify you”
🎯 When to use?
Use Long Polling:
Chat apps (fallback when WebSockets not available)
Controlled environments
Use Webhooks:
Payments 💳
CI/CD triggers
External integrations
💡 Final takeaway: Long polling reduces how often you ask
Webhooks eliminate asking entirely 🚀
#SystemDesign#Backend#APIs#DistributedSystems
Strong vs Eventual Consistency — explained simply 👇
When you build distributed systems, your data lives on multiple servers.
The challenge? Keeping all copies in sync.
🔒 Strong Consistency: Every read returns the latest data — no exceptions.
🎯 When to use what?
Use Strong Consistency: Payments
Inventory
Authentication
Use Eventual Consistency:
Social feeds
Analytics
Notifications
💡 Final takeaway: Strong consistency = “Always correct, but may be slower”
Eventual consistency = “Fast now, correct soon”
JSON vs Protobuf — which one should you use? 👇
JSON (JavaScript Object Notation) is a text-based, human-readable format widely used in REST APIs. It’s simple, flexible, and easy to debug since you can directly read and edit the data.
Example JSON:
{
"id": 1,
"name": "Alice"
}
When to use Protobuf:
• gRPC services
• Microservices at scale
• Real-time or high-performance systems
• When bandwidth & latency matter
Final takeaway:
JSON is best for ease of use and flexibility.
Protobuf is best for performance and efficiency.