stwrt

I have had much better experiences with the desktop apps for managing LLMs compared to the terminal.

Tasks like switching between multiple sessions, copying and pasting, viewing diagrams/web pages, and resuming remote sessions I have found significantly more polished when using the desktop app equivalents.

The author didn't go into much explanation behind "I would be a little nervous about letting people VSCode-remote-edit stuff on dev servers".

If you are worried about having VSCode server-side binaries running directly on the bare metal OS you can isolate the workspace using containers or VMs.

That is incredibly frustrating for a coworker to do that. Even if you do use an LLM to generate all the slides it is your job as a presenter to go through and make edits and actually practice the presentation.

If you are just presenting it for the first time after seeing it you are going to just be reading off the slides, which is a waste of everyones time.

Definitely agree. Most developers could build a basic Twitter or Facebook clone. The hard part is getting the users, content, and relationships that make the product worth coming back to.

The main tradeoff I’ve found with running models like Qwen 3.8 locally is speed. On my hardware, they’re significantly slower than models served through OpenRouter, ChatGPT, or Claude.

That’s been fine for smaller tasks like analyzing a document, but for more involved work like refactoring code the latency makes it harder to iterate.

The web inspector is often overlooked. Other important spots to look at are the Network tab and Lighthouse (in Chrome).

In May they replaced the Gemini CLI with the Antigravity CLI.

https://developers.googleblog.com/an-important-update-transi...