My reflection comes after reading Jarred's post yesterday, which I found interesting, and then Andrew's today.

I just pasted this article into an LLM to understand the tone and the summary is:

> The overall tone is deeply personal, cathartic, biting, and polemical, with flashes of humor and a deliberate attempt to soften the ending.

I know very little about Jared but his article yesterday, which I read, seemed appreciative of Zig. I now learn he's donated significant chunks of money to them.

This entire article is publicly and personally attacking him for choosing a different product.

It's insane to me that Andrew thinks this post will somehow exonerate Zig when it really just makes them look childish. Or maybe he doesn't care, and just wants to attack Jarred?

This current announcement seems silly, though.

As long as you're vetting your results just like you would any other piece of information on the internet then it's an evolution of data retrieval.

Maybe for a personal project but this doesn't work in a multi-dev environment with paying customers. In my experience, paying attention to architecture and the code itself results in a much more pliable application that can be evolved.

Edit - I'm fine with the article, it's abhorrent and relevant. My tongue in cheek comment was about the comments. These comments give me the same feeling of Reddit - angry people arguing over whether someones death was justified or not.

* for now

We also built one from scratch and used it in client-facing production applications (Angular + React Native). The biggest hurdle is that JSON schema is great at describing the shape of the form data but not a great job at describing how the form looks. We ended up creating a separate "presentation" schema which handled things like order of the form, rows/columns, widgets to use, and much more.