Hacker Newsnew | past | comments | ask | show | jobs | submit | owendarko's commentslogin

What a lot of people don’t mention here is the choice of an AI model.

The key word in the OP post is “Claude”. Anthropic has 2 amazing AI models (Sonnet, Opus), however they’re just a part of a much bigger picture.

When using AI for programming, you’re essentially interacting with AI models. The quality of output you get really depends on the model at the end of the day. Claude Code is optimized for models from Anthropic. You also have model-agnostic agents like Cursor and Kilo Code (disclaimer: I work at Kilo) where you can easily switch up models and see which one works the best for you converting an old jQuery + Django project into SvelteKit.

This area is moving at a crazy rate. Just the last 2 weeks alone, there were 3 main AI model versions released (first Gemini 3, then Opus 4.5, then GPT-5.2). I wrote a piece comparing their performance across 3 coding tasks [1]

So my advice is to also experiment a lot with the models because the quality can vary wildly depending on your stack.

[1] https://blog.kilo.ai/p/we-tested-gpt-52pro-vs-opus-45-vs


You could also use these AI coding features on a plug-and-play basis with an IDE extension.

For example, VS Code has Cline & Kilo Code (disclaimer: I help maintain Kilo).

Jetbrains has Junie, Zencoder, etc.


There are already a bunch of open source, free, and popular "AI coding agent" extensions for VS Code:

1) Cline (1.4mil downloads)

2) Roo Code (a fork of Cline, 450k downloads)

Still a drop in the bucket compared to Cursor in terms of # of users, but they're growing pretty fast.

Disclaimer: I maintain Kilo Code, which competes with 1) and 2) so I'm pretty familiar with this space/the growth patterns.


I am constantly surprised how seldom aider is mentioned in threads like this. I understand that it's not directly integrated into the editor, but the "editor + parallel CLI tool chain" paradigm feels so natural to me because we drop to terminal for so many other parts of building software. If you haven't tried it (particularly the architect/editor modality), it's worth a couple of hours of experimenting.


Aider doesn’t provide any interface that’s integrated into the editor tool, as you point out. That might be true for other similar side-by-side tools that I am not aware of.

But, if you tell aider to watch your files, you can drop a specially formatted comment into your file, and aider will see that and use it as a prompt.

So the integration is sort of “implicit”. Which sounds kinda like the cheap way to go, in comparison to the current brand name tools that have their own chat boxes, dropdowns with mode selectors (ask, edit, agent), and so on.

But look further into the future and an ambient interface is probably where we end up. Something where the Ai agent is just watching what you do, maybe even watching your eyes and seeing what you’re attending to, and then harmonizing its attention to what you are attending to.

But I dunno, i’m just guessing


Tight editor integration means better diffs (right in your editor), easier context manager, and other convenience features that CLI-only tools can't have.

This doesn't mean that aider, claude code, etc. aren't very good tools, but it does make sense to distinguish between built-in tools vs external ones. A similar non-AI example is debugging or linting: IDE integration makes it much easier than using a separate tool.


Continue.dev as well


I happy to know that I am not the only one that know about continue.


It's used a lot by self hosters like myself because you can modify their plugin to talk to your local LLM.


roo and cline also can use local llm


Ah thanks I might look at those too then. I'm not coding very much anyway though.


How are you differentiating from the cline/roo's of the world?


Our plan is to be a superset of Cline and Roo's features (we already have all the major features from both) [0]

We also have our own provider, which means no need to bring your own API keys (you can if you like, but it is batteries included by default) and we're not charging anything on top of the API pricing. Instead of monetizing on individual developers, we want it to be free for them and make money eventually off enterprise contracts [1]

[0]: https://blog.kilocode.ai/p/roo-or-cline-were-building-a-supe... [1]: https://kilocode.ai


I can't find any reference to Cline/Roo charging anything on top of API pricing.

Not sure how they'd do it considering you bring your own API keys. Can you link me to a resource?


GP didn't say Cline/Roo charged anything on top.


The comparison table on the kilo site says "OpenRouter without 5% markup" and only puts a checkbox next to kilo.


Yes - with our built-in provider, we provide all the models that OpenRouter provides but without OpenRouter's 5% markup. We provide them at cost (the AI provider cost)


Roo/Cline doesn't offer Openrouter, markup or not.


You can most definitely use Openrouter with Roo and Cline. Openrouter leaderboards are dominated by these 2 apps.


But they don't OFFER Openrouter a paid product... You cannot give roo/cline dollars and get openrouter api access.


maybe you could answer a question about kilo usage: If I choose Google Gemini as the API provider and give it my Gemini API key, why does it say that I'm low on credits (and I get API request failures immediately)? As far as I understand gemini 2.5 pro preview is free to use. (and in Cline I'm able to choose Google Gemini as the API provider & provide my API key and it will successfully make API requests)



Hey, we can't reproduce it. Could you maybe jump in and give some more details? https://github.com/Kilo-Org/kilocode/issues/349


It looks like a bug to me. Did you report it on GitHub?


We're reaching a point where we don't need to switch to another IDE (from VS Code/IntelliJ/insert-your-IDE-here) for "AI/vibe coding"

