A bit of a monologue about various syntax changes and adjustments in learning and using the tool.
I know. Everyone knows.
That's why I wrote a library that writes to a spreadsheet instead. Ever since I started using it I'm far more productive. I don't know how people are still putting with that god-awful lagging logger.
| #!/usr/bin/env bash | |
| ################################################################################ | |
| # This script can install RUBY binaries on Windows in Bash. | |
| # | |
| # Link to this file: | |
| # https://gist.github.com/andkirby/caf9e825e83f38ad98721956d6e0107c/raw/ruby-bash-win.sh | |
| # | |
| # Download latest version by command in GitBash Windows console: | |
| # $ curl -Ls bit.ly/ruby-bash-win | bash | |
| # |
| ///////////////////////////////////////////////////////////////// | |
| // Created by Kevin Elsenberger // | |
| // June 2, 2013 // | |
| // elsenberger.k at gmail.com // | |
| // from http://playground.arduino.cc/Code/EEPROMReadWriteLong // | |
| ///////////////////////////////////////////////////////////////// | |
| //Needed to access the eeprom read write functions | |
| #include <EEPROM.h> |
Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.
For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.
But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.
SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil
| -- | |
| -- Magento CE database clean-up extended | |
| -- | |
| -- This is an extended clean-up which will clean search, import/export, reports, etc. | |
| -- | |
| -- @author Constantin Bejenaru <boby@frozenminds.com> | |
| -- @copyright Copyright (c) Constantin Bejenaru (http://frozenminds.com/) | |
| -- @license http://www.opensource.org/licenses/mit-license.html MIT License | |
| -- |
| #!/bin/sh | |
| curl "$1/download" | tar zx --strip-components 1 |
| require "rubygems" | |
| # Install the Chef gem into the private Vagrant gem repo | |
| CHEF_VERSION = '11.8.2' | |
| def with_vagrant_gem_path | |
| @old_gem_path = ENV["GEM_PATH"] | |
| @old_gem_home = ENV["GEM_HOME"] | |
| Gem.paths = ENV["GEM_PATH"] = ENV["GEM_HOME"] = "#{ENV['HOME']}/.vagrant.d/gems" | |
| return yield |
| #!/bin/bash | |
| SSH=$HOME/.ssh | |
| [ ! -f $SSH/config ] && touch $SSH/config | |
| [ -f $SSH/config ] && [ ! -f $SSH/config.orig ] && mv $SSH/config{,.orig} | |
| rm -f $SSH/config.vagrant | |
| touch $SSH/config.vagrant | |
| for dir in $(vagrant global-status | grep $HOME) | |
| do | |
| pushd $dir > /dev/null |
| /* | |
| * FancyBox - jQuery Plugin | |
| * Simple and fancy lightbox alternative | |
| * | |
| * Examples and documentation at: http://fancybox.net | |
| * | |
| * Copyright (c) 2008 - 2010 Janis Skarnelis | |
| * That said, it is hardly a one-person project. Many people have submitted bugs, code, and offered their advice freely. Their support is greatly appreciated. | |
| * | |
| * Version: 1.3.4 (11/11/2010) |
| <?php | |
| /** | |
| * Narno Gettext Translate model | |
| * (overlap of Mage_Core_Model_Translate) | |
| * | |
| * Support Gettext file (binary). | |
| */ | |
| class Narno_Gettext_Model_Translate extends Mage_Core_Model_Translate | |
| { | |
| [...] |
