• Print

Four short links: 4 July 2013

Model-Driven Configuration, 1,000 RSS Readers Bloom, JSON Query Language, and Doug Engelbart's Vision

  1. ansibleModel-driven configuration management, multi-node deployment/orchestration, and remote task execution system. Uses SSH by default, so no special software has to be installed on the nodes you manage. Ansible can be extended in any language.
  2. The Golden Age of RSSOne of the things I expected least to see in 2013 was that this year would mark the greatest flourishing of RSS reader applications in the decade since it first came to prominence on the web.
  3. JSONiq: the JSON Query Languageexpressive and highly optimizable language to query and update NoSQL stores. It enables developers to leverage the same productive high-level language across a variety of NoSQL products. Implemented in Zorba, an Apache-licensed virtual machine for JSONiq and XQuery queries.
  4. Bret Victor on Doug EngelbartIf you attempt to make sense of Engelbart’s design by drawing correspondences to our present-day systems, you will miss the point, because our present-day systems do not embody Engelbart’s intent. Engelbart hated our present-day systems. Poetic, articulate, and bang on the money.
tags: , , , , , , , , , , , , ,
  • http://acroyear70.livejournal.com/ Joe

    Bret Victor’s is a good read, but I think, as he describes what Engelbart demoed in 1968, he actually does miss that there is a “package” where Engelbart’s collaboration is actually being done: Google Hangout. When combined with the newer ‘apps’ features, that can include Google Drive and therefore all of the spreadsheet and word processing capabilities, and yes, each user gets their own independent editing cursor – full document sharing and editing, not just screen-sharing. Other editors are also available as external plug-ins, allowing for code editing. With Google Drive sync apps for the desktop, everybody has their own copy of the edited product on their local drive as well as in the ‘cloud’.

    So yeah, that particular piece of what he designed is finally in practice today.

    • http://acroyear70.livejournal.com/ Joe

      That said, Google evolved their independent products over the course of years to get to this point, probably each improvement just being seen as “a good idea at the time”. That Englebart foresaw all of this integration in 1950?

  • http://voodoowarez.com rektide de la fey

    Great picks this week!

    Ive been using JQ for json querying. It’s intended more for parallel operations- pulling data out of JSON arrays- versus JSONiq which seems more general purpose.

    My favorite part about Ansible is how data driven it is, or above, model-centric: there’s an inventory of systems, files for configuration data, and those feed into a playbook (the script) which says what to do. As for configuration, Ansible doesn’t tightly couple itself to concerns for how configuration is done (there are no daemons), it just provides really powerful data-driven scripts that can run on a wide number of machines at once. I’m a big fan.