Menu ⇓

  1. Considering the possibility that preferring to use spaces over tabs for code indentation is indicative of excess complacency with the status quo of using complex text formats to express behaviour, and of the viewpoint that code is a static, inflexible material (think raster images vs vector)

  2. Last night: built commenting on posts direct from my feedreader using — video demo:

    Example replies sent using this technique: 1, 2

    Next up: cleaning code, implementing likes, distilling learnt knowledge into diagrams, code.

    Futher reading:

  12. ↪ Ryan Barrett:

    Heard an amazing rumor from a trusted source yesterday: after 10+ years on PHP, Automattic is looking at porting WordPress to Node.js. No joke. Whoa.

    @schnarfed not sure what to think of this. On one hand it might push more webhosts to support “anything other than PHP” which would be great, on the other hand it’s probably going to add to the oft-parroted nonsense that PHP is inherently a bad language.

  20. ↪ Thomas Steiner: Getting started w/ #microformats2 http://microformats.org/2014/03/05/getting-started-with-microformats2 …. @BarnabyWalters, is http://waterpigs.co.uk/php-mf2  100% correct w/ single elem & > 1 type?

    @tomayac for example like this?

    <a class="h-card h-org">Hypothetica Inc.</a>

    php-mf2 gives

    {
    "items": [
        {
            "type": [
                "h-card",
                "h-org"
            ],
            "properties": {
                "name": [
                    "Things"
                ]
            }
        }
    ],
    "rels": [

    ]
}

    which is correct, one microformat with multiple vocabularies, which effectively allows multiple vocabularies to be mixed, e.g. you can have a h-review which is also an h-entry.