EthanJJackson

Joined 11 years ago

Karma

39

Submissions

16

Member since

Aug 5

[ my public key: https://keybase.io/ejj; my proof: https://keybase.io/ejj/sigs/hFNbEOC8AqEF_blOuxugIDig-m13QG17XxM4g481_Jk ]

View on Hacker News

Recent submissions

Comment · 5 years ago

"It’s a no brainer that the search engine giant will be compelled to bring a similar anti-ad tracking feature on Android to keep the mobile ecosystem in sync."

Huh? Perhaps I'm missing something, why would Google do the same? Seems out of their interests ...

Why DevOps Should Be Responsible for Development Environments kelda.io

4 EthanJJackson 6 years ago 0 comments

How we cut our Docker push time by 90% kelda.io

2 EthanJJackson 6 years ago 0 comments

Using Data Containers to Boot Your Development Environment in Seconds kelda.io

2 EthanJJackson 6 years ago 0 comments

Comment · 6 years ago

Completely agree. In case it's helpful, we're working on a cloud dev environment for Docker that addresses the resource issues by running containers in the cloud instead of locally: http://kelda.io/blimp

Of course, if you can avoid docker for local development, that's definitely easiest in many cases.

Italian study funds 73.9% asymptomatic rate for those under 60 arxiv.org

6 EthanJJackson 6 years ago 3 comments

5 Common Mistakes When Writing Docker Compose kelda.io

1 EthanJJackson 6 years ago 0 comments

Comment · 6 years ago

I agree. I would never put data in a container in production, but for development purposes it can be helpful.

Show HN: Dksnap – Docker Snapshots for Dev and Test Data github.com

16 EthanJJackson 6 years ago 4 comments

Comment · 6 years ago

FWIW I think they definitely have a place going forward. But also don’t think the hype is helpful. It’s a big complicated change with goods and bads. Folks should know what they’re getting into.

The Dark Side of Microservices link.kelda.io

9 EthanJJackson 6 years ago 2 comments

Comment · 6 years ago

Ethan J. Jackson here, Founder/CEO of Kelda, and author of the post.

Thanks for the comment! You are, of course, right, once the initial OCR standard was developed, it acts as sort of a thin-waist under which tons of innovation in container runtimes are possible.

The main goal of the post was to provide a high-level overview for folks new to containers that need a beginning working model on what this stuff is all about. So I elected to omit this (and other) details in the hopes of being a bit easier to grok. But I think you’re right, I could definitely have clarified the point a bit more.

U.S. Revamps Process for H-1B Visa Application wsj.com

11 EthanJJackson 7 years ago 4 comments

Comment · 9 years ago

Already in progress =)

Comment · 9 years ago

I'm working on an approachable (i.e. easy to setup and manage) container orchestrator at http://quilt.io that may be worth checking out. It's still very early beta quality software, and some features are missing (notably bare-metal isn't there yet, but it's on the roadmap). That said, it's designed to solve precisely this problem -- ops shouldn't be this hard.