LLMs often default to a single tech stack (like React, Tailwind, ShadCN). This tendency could reduce competition and innovation in the long run, potentially leading to a development monoculture.
I've slept for too long on open LLMs like Gemma, Llama, Qwen, DeepSeek etc.
They're AMAZING!
Using them is simple (with LM Studio or Ollama) and they're not far behind the "big models" you can access via ChatGPT etc. At least in my experience.
I'm using them for all kinds of tasks...
React Compiler RC (Release Candidate) was released!
Almost one year after its initial release (back then in experimental status), it's now almost ready for production use.
And it can save you LOTS OF time of writing useMemo(), useCallback() and memo()!
Google released a couple of AI Agent related products & services!
The A2A protocol is maybe the most interesting initiative. Also because it kind of clashes with MCP. Or does it?
Microsoft & VS Code are striking back against Cursor & Windsurf. And not just by making GitHub Copilot better...
It's essentially ONE key feature I really don't want to miss anymore.
Well, maybe 1.5 features...
MCP has been a hot buzzword. But what exactly is that model context protocol thing about? And who do LLMs actually use tools?
Obviously, parts of the web dev community are upset: Why didn't they choose Rust?
Well, turns out they had good reasons!
Originally coined by Andrej Karpathy, it describes a way of coding where you don't write any code but you just ask (and blindly trust) LLMs.
React Router 7 is pretty amazing. It always has been.
But v7 especially is exciting because it offers "library mode" and "framework mode".
But "library mode" then actually can be used in at least two different ways.
And the docs don't necessarily cover that very well...