hox

Look at the converse - these employees have already been through a thorough background investigation and have been entrusted with highly secure data. These employees probably also have a higher (or at least average) tolerance against "being coerced" as you say into circumventing security mechanisms enforced by their employer - I can only imagine the counterintelligence nightmare that would exist if the clearance vetting process didn't try to weed out easily coerced individuals.

My point being: try not to focus on the negatives of the news, and remember that these are real people, many incredibly talented and trustworthy.

One specific test uses approximately 20k goroutines and averages 15-20MB RAM depending on test load. As for CPU utilization, the impact is minimal; RabbitMQ is the biggest bottleneck, as our peak message throughput for a single RabbitMQ broker is about 50k/messages per second, which our go process is able to handle without much issue. The worst-case scenario that I've been able to test for is one where those 50k messages are evenly spread across different queues; even then, our CPU utilization wasn't any higher than 15%/core on a 12-core server.

My company currently is using Go to monitor and respond to events on hundreds of thousands of RabbitMQ message queues. We create a goroutine for handling each queue, and Go handles all of the concurrency and threading in the runtime while avoiding the resource overhead of standard threads. All of this is done in an application that took about 6 hours to write.

It really made a difference in our experience.

I personally would be interested in the progression of the project. But yes, finding time for yet another project is always fun...

Doesn't show join date, but user IDs are auto-incrementing.

As with everything, it's what you make of it.

I believe a lot of what they have to say is at least interesting to the hacker crowd at large, and as such, they have a place.