A bit of a tour through the Ruby source code seems necessary as the documentation is a bit thin.

:structured - Lumberjack::Formatter::StructuredFormatter - crawls the object and applies the formatter recursively to Enumerable objects found in it (arrays, hashes, etc.).

If you look at the source code you'll see that they're exactly the same thing.

Read the code! No, really. I wrote this code to be read.

The only place I can find it is in the sprockets-rails gem. javascript_include_tag calls this: def find_debug_asset(path) if asset = find_asset(path, pipeline: :debug) raise_unless_precompiled_asset asset.logical_path.sub('.debug', '') asset end end

Check yourself some shell-sources.

If interested, you can check the plain old /bin/sh signal handling in the source code here.

Treating the web as a compile target has a lot of implications, many negative. For example “view source” is a beloved feature of the web that’s an important part of its history and especially useful for learning, but Svelte’s compiled output is much harder to follow than its source. Source maps, which Svelte uses to map its web language outputs back to its source language, have limitations.

they're in the svelte compiler: https://github.com/sveltejs/svelte/blob/master/src/compiler/compile/nodes/Element.ts#L668 (search for the warning text)

I don't read comments as I think they are dangerous

Docker 19.03 does this automatically # by setting the DOCKER_HOST in # https://github.com/docker-library/docker/blob/d45051476babc297257df490d22cbd806f1b11e4/19.03/docker-entrypoint.sh#L23-L29

“The source code for Falcon is so good, I almost prefer it to documentation. It basically can’t be wrong.”

source

From error.c

We believe load test scripts should be plain code to get all the benefits of version control, as opposed to say unreadable and tool generated XML.

I was going through the source for Thin and noticed that instead of using require, Marc-Andre Cournoyer was using a method called autoload to load thin's constituent parts.