This may discover services, but not hostnames. If the server does not disclose them (e.g. in the certificate used on the IP host), an attacker doesn't have much further to go on.
The English version of the CCEO (Eastern Code) has some copyright issues:
> This document is temporarily unavailable due to a cease and desist from the Canon Law Society of America. We are hoping for a solution in the near future.
We've been wondering about why it's worth the money for these sponsors. The links ideally shouldn't have much effect because they're marked as `sponsored`.
Anybody got any ideas?
Either way, it's money that helps the project so we're fine with accepting it.
I'm a core developer of Crystal.
Crystal's dynamic nature is only in the source code. It generates highly optimized code thanks to LLVM codegen.
So performance is generally comparable to other compiled languages like Go, Rust or C.
Of course there are differences depending on specific use cases.
A workload with lots of memory allocations means a high workload for GC which could be less efficient than an implementation that uses no garbage collection. But even that depends.
I'm a core developer of Crystal.
Looks like something went very wrong there. The GC may not be super optimised, but it's still practical.
I have never heard about such drastic performance issues. And I'm aware of quite a few companies who use Crystal in heavy production loads for exactly the web server + db use case without such issue reports.
So I'd suggest the root cause might be something else then the GC implementation.
I'm a core developer of Crystal.
Note that there are two different flavours of blocks in Crystal: inlined and captured ones. `return` and `break` are supported in inlined blocks.
That's basically how discussions work in Wikipedia (and other MediaWiki projects). Discussion pages are just a giant text file which anyone can edit fully. The only extra feature over Notepad is an implicit edit history.