Skip to main content

The case against polycryo

When thinking about the polycryo vs tyvek argument most people reference these facts:

  • polycryo is the lightest
  • polycryo is the least expensive
  • polycryo is available everywhere
  • My favorite is polycryo rips/punctures easy and develops tear lines
  • Tyvek is heavier
  • Tyvek makes crinkly noises
  • Tyvek is not waterproof
  • Tyvek is available everywhere
While these checklists are mostly they miss the point:
  • polycryo is a vapor barrier and that's it
  • Tyvek offers some insulation even if it's just a little
  • Tyvek while not waterproof does have some limits
  • Tyvek comes in different weights for construction and kite making
  • Tyvek can be machine washed to soften the fabric
  • Tyvek is more robust and can be used to carry a load and maybe a person (survival mode who cares)
But for me the best reason for Tyvek is that living in Florida when it is humid most of the time I won't stick to it. And while it's mentioned here as a groundsheet it could also be used as a blanket or insulation in a hammock.
remnants - out of stock
What I like about the 2GoSystems remnants is that it makes a perfect groundsheet. It has all the insulation of the tyvek and adds a reflective coating. In a sudden rain shower it's a shelter, it's a groundsheet, or it's a blanket.


I like my Borah Bivy and my Snugpak Jungle Bag but there are hot and steamy Florida days when a net tent, tarp, and simple insulation is needed. You could even make a case for the 2Go bivy and an umbrella.


Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

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…