$500k for JSON files LOL OK
We rewrote JSONata with AI in a day, saved $500k/year
191–200 of 278 posts
Re: We rewrote JSONata with AI in a day, saved $500k/year
#192The key point for me was not the rewrite in Go or even the use of AI, it was that they started with this architecture: > The reference implementation is JavaScript, whereas our pipeline is in Go. So for years we’ve been running a fleet of jsonata-js pods on Kubernetes - Node.js processes that our Go services call over RPC. That meant that for every event (and expression) we had to serialize, send over the network, ev…
[deleted]
Re: We rewrote JSONata with AI in a day, saved $500k/year
#193These examples of rewrite are fallacy.
See Next.js, over a decade of iterative development. Countless vulnerabilities discovered internally, and externally, which got patches with tribal knowledge acquired by core contributors, security reviewers.
Now Joe shows off he rewrote it with Vite at its core, for just 1,100 dollars worth of token. Performance improvement and no licensing liability.
Outcome: more money for Nvidia, and even more money into the pockets of your next hackers.
Re: We rewrote JSONata with AI in a day, saved $500k/year
#194Earlier quoted context omitted.
The original author said he built this on the weekend, so my assumption is that this was something engineers had advocated for before but were shut down because management wanted them elsewhere. The use of ai agents allowed them to shrink the problem down to the point where it was small enough to fit in their free time and not interrupt their assigned work.
Why are engineers spending their week-end on saving their company money especially if the company clearly doesn't care to allocate resources to the problem? I get that it's fun and there's personal satisfaction in it, but it just reinforces to management that they don't need to care about allocating resources to optimisation, the problem will just take care of itself for free.
A cynical take is that this makes them more hireable, so they can more easily get to a better company with not-so-brain-dead management
This also explains this blog post
Re: We rewrote JSONata with AI in a day, saved $500k/year
#195Earlier quoted context omitted.
Like other commenters already said, there are numerous ways they could have avoided/reduced the $500k/yr cost pre LLM, including simply paying someone to do port the code. So I don't see there is any point in the article.
The point of the article is that that was his way to do it. To show that it is possible to save money with AI rewrites.
Then I have learned nothing new.
Since at least November 2022, everyone in the software industry knows that "it is possible to save money with AI rewrites".
I found nothing I don't already know from the article.
The only way this specific article gained attention is with the number in the headline.
Re: We rewrote JSONata with AI in a day, saved $500k/year
#196The key point for me was not the rewrite in Go or even the use of AI, it was that they started with this architecture: > The reference implementation is JavaScript, whereas our pipeline is in Go. So for years we’ve been running a fleet of jsonata-js pods on Kubernetes - Node.js processes that our Go services call over RPC. That meant that for every event (and expression) we had to serialize, send over the network, ev…
Normally I'd say "Good architecture is far from requirement for profitable product, good enough is good enough, you can optimize later"
...but this is VC funded AI startup, the product might still be burning VC money on each customer ever after optimizing it.
Re: We rewrote JSONata with AI in a day, saved $500k/year
#197They say "embedding V8 directly into Go (to avoid the network hop)" was only an "incremental improvement"
I'm very curious why this didn't help more. That was my first thought. Maybe they didn't get the result they wanted immediately so gave up before evaluating this fully?
Re: We rewrote JSONata with AI in a day, saved $500k/year
#198[flagged]
Re: We rewrote JSONata with AI in a day, saved $500k/year
#199I'm going to be the contrarian here. I have looked at the code. I suspect quite a few nil deref panics in their future.
Re: We rewrote JSONata with AI in a day, saved $500k/year
#200The key point for me was not the rewrite in Go or even the use of AI, it was that they started with this architecture: > The reference implementation is JavaScript, whereas our pipeline is in Go. So for years we’ve been running a fleet of jsonata-js pods on Kubernetes - Node.js processes that our Go services call over RPC. That meant that for every event (and expression) we had to serialize, send over the network, ev…
The result is literally on github
https://github.com/RecoLabs/gnata
I have no idea what is JSONata. It seems it is not THAT hard to rewrite to go, just very tedious, and would cost more than 400 USD in developer time.