Readit NewsIf you're running databases continuously, I find a lot of their original unique selling point pretty moot, especially if you're paying them extra for it.
The bullet I quoted makes it seem like you feel punished for having to pay more because you used more resources. That's, like, the fundamental idea of usage-based pricing. If you feel punished, it seems as though you misunderstood the whole idea.
> - Usage-based pricing that punished our success, the more users chatted, the more we paid
This is such a strange position on usage-based pricing and seems telling.
Unless Data Center uses water in a way we dont know?
I suppose not all water cooling systems (especially of this scale) work exactly like e.g. a water-cooled PC.
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
Neither VSCode nor Cursor do this, so even if it's an extension triggering it somehow, the behaviour in Kiro is different to those other two.
Can't we ask legislators to clarify their own legislation?