IDEs can support "AI coding agents" on their own.

The entire workflow for "AI coding agents" boils down to:

1. You write a prompt

2. The "agent" wraps it in a system prompt and sends it to the LLM

3. The LLM sends back a response

4. The agent performs specific actions based on that response (editing files, creating new ones, etc.)

Microsoft already started doing that with Copilot. And they have a vibrant ecosystem of VS Code extensions (I maintain one of them [1])

"AI agents" should be a feature, not a separate piece of software (IDE) that's integral to software devs.

[1] https://github.com/Kilo-Org/kilocode


There are already VS Code extensions (Cline, Roo Code and Kilo Code) that do the same + are much better IMO.

Disclaimer: I'm one of the maintainers of Kilo.


Why do we need a new IDE for "AI/vibe coding"?

The entire workflow for "AI coding agents" boils down to:

1. You write a prompt

2. The agent wraps it in a system prompt and sends it to the LLM

3. The LLM sends back a response

4. The agent performs specific actions based on that response (editing files, creating new ones, etc.)

I don't see why anyone would ditch their current (non-AI) IDE for Cursor just to get this functionality (especially if you're getting hit with a monthly subscription fee on top of it.)

P.S. I maintain a VS Code extension that does the 4 steps above as a baseline[1]

[1] https://github.com/Kilo-Org/kilocode


It’s vibes investing to match the vibes coding


I think there are 2 or 3 reasons:

1) Popularity. While there are plenty of die-on-a-hill users for ____ app, there are just as many people who will step away to try something and find they like it. Lots of devs use VScode, but its only been around for 10 years. Some people still swear by Notepad++

2) Demand from on-high: When the non-tech boss shows up and says "Everyone use this now". I don't know how much this happens, but it does happen. Technical dictates from someone who shouldn't be making the decision, probably for a non-technical reason.

3) I hesitate to bring this one up, but here we go: People don't know any better. There is a new generation of developers coming up who are leaning hard into vibe coding. And just when I was young, there are plenty of seasoned developers crying out about it's validity. The new generation will pick their own tools - in part to distance themselves from the current generation.


As someone who has basically been told by the boss "I'm the one pushing for AI, so we all have to make it a success" I can see 2 being a thing because it lets them point at the desks and say "see, they're all using the tools."

We're a JetBrains shop, so they showed us Cursor and how to set up Claude in a terminal window, and I think most of our team has been using Claude because we don't want to give up the experience we're used to for the non-AI parts of the day.


I've been very happy with VSCode + Gemini 2.5 (a recentish integration). I will re-evaluate Cursor again but I can't imagine they're going to be able to beat Microsoft to the punch.


There is literally no need for that. Roo or Kilo (extensions for VSCode) are open-source multi-agent plugins that don't require a whole new IDE.


The flat monthly fee charged by Cursor is attractive to many businesses and individuals.


I'm "old school", I do these steps manually.

(It actually helps more, IMO).


After trying a lot of them, the need for a real ide is even stronger. Every single tool I've tried creates bugs, unrequired code, mistakes, hallucinations. Currently playing with Junie and Augment, and CoPilot holds up surprisingly well, not sure why people are so eager to ditch it.


Why do people pay for water bottles when it comes out of the sink for free? Why do people use Dropbox when you could just mount a filesystem with curlftpfs? Why do people pay for Docusign or Postman or Duolingo?


> P.S. I maintain a VS Code extension that does the 4 steps above as a baseline[1]

Still needs an IDE!

Why should I use kilo instead of aider?

https://aider.chat/


1. Kilo Code works inside VS Code. Aider works inside the terminal.

2. Kilo is a feature-merge of Roo+Cline+our own features. This means at least 20 new features are added weekly.


Aider works inside any IDE.

https://aider.chat/docs/usage/watch.html

And there are plugins for many IDEs.

The whole point of my comment is someone (ridiculously) implying you don't need to change IDEs with kilo when kilo is clearly tied to an IDE!


The answer clearly is, because you are already using VS Code. If you're not.. well then use aider.


Honestly main reason is the UI and speed.

Cursor has consistently felt faster and easier to use with better inline auto-complete and faster large edits in chat than VSCode ever did. The way suggestions and chat is shown is just a bit easier to read and more elegantly presented.

These things make a big difference.


Numbering != level of improvements in this case.


Proof that even developers fall for "marketing schemes".


There's definitely a negative sentiment around "vibe coding" on HN. I remember a few days ago seeing a story [1] on the home page which immediately got downvoted/flagged.

[1] https://news.ycombinator.com/item?id=43231978


That probably got flagged for reasons other than "negative sentiment around vibe coding".


Weren't 182 t-shirts sold? That would put the total amount made to 16,653.

But yes, that's the way to calculate it.


I think you're right. A price of 183 means that the seller is offering it to potential buyers at 183, not that it has sold at 183. So your calculation is correct.


Yeah my bad, 183 t-shirts were sold but your total is still correct because the first one was sold for 0.

EDIT: Someone bought another one, so my initial total is now correct lol


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: