Dan W. dnwade

tl;dr You should watch this.

It's interesting to me that a significant number of talks in this year's Strange Loop conference referenced a 1966 paper by Peter Landin called (somewhat tongue in cheek) "The Next 700 Programming Languages". In this paper, Landin describes a programming language which he says in a footnote might be aptly called "Church without the lambda" - but which in the paper is called "If You See What I Mean" (ISWIM).

Alvaro's talk delved deeply into the question of "What is the semantics or meaning of a program?" Alvaro's thesis is that the meaning of a program is to produce desired outcomes from a computing system but that current languages focus on

Descartes, Berkeley and Functional Reactive Programming

By @dmvaldman

Functional Reactive Programming (FRP) is generating buzz as an alternative to Object Oriented Programming (OOP) for certain use cases. However, an internet search quickly leads a curious and optimistic reader into the rabbit-hole of monads, functors, and other technical jargon. I’ve since emerged from this dark and lonely place with the realization that these words are mere implementation details, and that the core concepts are far more universal. In fact, the groundwork was laid down many centuries before the first computer, and has more to do with interpretations of reality, than structuring programs. Allow me to explain.

There’s an old thought experiment that goes like this:

When should you use DateTime and when should you use Time?

It's a common misconception that [William Shakespeare][1] and [Miguel de Cervantes][2] died on the same day in history - so much so that UNESCO named April 23 as [World Book Day because of this fact][3]. However because England hadn't yet adopted [Gregorian Calendar Reform][4] (and wouldn't until [1752][5]) their deaths are actually 10 days apart. Since Ruby's Time class implements a [proleptic Gregorian calendar][6] and has no concept of calendar reform then there's no way to express this. This is where DateTime steps in:

>> shakespeare = DateTime.iso8601('1616-04-23', Date::ENGLAND)
=> Tue, 23 Apr 1616 00:00:00 +0000
>> cervantes = DateTime.iso8601('1616-04-23', Date::ITALY)
=> Sat, 23 Apr 1616 00:00:00 +0000

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

	/*
	* Copyright Datalogics, Inc. 2015
	*/

	package pdfjt.cookbook.imaging;

	import java.awt.image.BufferedImage;
	import java.io.File;
	import java.net.URL;
	import java.util.Iterator;

	<powershell>
	write-output "Running User Data Script"
	write-host "(host) Running User Data Script"

	cmd.exe /c net user /add vagrant FooBar@123
	cmd.exe /c net localgroup administrators vagrant /add

	Set-ExecutionPolicy -ExecutionPolicy bypass -Force

	# RDP

	#!/usr/bin/env python3
	# -- coding: utf-8 --

	import uno
	from com.sun.star.beans import PropertyValue
	from pythonscript import ScriptContext
	import os
	import sys
	import time

	module DapperFSharp =
	open System.Data.SqlClient
	open System.Dynamic
	open System.Collections.Generic
	open Dapper

	let dapperQuery<'Result> (query:string) (connection:SqlConnection) =
	connection.Query<'Result>(query)

	let dapperParametrizedQuery<'Result> (query:string) (param:obj) (connection:SqlConnection) : 'Result seq =

	#!/usr/bin/env python3
	"""
	VIEW COMPLETE CODE AT
	=====================

	* https://github.com/six519/libreoffice_convert

	THANKS
	======

Dan W. dnwade

Descartes, Berkeley and Functional Reactive Programming

When should you use DateTime and when should you use Time?

Contents

Essential JavaScript Links