I've made money on my ISOs at every startup I was an early employee of. The secondary markets are fairly liquid if you know how to navigate them. None of the companies were in the Bay Area either.
You mentioned that you would write about how SV is different than what's happening at the seed stage everywhere else. What's the tl;dr of that upcoming post?
They are actually very public about the fact they are not a machine learning company and are more or less opposed to machine learning. Their goal has always been to wrangle data and make it useful to human decision makers. not automate decision making.
I think you're under estimating the number of people required to run your own infrastructure. You need people who can configure networking gear, people swapping out failed NICs/Drives at the datacenter, someone managing vendor relationships, and people doing capacity planning.
I think you could probably get the IO performance you're talking about in your blog post from AWS instances or Google Cloud's local NVMe drives, but if you truly need baremetal, I'd recommend Packet or Softlayer. Don't try to run your own infrastructure or in a year you'll be: https://imgflip.com/i/1fs7it
Nice project! The callbacks on event listeners reminds me a lot of javascript and can get messy. Go handles this with channels. Why did you decide not to use channels to emit events?
The squashed commits is pretty awesome. Here's what someone on our team found about the performance based against `docker pull` on quay using the same images for various scenarios:
Okay I was testing this squash pulling method, and here's the performance results I found.
Below, the tag only has VIM installed, the update installs Emacs.
First column is docker pull the next is the squash pull.
Latest pull w/o Ubuntu base downloaded: 38.1s | 19.4s
Latest pull w/ Ubuntu base downloaded: 32.8s | 18.8s
Tag pull w/o Latest downloaded: 38.3s | 21.4s
Tag pull w/ Latest downloaded: 5.7s | 20.8s
Tag pull(up to date): 2.2s | 20.1s
Tag pull(updated commit, old tag downloaded): 13s | 34.2s
Of course these values all depend on the things being installed but time differences for the tag pulls make this seem bad because it always has to download the entire commit tree.
