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.
I don't think it's disproportionate. Windows is a huge platform with lots of developers. Also you don't hear anyone asking for other OS support because all other major operating systems are supported. So there's no real comparison.
I bought the 1080p variant. It makes a great preview monitor for video signals, camera output etc.
I'm considering buying a 4k version with touchscreen for travelling, which fits well to the 4k touchscreen on my laptop. Not sure if I actually need touch for a side monitor, though. Or even 4k for that matter...
Getting hot has a lot of complexity, actually: How hot does it get? How can you select the temperature and how accurate is that selection? How well does it maintain the selected temperature?
Simple soldering irons often don't even have temperature selection. And their predetermined temperature drops significantly when heat is transferred into the soldering pieces.
I can dial the Pinecil very accurately to anywhere between 100° C and 400° C, to provide the optimal temperature for the soldering job and it meticulously maintains that temperature (given the power supply is beefy enough).
Another nice feature is automatic stand-by when the tool isn't used. This preserves the tip, saves energy and lowers the risk of accidentally setting anything on fire. It automatically heats up blazingly fast when I pick it up again.
Yeah, there's a switch to select direction. But it activates by pressure.
I'm either screwing a bunch of screws in or out, so it's not a big hassle to use the switch when you need the other.
And this thing generates so much torque, I feel kinda worried about twisting my wrist to select the direction.
IronOS is actually a firmware, not a classical operating system.
The soldering iron is like many modern appliances a smart device and contains a RISC-V CPU on which the firmware runs.
I bought a Pinecil as well this year, and it's really a great tool, and I dare say much more versatile and powerful than many traditional soldering stations which cost much more.
I think Crystal shines with these focus points, except 3. which needs some love (but it's on our radar).
1. C bindings are nice and easy
2. The integrated spec framework builds on the syntax of rspec and is quite capable. Of course it's opinionated, and there are alternatives in the ecosystem.
3. There are some IDE plugins with basic features. Context awareness in source code is an intricate problem because it requires a lot of semantic analysis. So it needs a bit more effort to iron out.
4. Crystal feels like a dynamic language, yet it's fully statically typed. Features like type inference and union types make this possible.
I think this argument is less about the concrete syntactical and semantic similarities to Ruby, but the shared general idea to focus on developer happiness. For example, code is easy to read, yet still expressive.