gtools VS go

Looks good Do you benchmark it vs for loop? Recently I am wrote pretty similar lib but using functions for all(filter, ForEach etc): gtools Maybe you will find something for yours lib

MicroSCOPE is a software program developed through the [Go](https://go.dev) programming language that allows for the inidetection of a precise category of malicious software. The program is designed specifically for a class of malicious programs called _ransomware_ whose operation consists of data encryption and ransom demand in order to gain access to the content again.

In particular, MicroSCOPE was developed to be able to support two of the mainly used formats: the PE (_Portable Executable_) format for Windows platforms and ELF (_Executable and Linking Format_) for Unix-based platforms. Through the application of certain heuristics, MicroSCOPE is able to assign a score that corresponds to the level of dangerousness of the file being analyzed. The higher the score, the more similar characteristics the software will exhibit to ransomware that has already been studied. The heuristics have been extrapolated from numerous case studies and will be improved over time.

If you want to delve further into concurrency, you can check out this link. If you want to test and see some examples, you can click here. We'll create a separate post to talk about Goroutines, which is a very detailed and interesting topic. We know that Go's support for concurrency makes it a godsend for problems that are best solved using concurrency.

I believe that if Google dies, Go doesn't die with it, as per the license.

Would be great to have the ideas from nbio and gobwas/ws in standard library at some point. Because I personally worry to shift from std lib. Custom TLS implementation makes me nervous, things like QUIC will be not available when I decide I need them in the application, etc. Unfortunately seems that discussions which could make it happen (like this one https://github.com/golang/go/issues/15735) not proceeding these days.

- might be the same info as https://github.com/golang/go/milestone/279 in a different form

It depends on what you're up to, I had different experiences depending on my use case: * CLI - awesome, very comfy - writing utilities to automate some stuff in Docker and Vault was a breeze. * Stateless services - also nice - spinning up web server, generating code from OpenApi spec, or validating stuff with jsonschema was easy to set up. However, I was disappointed with lack of niceties, I.e. nilasempty * Stateful services - bad experience - manually managing transactions and db retries was such a chore. On top of that, we had to switch from CockroachDB to Postgres due to company policy, which resulted in us manually setting the isolation level for each transaction.

Using go professionally for the past year or 2 (granted, not that long, but still), i've had next to zero issues. Only thing i can complain about is the loop variable scoping, which is being fixed

I know somebody is going to rush to defend Go's performance and in many cases you may be right, but web dev is not one of them. Even Go regexes are among the slowest of any language, far behind JavaScript and PHP. The regexp performance issue has been open since 2015. Despite rsc himself being the former Google RE2 open source maintainer, and Google in general having several regex experts and obviously Go experts, nobody has cared enough to make Go's regexes even passably average.