Eric Richards ericrrichards

At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.

What killed Haskell, could kill Rust, too

What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.

Is Haskell dead?

If you enjoyed reading this, I'm intending to do more blogging like this over here: https://cdgd.tech

This is not a complaint about Webpack or v4 in any way. This is just a record of my process trying it out so I could provide feedback to the webpack team

Hmm... I don't see any docs for 4.0 on https://webpack.js.org. I guess I'll just wing it. All I need to do is npm i -D webpack@next, right?

+ webpack@4.0.0-beta.2

On the cost of being lazy

Full source code can be found here

Changelog

2017-01-04
New performance test - Paul Westcott (@manofstick) provided his implementation of Lazy semantics (called Lazzzy) which I included in the graphs. This implementation is intended to be equivalent to Lazy<'T> in .NET with regards to functionality.
2017-01-17
New performance test - is working on a PR for .NET Core. I wanted to include performance numbers for the updated Lazy<'T> class.

	// ==UserScript==
	// @name Kindle Download
	// @namespace http://tampermonkey.net/
	// @version 2025-02-20
	// @description Download all your kindle books
	// @author You
	// @match https://www.amazon.com/hz/mycd/digital-console/contentlist/booksPurchases/*
	// @icon https://www.google.com/s2/favicons?sz=64&domain=amazon.com
	// @grant none
	// ==/UserScript==

	<#
	.SYNOPSIS
	Gets focused Az log information on resources. Helpful to determine who created what.

	.DESCRIPTION
	Providing only the ResourceGroupName will retrive logs for all items in that resource group. You can additionall filter the operations. If you also provide the resource name and type then only logs for that single items will be retrieved

	.PARAMETER ResourceGroupName
	Specifies the name of the resource group.

	i
	me
	my
	myself
	we
	our
	ours
	ourselves
	you
	your