Sure async/await makes your casde more complicated . That reason why, I prefer use Go for I/O wait application because I don't need to manage this Go doesn't it fore me. My code still readable and simple.
Allow you to use GOPROXY directly with go get.
At scale, details matter and Go also :)
Lol, I let you use java spring boot technology. It is really bloat (ram, cpu, disk, infamous slowly startup and jit optimization, complex tuning eg. thread pool and so on). Good luck.
That respects https://12factor.net/dependencies
No
Bye bye Java, still time to switch to real language (e.g Go)
... is dead. Java RIP, thx Oracle.
I prefer qwant
Brave browser is LGTM
I wrote several parsers that I fuzzed with tools like AFL or gofuzz. And I promise you that fix lot ugly corner cases.
Just fuzz every parser you write. And the problem is solved.
Gofmt, and the problem is done.
Sure async/await makes your casde more complicated . That reason why, I prefer use Go for I/O wait application because I don't need to manage this Go doesn't it fore me. My code still readable and simple.
Allow you to use GOPROXY directly with go get.
At scale, details matter and Go also :)
Lol, I let you use java spring boot technology. It is really bloat (ram, cpu, disk, infamous slowly startup and jit optimization, complex tuning eg. thread pool and so on). Good luck.
That respects https://12factor.net/dependencies
No
Bye bye Java, still time to switch to real language (e.g Go)
... is dead. Java RIP, thx Oracle.
I prefer qwant
Brave browser is LGTM
I wrote several parsers that I fuzzed with tools like AFL or gofuzz. And I promise you that fix lot ugly corner cases.
Just fuzz every parser you write. And the problem is solved.
Gofmt, and the problem is done.