progrium's comments

Working with VMs always felt difficult because of this. So authoring was built-in to Docker. Now you can use Apptron to author and embed a Linux system on a web page. This aspect is usable, but it's only going to get better.

It's getting there. Among other things, it's probably the quickest way to author a Linux environment to embed on the web: https://www.youtube.com/watch?v=aGOHvWArOOE

Apptron uses v86 because its fast. Would love it for somebody to add 64-bit support to v86. However, Apptron is not tied to v86. We could add Bochs like c2w or even JSLinux for 64-bit, I just don't think it will be fast enough to be useful for most.

Apptron is built on Wanix, which is sort of like a Plan9-inspired ... micro hypervisor? Looking forward to a future where it ties different environments/OS's together. https://www.youtube.com/watch?v=kGBeT8lwbo0

Damn, who wrote this amazing piece of software

wow, thanks!

This is a good question that should be added in the readme. Would love an issue for it to also collect data

age old problem, i should definitely warn people about memory management implications. what would you put in the readme for this?

Awesome, can you throw into an issue?

I guess I will look into this as that really sounds like syntactic sugar for something more basic. Like using the class.

I have a hard time keeping up with their changes but you might be right: https://developer.apple.com/documentation/foundation/nsautor...

Oddly it says you cannot use them directly, but later implies maybe they are just less efficient. It would be nice if somebody made an issue for this.

I thought I wrapped NSAutoreleasePool but maybe I just used it directly dynamically. If something is not wrapped in the source that doesn't mean you can't use it. objc.Get("NSAutoreleasePool").Alloc().Init()

Unfortunately I can afford some leaks at the moment, so if that's critical to anybody else and I'm doing something wrong just submit a PR

sorry I meant memory management not garbage collection. again they're just convenience methods wrapping those exact methods on NSObject

also helped design docker (the good parts) and a bunch of other stuff

So, I wrote Dokku, helped design Docker, was co-architect of Flynn, and am now in R&D partnership with Deis. I also made Localtunnel, RequestBin, Hacker Dojo, etc etc if anybody is keeping track. I guess I'm not who this question was intended for, but I figured I'd share some context.

I can't speak as much to Flynn right now, but here is a fairly recent blog post about the current status of Dokku: http://progrium.com/blog/2014/10/28/deis-breathes-new-life-i...

tl;dr, after a long lull between 2013 and 2014, its activity has picked up and is slowly working towards a 1.0 including a major refactoring to address a lot of issues and bring it up to modern standards. In fact, here is our refactoring doc in progress: https://github.com/progrium/dokku/wiki/Refactoring

I feel the flaws of these projects quite deeply, especially Dokku. But I'm surprised to still run into so many people (just not as many here) that really love Dokku. Without them I would not be motivated to come back to it and make it what it should be.

Keep in mind Dokku was the first killer app for Docker and a lot of my design influence on Docker was to be able to easily make something like Dokku and eventually systems like Flynn, Deis, etc. But also so many other things...

I'm involved as an independent collaborator again in Docker's internal extension efforts, and after I saw this I got ClusterHQ looped in to that working group. Then we talked about collaborating on a Go port of Powerstrip, so I'm working on that here: https://github.com/ClusterHQ/powerstrip/tree/golang

We're also planning to combine the Docker event stream plugin system I prototyped previously into Powerstrip: https://github.com/progrium/docker-plugins

And ultimately, eventually, we'll have native extension support in Docker that allows much more extensibility, but all this is a good first step IMO.

Thank you!

Yeah, and actually, that bootstrapping was previously a manual process, but thanks to DigitalOcean I had my summer intern Robert (@robxu9) implement and submit the patch for -bootstrap-expect.

It originally had PATCH in the design. I think it was a limitation of our tooling that made us reconsider. And that PUT was slightly more familiar for novice users. At the end of the day ... it doesn't matter. Either way is a huge improvement from all GET.

You can generate personal OAuth tokens and let them use the API.

They should have took my naming suggestion and called it Jon Hamm.

Yeah, Flynn is open source so I can contribute as necessary, but Cupcake is continuing to maintain and build the project.

My specific long-term plan is still vague, but it will involve Flynn and so far I've been finding ways to fund my time to invest in some R&D type projects for the Flynn ecosystem.

DigitalOcean's plan is not set either, but my work there should involve Flynn and that ecosystem / architecture / worldview.