sonic VS Java-Hello-World-Enterprise-Edition

Since most of the time would be spent decoding json, you could try to cut this time using https://github.com/bytedance/sonic or https://github.com/json-iterator/go, both are drop-in replacements for the stdlib, sonic is faster.

Also worth looking at https://github.com/bytedance/sonic

The article inside does not mention this.

Good morning.I hope this is not the wrong place to post… so let me introduce my first public Golang package. This is a JSON decoder called Sonnet ( https://github.com/sugawarayuuta/sonnet ) that has given faster results (at least in my environment) than Sonic - https://github.com/bytedance/sonic (which is said that it's the fastest) without the help of assembly!

JSON is a very well-known file format. It is used by everyone who does programming. However, it is also not uncommon to find problems with encoding/json and other third-party libraries. for more… (see https://github.com/sugawarayuuta/sonnet#problems-we-had )

I decided to create a new, standard library-compatible decoder that would be both easy to use and fast.

Thanks for reading, feel free to use, help, or ask questions, I look forward to hearing from you. All benchmarks and other information can be found in the link at the top.

Good morning. Let me introduce my first public Go package. This is a JSON decoder called Sonnet ( https://github.com/sugawarayuuta/sonnet ) that has given faster results (at least in my environment) than Sonic (which is said that it's the fastest) without the help of assembly!

I'd say the https://github.com/bytedance/sonic has the fastest encoder due to C and assembly optimization. (Use at your own risk.)

If you judge productivity by lines of code, absolutely.

https://github.com/Hello-World-EE/Java-Hello-World-Enterpris... is an excellent demonstration of this.

This reminds me of the "enterprise programming" mindset in OOP where people would make factories, strategies, strategy factories etc. just for the sake of it (instead of those solutions serving a real need) and ending up codebases that look like Hello World enterprise edition.

No other language or framework seems to get the same scrutiny as JavaScript.

The Enterprise Java solutions never seem to get as much discussion but we all recognize it also as being equally if not more so absurd[1]. This is true of every language and framework that gains mass adoption and use. Scala projects are crazy complex, the python 2 to python 3 migration was a mess, none of these are problems. They reflect the improvements in every metric to the underlying platforms and systems - end user experience, developer experience, reliability, testability etc.

JavaScript is in a phenomenal place today - we have come "full circle" but with better tooling, new capabilities, improved experiences etc.

There's a lot of keeping up with the jones' - that's partly nice as its job security and partly nice as a reflection of engineers improving our own ecosystem.

[1] https://github.com/Hello-World-EE/Java-Hello-World-Enterpris...

It’s bad, but not as bad as the enterprise edition

Hello World Enterprise Edition - https://github.com/Hello-World-EE/Java-Hello-World-Enterprise-Edition

You might actually have to think about writing longass assembly hello world, but I can spin up fifteen Enterprise Java Hello World APIs in an afternoon.

Haven't written Java in years, but I'd take an enterprise edition program written in it, much like this one: https://github.com/Hello-World-EE/Java-Hello-World-Enterprise-Edition