News for hackers. Stuff that matters.
Re:AI Blindspots – Blindspots in LLMs I've noticed while AI ... by dataviz1000 on Wednesday March 19, 2025 @04:35PM (#43417009)
Are you using Cursor? I'm using Github Copilot in VSCode and I'm wondering if I will get more efficiency from a different coding assistant.
Re:AI Blindspots – Blindspots in LLMs I've noticed while AI ... by diggan on Wednesday March 19, 2025 @06:37PM (#43417978)
I've tried Copilot, Aider and Cursor and the best I've found is to just use the various chat interfaces. I sometimes throw hundreds of lines straight in there, and the models seem to understand the full context much better than any "LLM Editor" I've tried so far. Then different models are good for different things (obvious maybe). For example, O1 Pro is miles ahead any models when it comes to overall architecture, R1 is great for finding nasty bugs and Sonnet great for small and fast feature additions/modifications with strict requirements.
Re:AI Blindspots – Blindspots in LLMs I've noticed while AI ... by dsabanin on Wednesday March 19, 2025 @06:00PM (#43417742)
You will. Cursor is much further along on the journey of building an actually powerful AI coding system. Since they are smaller, they can afford to iterate more quickly and experiment with a much tighter feedback loop.
Re:AI Blindspots – Blindspots in LLMs I've noticed while AI ... by ezyang on Wednesday March 19, 2025 @06:45PM (#43418035)
I have used Cursor and my own MCP codemcp. Cursor has a lot of nice QoL that you can't get from an MCP package; the TAB is really good for traditional coding. Haven't used copilot so I don't have a comparison there. Definitely use agent mode.
Re:AI Blindspots – Blindspots in LLMs I've noticed while AI ... by hooloovoo_zoo on Wednesday March 19, 2025 @06:53PM (#43418087)
It doesn't matter. They're all thin layers on functionally equivalent models. Stick with whatever text editor you prefer.