every file format it uses has been created from scratch in order to handcraft the content authoring experience.

Getting hooked on computers is easy—almost anybody can make a program work, just as almost anybody can nail two pieces of wood together in a few tries. The trouble is that the market for two pieces of wood nailed together—inexpertly—is fairly small outside of the "proud grandfather" segment, and getting from there to a decent set of chairs or fitted cupboards takes talent, practice, and education.

the 31,085 lines of configure for libtool still check if <sys/stat.h> and <stdlib.h> exist, even though the Unixen, which lacked them, had neither sufficient memory to execute libtool nor disks big enough for its 16-MB source code.

the Peter Principle, the idea that in an organization where promotion is based on achievement, success, and merit, that organization's members will eventually be promoted beyond their level of ability

graphics/libtiff is one of the 122 packages on the road to www/firefox, yet the resulting Firefox browser does not render TIFF images. For reasons I have not tried to uncover, 10 of the 122 packages need Perl and seven need Python; one of them, devel/glib20, needs both languages for reasons I cannot even imagine.

I also don’t think we’ll be seeing any serious production services running on Deno or Crystal any time soon.

if count > 1 if count < 4 && c != '{' count.times { into << c } else into << '{' << c << count << '}' end elsif c == '{' into << "{{1}" else into << c end end

Where classic TCP relies on packet losses to detect congestion, L4S Prague uses a bit in the IP header as an explicit congestion signal. That bit is called Explicit Congestion Notification (ECN). Using ECN makes it possible to signal congestion early and often. A congestion signal can be sent before the queue begins to fill and without paying the costs of dropping packets. This is one of the major strengths of L4S. Early and frequent signals allow the sender to react less dramatically to congestion signals, so the transmission rate can be fine-tuned quicker and more accurately.

"But if you look at the people, the people are so much like us today. We really should be having peace together."

a lightning-fast compiler

since Ruby code can work for Crystal with just slight changes, I was able to use the best code writing practice in the world: Copy and Paste!

not user-friendly.

The thing is, you’ll have to think about the types you pass and receive while also making sure your code is readable and simple.

for writing a cross-platform tool, Crystal is probably not the perfect choice.

On macOS, this is not supported at all

This is the price we pay for all the benefits static types give us

Phew, describing variants of Hash value types can be annoying, especially when value types are different.

To me, Ruby with explicit, static typing would be like a salad with a scoop of ice cream. They just don't go together.

When I’m in my_app, I can’t do crystal build/run to build or run my project, but I can do shards build/run. But typing crystal docs builds my project documentation, while shards docs does not. Also shards spec does not run my test code, but crystal spec does. In my opinion, when working with an app you created you should be able to manage it entirely with shards build/spec/docs/run all from the root my_app/ directory and it should just work™.

and GitHub/GitLab to store its code