Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kiro: A new agentic IDE

kiro.dev

Post reply on HN
Print view View original

301–310 of 498 posts

Re: Kiro: A new agentic IDE

#301

Post by 9cb14c1ec0 »

didibus wrote: post #163
NathanKP wrote: post #135

Earlier quoted context omitted.

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 result…

That's all old news. Claude Code and even Amazon Q CLI can leverage all this context through MCP as well, with connecting to LSP servers, computing repo-maps or code indexes, integrating with linters, etc. In my opinion, CLIs have a higher ceiling, and then they are easy to integrate into CI/CD, run them in parallel, etc.

The next level of features I want from Claude Code is LSPs built right into it, rather that something I have to configure with some random MCP server I download from some random place.

Re: Kiro: A new agentic IDE

#302

Post by apwell23 »

NathanKP wrote: post #5

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 pr…

> almost 95% AI coded

I think its because you didn't have hard expectations for the output. You were ok with anything that kind of looked ok.

Re: Kiro: A new agentic IDE

#303

Post by Twirrim »

p1necone wrote: post #299
manbash wrote: post #297

> 2. Technical design based on requirements > Kiro then generates a design document by analyzing your codebase and approved spec requirements. It creates data flow diagrams, TypeScript interfaces, database schemas, and API endpoints—like the Review interfaces for our review system. This eliminates the lengthy back-and-forth on requirements clarity that typically slows development. This is nice for documentation but r…

The Eisenhower quote comes to mind: "Plans are worthless, but planning is everything."

If you don't start with approximately the right destination, you're definitely never going to end up there, even if you have to take some detours and compromise on some choices.

It gets really frustrating reviewing people's designs at times, when it's crystal clear they're a) working backwards and b) haven't really considered the customer experience at all.

One of my favourite tell tale signs of a) is when the chosen option 100% fits the specifications, doubly so if there's no cons associated with the pros. Sometimes it's genuine, but very rarely.

Re: Kiro: A new agentic IDE

#304

Post by apwell23 »

suralind wrote: post #12

Here my problem with this: I don't want to be jumping an editor/IDE every 6 months, learning new key bindings and even more importantly, getting used to a completely new look. In a space that moves as quickly as "AI" does, it is inevitable that a better and cheaper solution will pop up at some point. We kinda already see it with Cursor and Windsurf. I guess Claude Code is all the rage now and I personally think CLI/T…

this project was conceived when cursor was the king of vibecoding. Everyone thought being an IDE would give you so much more power.

Re: Kiro: A new agentic IDE

#305

Post by [deleted] »

p1necone wrote: post #299
manbash wrote: post #297

> 2. Technical design based on requirements > Kiro then generates a design document by analyzing your codebase and approved spec requirements. It creates data flow diagrams, TypeScript interfaces, database schemas, and API endpoints—like the Review interfaces for our review system. This eliminates the lengthy back-and-forth on requirements clarity that typically slows development. This is nice for documentation but r…

The Eisenhower quote comes to mind: "Plans are worthless, but planning is everything."

[deleted]

Re: Kiro: A new agentic IDE

#306

Post by the_arun »

manbash wrote: post #297

> 2. Technical design based on requirements > Kiro then generates a design document by analyzing your codebase and approved spec requirements. It creates data flow diagrams, TypeScript interfaces, database schemas, and API endpoints—like the Review interfaces for our review system. This eliminates the lengthy back-and-forth on requirements clarity that typically slows development. This is nice for documentation but r…

I slightly disagree. Plans are really useful for enhancements. If we stick to original plans & patterns as we extend & add new features, we can slow down the decay process.

Re: Kiro: A new agentic IDE

#307

Post by stillpointlab »

zmmmmm wrote: post #286
stillpointlab wrote: post #182

I love all of this experimentation in how to effectively use AIs to co-create output with human steering. This pattern, of the human human focusing on the high-level and the AI focusing on the low level feels like a big win. In some sense, we are starting with a very high-level and gradually refining the idea to a lower and lower levels of detail. It is structured hierarchical thinking. Right now we are at 3 levels:…

> Exposing each of these layers as structured text documents If we take it far enough, we could end up with a well structured syntax with a defined vocabulary for specifying what the computer should do that is rigorously followed in the implemented code. You could think of it as some kind of a ... language for .... programming the computer. Mind blowing.

I get you are being sarcastic, but lets actually consider your idea more broadly.

- Machine code

- Assembly code

- LLVM

- C code (high level)

- VM IR (byte code)

- VHLL (e.g. Python/Javascript/etc)

So, we already have hierarchical stacks of structured text. The fact that we are extending this to higher tiers is in some sense inevitable. Instead of snark, we could genuinely explore this phenomenon.

LLMs are allowing us to extend this pattern to domains other than specifying instructions to processors.

Re: Kiro: A new agentic IDE

#308

Post by WD-42 »

usef- wrote: post #292
blibble wrote: post #206

Earlier quoted context omitted.

> 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...)

I'm surprised none of them have built on Zed yet

Rust is too hard when you can quickly fork vscode and hack together enough JavaScript to hopefully get acquired before the moat evaporates.

Re: Kiro: A new agentic IDE

#309

Post by WD-42 »

slacktivism123 wrote: post #128
ActorNightly wrote: post #122

Earlier quoted context omitted.

While I like the product, implementation could be better. Kiro is sitting idle with Helper Plugin using a shitload of CPU for no reason.

Having ten "Electron Helper (Plugin)" eat a GB of RAM each on idle is the premier desktop experience nowadays. We can't have native apps any more: we don't know how to build them.

Zed exists.
Post reply on HN