tkellogg

What?

Find all the servers I have running on my laptop. It just prints port, pid and the command that started it (from ps aux)

Why?

Why not?

No, Really...

idk i just have a lot of servers running on my laptop and i sometimes forget where/what each is

It works fine on Mac OS 14.2

tkellogg

#!/usr/local/bin/oil
# Re-create the current branch on top of "master" after pulling latest.
#
# Normal usage:
#   git rebranch
#
# On a branch other than master:
#   git rebranch prod-master
#
# Alternately, configure a default branch in the local repository:

tkellogg

~> scala
Welcome to Scala version 2.11.6 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_66).
Type in expressions to have them evaluated.
Type :help for more information.

scala> class Foo { lazy val bar = 2 }
defined class Foo

scala> :javap Foo
  Size 831 bytes

tkellogg

def mergeFields(vs1: List[JField], vs2: List[JField]): List[JField] = {
  def mergeRec(xleft: List[JField], yleft: List[JField]): List[JField] = xleft match {
    case Nil => yleft
    case (xn, xv) :: xs => yleft find (_._1 == xn) match {
      case Some(y @ (yn, yv)) =>
        JField(xn, merge(xv, yv)) :: mergeRec(xs, yleft filterNot (_ == y))
      case None => JField(xn, xv) :: mergeRec(xs, yleft)
    }
  }

tkellogg

Objectives

The objectives of CBOR, roughly in decreasing order of importance, are:

1. The representation must be able to unambiguously encode most common data formats used in Internet standards.
   • It must represent a reasonable set of basic data types and structures using binary encoding. "Reasonable" here is

tkellogg

A couple open source .NET projects have need for a headache-free storage option. [Jump-Location][1] is a command line tool that currently uses flat files to store information about what directories a user has visited. Flat files were great at first, but we need more. Also, PSReadLine is also running into similar problems.

Storage Engine

This will most likely wrap an existing storage engine to take care of the administrative tasks. We'll have to choose a storage engine that meets some basic requirements.

• Small size -- It will have to be packaged with other apps, especially commandline apps where there is an expectation of small size. The storage engine itself should probably be < 10MB.
• Easy to use -- Otherwise, what's the point of this project?

tkellogg

module Test.Main where

import Debug.Trace
import Data.Char
import Data.String

parse [] = []
-- Error: unexpected "'"
parse ('h':cs) = cs
parse (c:cs) = c:c:cs

tkellogg

Keybase proof

I hereby claim:

• I am tkellogg on github.
• I am kellogh (https://keybase.io/kellogh) on keybase.
• I have a public key whose fingerprint is 402D 2BD0 DEF8 57ED DFAA A221 A1B1 2838 7802 BD5E

To claim this, I am signing this object:

tkellogg

implicit class BecauseFsharp[T](obj: T) {
  /**
   * This comes from OCaml/F#; very handy when used with partial function
   * application. It's mainly useful for reducing parenthesis nesting.
   *
   * `foo(bar)` is same as `bar |> foo`
   */
  @inline def |>[U](function: T => U): U = function(obj)
}

tkellogg

As for statements equating MQTT with CoAP style REST and why they're not complete or true:

Statement 1

CoAP URI path == MQTT topic

This appears to be true because they have a lot in common. In reality an MQTT topic is ephemeral (or you could say it's just a convention). You don't create it, you don't delete it, you just use it to synchronize where you're publishing and where you're subscribing.

A CoAP URI is material. Or at least it is with Californium, and I believe it has to be this way as long as CoAP is used in conjunction with CoRE link formats because all resources have to be enumerated so they can be described by the CoRE document.