Andreas Niedermair dittodhole

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

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

A good commit message looks like this:

Header line: explaining the commit in one line

Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc etc.

The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about

	namespace YourNamespace
	{
	/// <summary>
	/// Uses the Name value of the <see cref="ColumnAttribute"/> specified to determine
	/// the association between the name of the column in the query results and the member to
	/// which it will be extracted. If no column mapping is present all members are mapped as
	/// usual.
	/// </summary>
	/// <typeparam name="T">The type of the object that this association between the mapper applies to.</typeparam>
	public class ColumnAttributeTypeMapper<T> : FallbackTypeMapper

	using System;
	using System.Net.Sockets;
	using System.Net;
	using System.Text;
	using System.Threading;

	namespace UDPer
	{
	class UDPer
	{

	// select (LINQ Syntax)
	var regions =
	from r in Regions
	where r.RegionID > 0
	select r;
	regions.Dump();

	// insert
	Region newRegion = new Region(){
	RegionID = 99,

	<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
	<script type="text/javascript">
	$(function(){
	if (/iPhone\|iPod\|iPad/.test(navigator.userAgent))
	$('iframe').wrap(function(){
	var $this = $(this);
	return $('<div />').css({
	width: $this.attr('width'),
	height: $this.attr('height'),
	overflow: 'auto',

	Stuff this into your start method

	// Configure the Scheduler
	ISchedulerFactory schedFact = new StdSchedulerFactory();

	// get a scheduler
	IScheduler sched = schedFact.GetScheduler();
	sched.Start();

	Add to app config

	license: gpl-3.0
	redirect: https://beta.observablehq.com/@mbostock/d3-stacked-bar-chart

	internal static class NativeMethods
	{
	[DllImport("XpsPrint.dll", ExactSpelling = true, CharSet = CharSet.Unicode)]
	public static extern int StartXpsPrintJob(string printerName, string jobName, string outputFileName, IntPtr progressEvent, SafeWaitHandle completionEvent,
	[MarshalAs(UnmanagedType.LPArray)] byte[] printablePagesOn, int printablePagesOnCount, out IXpsPrintJob xpsPrintJob, out IXpsPrintJobStream documentStream, out IXpsPrintJobStream printTicketStream);
	}

	[ComImport, Guid("E974D26D-3D9B-4D47-88CC-3872F2DC3585"), ClassInterface(ClassInterfaceType.None)]
	internal class XpsOMObjectFactory
	{