←back to thread

1014 points QuinnyPig | 1 comments | | HN request time: 0.333s | source
Show context
NathanKP ◴[] No.44561071[source]
Hello folks! I've been working on Kiro for nearly a year now. Happy to chat about some of the things that make it unique in the IDE space. We've added a few powerful things that I think make it a bit different from other similar AI editors.

In specific, I'm really proud of "spec driven development", which is based on the internal processes that software development teams at Amazon use to build very large technical projects. Kiro can take your basic "vibe coding" prompt, and expand it into deep technical requirements, a design document (with diagrams), and a task list to break down large projects into smaller, more realistic chunks of work.

I've had a ton of fun not just working on Kiro, but also coding with Kiro. I've also published a sample project I built while working on Kiro. It's a fairly extensive codebase for an infinite crafting game, almost 95% AI coded, thanks to the power of Kiro: https://github.com/kirodotdev/spirit-of-kiro

replies(27): >>44561401 #>>44561480 #>>44561505 #>>44561508 #>>44561540 #>>44561643 #>>44562248 #>>44562738 #>>44562815 #>>44562867 #>>44562880 #>>44563346 #>>44563915 #>>44563941 #>>44563988 #>>44563992 #>>44564153 #>>44564270 #>>44564551 #>>44565359 #>>44565453 #>>44565634 #>>44565909 #>>44566659 #>>44567132 #>>44568049 #>>44570644 #
theusus ◴[] No.44562867[source]
Why build an editor and not a CLI. VS code is really slow for me and I would have preferred a CLI.
replies(4): >>44563103 #>>44563524 #>>44563566 #>>44565358 #
NathanKP ◴[] No.44563103[source]
Stay tuned! I think there is definitely room for a CLI version as well. That said, IDE's have a significant advantage over CLI because of the features available to them. For example, the reason why IDE's feel "slow" is often because they just come with more features: automatic linters and code formatters, type checkers, LSP servers.

An agent running in the IDE can make use of all this context to provide better results. So, for example, you will see Kiro automatically notice and attempt to resolve problems from the "Problems" tab in the IDE. Kiro will look at what files you have open and attempt to use that info to jump to the right context faster.

The way I describe it is that the ceiling for an IDE agent is a lot higher than a CLI agent, just because the IDE agent has more context info to work with. CLI agents are great too, but I think the IDE can go a lot further because it has more tools available, and more info about what you are doing, where you are working, etc

replies(2): >>44563562 #>>44564310 #
blibble ◴[] No.44564310[source]
> For example, the reason why IDE's feel "slow" is often because they just come with more features:

IDEs don't feel slow, they ARE slow

because written in HTML and Javascript

go and try Delphi from 2005, it's blazing fast (and more functional...)

replies(3): >>44566528 #>>44566532 #>>44568874 #
1. ◴[] No.44566528[source]