News for hackers. Stuff that matters.
Re:Building a high performance JSON parser by stephc_int13 on Sunday June 28, 2020 @06:57AM (#23667973)
It makes me sad every time I see a rewrite from scratch of a working, optimized and well tested library for the sake of writing it in a newer/trendy language...

In my opinion this is much worse than reinventing the wheel.

Especially when the result is, in the end, slower.

Re:Building a high performance JSON parser by enriquto on Sunday June 28, 2020 @12:33PM (#23669945)
> In my opinion this is much worse than reinventing the wheel.

You say it as if reinventing the wheel was a bad thing, but it is not. Technology advances by the continued reinvention of the wheel.

Re:Building a high performance JSON parser by yomly on Sunday June 28, 2020 @08:24AM (#23668264)
Once upon a time, C and scheme were trendy languages.

Since then C has spawned many algol derivatives and the likes of Ruby and Python drew heavy inspiration from Scheme.

I'm not sure when we'll be done or what constitutes "done" but a little churn feels reasonable as a side cost to finding innovation.

Re:Building a high performance JSON parser by jiofih on Sunday June 28, 2020 @08:06AM (#23668211)
Replying to the wrong article? This is neither a rewrite nor slower than the original.
Re:Building a high performance JSON parser by mkcg on Sunday June 28, 2020 @08:27AM (#23668280)
You missed the "streaming" part.

Being able to allocate only a few KB to ingest any JSON is a killer feature.

There is a valid reason to reinvent the wheel : in my case I had to do something similar in C99 for a SaaS federated search engine to have the lowest memory footprint possible.