p8952

Asking end users of your product to report issues via DM'ing your personal Twitter account, an account which is full of retweets of homophobic garbage, is really REALLY bad.

Quietly editing your comment after being called out to hide it is even worse.

>You start with a background in English or professional writing and learn the technology, or you can start with a computer science degree or something similar and learn how to write.

Could you please recommend some good resources for learning to write, in the context of technical writing or more generally?

Seconded. I've never heard this in the UK from people of any age.

I wonder if it has anything to do with the way "an" sounds when spoken with an American accent. A mishearing and then repetition of "an accident" seems much more plausible to me than confusion with "on purpose".

> So you choose a template

"It's called The Grid. No templates, no coding."

Could you please elaborate on what parts of git-grep you find most useful?

I agree 100%. While the tech in Docker is great, it alone can't be easily monetized.

The real value comes from things like DockerHub, and getting people to buy into the whole ecosystem.

Looks good!

I'd marked 'docker pull' as out of scope because I thought it would be fairly hard to interface with their API from bash, looks like I was wrong.

Thank you.

One of the things I found really interesting here is how much could be done with just basic userland tools, and how old some of those tools are.

Docker was released in 2013, but support for kernel namespacing has been around since ~2007. That's quite a long time for such a great feature to go mainstream.

Thank you.

Interesting, it was my understanding that Docker was going in the other direction. Moving off AuFS towards Btrfs due to issues getting AuFS patches into the mainline kernel.

I'll have to look info CoreOS's reasons for going with Ext4.