This probably won't help but it makes for a great quote when speaking about around this topic.
I agree. The first release of IE had a user-agent starting with Mozilla and its something all major browsers (Chrome, Safari, IE, Firefox) still prefix their user-agents with. Mozilla/1.22 (compatible; MSIE 2.0; Windows…
So Russ Cox goes into more detail in this post https://groups.google.com/d/msg/golang-nuts/MdYlJbW4SAo/TrAE... Although Go does not compile via C, occasionally C code does need to refer to Go identifiers. Since we chose…
Given how big the changes/cuts to OpenSSL so far this seems like a positive step towards making it a future credible alternative. As for the vitriolic LibreSSL rhetoric. I for one hope that both projects continue to…
On modern hardware with many cpu cores you can use a similar process of fork and join to maximise throughput of large datasets.
+1 to the request headers and HTTPS support
The redesign looks good. Out of interest why are you not using something like websockets or SSE to push updates to the client?
Are these trivial micro benchmarks, (simply respond with an empty 200) not totally misleading to focus on? Especially when you start to factor in many real workloads that involve disk or network io.
This probably won't help but it makes for a great quote when speaking about around this topic.
I agree. The first release of IE had a user-agent starting with Mozilla and its something all major browsers (Chrome, Safari, IE, Firefox) still prefix their user-agents with. Mozilla/1.22 (compatible; MSIE 2.0; Windows…
So Russ Cox goes into more detail in this post https://groups.google.com/d/msg/golang-nuts/MdYlJbW4SAo/TrAE... Although Go does not compile via C, occasionally C code does need to refer to Go identifiers. Since we chose…
Given how big the changes/cuts to OpenSSL so far this seems like a positive step towards making it a future credible alternative. As for the vitriolic LibreSSL rhetoric. I for one hope that both projects continue to…
On modern hardware with many cpu cores you can use a similar process of fork and join to maximise throughput of large datasets.
+1 to the request headers and HTTPS support
The redesign looks good. Out of interest why are you not using something like websockets or SSE to push updates to the client?
Are these trivial micro benchmarks, (simply respond with an empty 200) not totally misleading to focus on? Especially when you start to factor in many real workloads that involve disk or network io.