Isn't Skia controlled by Google?

This is why you don’t make your own cross platform toolkit.

I like the idea of a semantic Layer but don't think defining it in yaml is the right way to go about it.

Semantic Layer needs proper language and tooling support which Malloy provides.

Reading the article and the linked Github post, as well as the original pricing announcement and the clarification post afterwards, this whole thing seems like some sort of Monty Python sketch. I can't believe that an actual enterprise targeted product comes up with something like:

> "AWS now defines two types of Kiro AI request. Spec requests are those started from tasks, while vibe requests are general chat responses. Executing a sub-task consumes at least one spec request plus a vibe request for "coordination"".

I still don't understand why pricing can't be as simple as it was initially and presented in a clear and understandable way: token cost this much, you used this many tokens, and that is it. Probably because if people would see how much they actually consume for real tasks, they would realize that the "vibes" cost more than an actual developer.

In his way towards what?

One thing to keep in mind here is that the CEO didn't hide the flaws to make a profit, otherwise he wouldn't have been on board the submersible. He hid them because he believed they were wrong.

Their FOSS local inference service didn't go anywhere.

This isn't Anaconda, they didn't do a bait and switch to screw their core users. It isn't sinful for devs to try and earn a living.