Skip to main content


I classify BSD and Apache as MIT licenses. They just don't care what you do with thrie code. I think there is some attribution that is required but that's it. And in this post I'm going to take a birds eye view of MIT and GPL.

I'll start by saying that I do not like any of the GPL licenses and for the most part it just not matter why although when you compare the different licenses only the GPL expects me to actively do something when consuming GPL'd source which goes beyond simple attribution.

So far as I can tell the MIT license only requires attribution.

If you ask me to choose between the two I will always choose the MIT version. Both as a consumer and as a publisher. Sure I'd like to get credit for my code. Sure I'd like to get paid if something I did was the root of some else's billion dollar enterprise. And for that matter I have no idea why RHS is so hell bent on the GPL other than he is simply so invested in it.

If you're a good programmer and you release good software someone will take notice and you'll get a killer job. And if you write mediocre software it may not mean anything at all and may be how you interview or what you really know.

There was a case where Linksys was taken to court because they violated the GPL. The lawyers got rich whether it was from the plaintiff or from donations. You certainly never hear of Microsoft or Google suing for appropriating some GPL code. It's bad press. It's bad business. It's just bad!

So when you GPL your thirteen lines of shell script you'll have to ignore my snickering.

One more thing. The MIT licenses is one paragraph.  There are 3 versions of the BSD; 1, 2 and 3 paragraphs. They require someone with common sense. The GPL requires a team of lawyers. In fact I do not know any enterprise business that does not have a team of lawyers strictly to comprehend the GPL.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…