Karthik Krishnamurthy kkrs

API	Status Codes
[Twitter][tw]	200, 304, 400, 401, 403, 404, 406, 410, 420, 422, 429, 500, 502, 503, 504
[Stripe][stripe]	200, 400, 401, 402, 404, 429, 500, 502, 503, 504
[Github][gh]	200, 400, 422, 301, 302, 304, 307, 401, 403
[Pagerduty][pd]	200, 201, 204, 400, 401, 403, 404, 408, 500
[NewRelic Plugins][nr]	200, 400, 403, 404, 405, 413, 500, 502, 503, 503
[Etsy][etsy]	200, 201, 400, 403, 404, 500, 503
[Dropbox][db]	200, 400, 401, 403, 404, 405, 429, 503, 507

Should be work with 0.18

Destructuring(or pattern matching) is a way used to extract data from a data structure(tuple, list, record) that mirros the construction. Compare to other languages, Elm support much less destructuring but let's see what it got !

Tuple

myTuple = ("A", "B", "C")
myNestedTuple = ("A", "B", "C", ("X", "Y", "Z"))

Applied Functional Programming with Scala - Notes

1. Mastering Functions

A function is a mapping from one set, called a domain, to another set, called the codomain. A function associates every element in the domain with exactly one element in the codomain. In Scala, both domain and codomain are types.

val square : Int => Int = x => x * x

Laws

A law is a group of two or more expressions which are required to be the same. The expressions will usually involve one or more typed holes ("inputs") which vary.

Some examples:

x.map(id) === x

Thread Pools

Thread pools on the JVM should usually be divided into the following three categories:

CPU-bound
Blocking IO
Non-blocking IO polling

Each of these categories has a different optimal configuration and usage pattern.

Overly aggressive CFS

We're looking at CPU bandwidth control via CFS:

https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt

Reproduction program

Program does number of iterations, in each iteration we burn CPU in small chunks until we get 5ms of real time spent. On each iteration we also print how much

The Elm Architecture is the wrong abstraction for the web

In this article, I'd like to explain why I think The Elm Architecture is fine for small components, but quite harmful for websites based on pages.

Definition and Pros/Cons

First, let's clarify what I mean by "The Elm Architecture".

The Elm Architecture's webpage describes it pretty well.

	package utils

	import java.nio.ByteBuffer

	import cats.data.Xor
	import io.circe.Json
	import play.api.http.LazyHttpErrorHandler
	import play.api.http.Status._
	import play.api.libs.iteratee.{Iteratee, Traversable}
	import play.api.mvc.BodyParsers.parse._

	package se.kth.edx.id2203.core

	import java.net.{ InetAddress, InetSocketAddress }

	import se.kth.edx.id2203.core.ExercisePrimitives.PerfectP2PLink._
	import se.kth.edx.id2203.core.Ports._
	import se.sics.kompics.{ Init, KompicsEvent }
	import se.sics.kompics.network.{ Address, Network, Transport }
	import se.sics.kompics.sl.{ ComponentDefinition, _ }

	package controllers

	import java.io.File
	import javax.inject.Inject

	import play.api.Logger
	import play.Environment
	import play.api.mvc.{Action, AnyContent}
	import play.mvc.Controller