Hacker Newsnew | past | comments | ask | show | jobs | submit | chrisbuchholz's commentslogin

We are using docker for developing and testing services in the same environment they are put in production in: Debian.

My personal docker ID is chrisbuchholz.


Hey, I don't see you on the beta list as having signed up. You'll need to have signed up at https://beta.docker.com/ first.


Yeah, I dunno why I thought I was. I am now, though, so if you don't mind, please go ahead and fast-tract me through the waiting list :)


You've been approved. Check your email for the invite.


By whom?

Google gives me numerous books with that title.


Paulo Coelho, edited the post to include that.


But they will surely understand that if they're able to obtain and see your dick pics, they are also able to see all the other pictures your take and send via email and so forth.

Most people don't take dick pics, but almost everyone take photos of other occasions which they might not like others to see, like their children running naked in the garden, your wife sun bathing or just the random social occasion that are no others business but yours and whom ever you deliberately choose to share it with.


Which again buries the entire issue because if we're going to ask "who can see pictures you share with people without encryption" then the question goes a good deal further then "oh my god the government!"

Quite literally any sysadmin at your ISP can see that material, and might see that material in the course of normal work. If you posed this to an "average" person they also haven't realized this. They also don't realize Dropbox is unencrypted. Neither are your bank records - not from your banker or the random support person you're calling.

If we're on a role they might then be inclined to wonder why everyone in their life isn't constantly trying to blackmail them with all the information they could easily get all the time. And then eventually, we'd loop around to the obvious realization: because it would be illegal for them to actually use any of that information they obtained in confidence. And so on the vast vast scale of modern society, they don't.

At which point you have a problem: the NSA doesn't actually randomly start posting stuff it collects on the internet. In fact people barely know what it does because it doesn't impact them. Because government thugs aren't kicking down doors of political dissidents, or doing any of the "totalitarian" stuff they expect.

After this entire thought exercise, the average person might conclude they should stop emailing dick pics around if they don't want their ISP to see them. But then they'd also realize that's probably nothing to worry about from the NSA either. And by and large, they'd be right.


> They also don't realize Dropbox is unencrypted.

This set off my alarm bells at the broad statement - I checked, and Dropbox is encrypted, in that any uploads to and from the server are via SSL. This is probably 80 of what anyone cares about.

It's like saying your online banking isn't encrypted because the bank can still read your balance.


No, Dropbox is not encrypted on the server, which is the point the parent was trying to make. Theoretically, any Dropbox employee can look at any unencrypted dick pics that you decided to store on their servers, much like how your ISP can see any of your unencrypted web browsing.


I feel you misunderstood the article.

To my understanding, his point is that we need database persistence, automated RESTful APIs, triggers and responses and better ways to do UI layout, but what we got was Swift which doesn't address any of these things. The things we actually need.

So we end up with a new language which we have to spend time mastering, and when we are done doing that, we still need to fix those problems we had before we got Swift, so what is the point? Why do we need Swift?

That's how I read the article anyways.


That makes it sound as if a modern language sans the baggage of C was not needed. It was.


Hmmm...to me it makes it sound like a modern language without the baggage of C was and is needed, but Swift is not that language.


[language] does not solve [problems not solved by languages].

Film at 11.


Welcome to Tautology Club! If Tautology Club is the sort of thing you like, you will like Tautology Club. Alternatively, you will find that you like Tautology Club if that is the sort of thing you like.

In other news, you might have checked some of the other posts here that explain why some of these problems are, or at the very least can be language problems, before letting loose the snark.

For example https://news.ycombinator.com/item?id=8377860


"My smartphone didn't palliate my hemmoroids" is no tautology.


But "[language does not solve] [problems not solved by languages]" is.


Your opinion fails to shorten my daily commute – which is the truly pressing concern.


Your example is a link to yourself and two footnotes that link to articles written by yourself. Are you a joker?


I have not, no. Never heard about before now.

Do you have experience with it?


I saw it on Dan Gillmor's site, http://dangillmor.com/2014/09/16/a-return-to-hong-kong/

Related effort for students: http://www.wired.com/2014/09/known/



What I am afraid of is to become crippled by moving around too much, never mastering a single tool. I switch between different languages multiple times a week, but I guess if the features a certain editor/IDE adds are so great, they might add more than me knowing everything about it would.


IMHO the reason not to worry about being crippled by moving around too much is that this is about completing the task. In most cases they will add more, and to top it all off, if you learn a few key "most useful" shortcuts/features of the IDEs you end up using, then you strike what I call an acceptable middle ground.


Sometimes it is, on my job it is. At home it's more about having fun - seing the code compile/run, but just as much writing and reading the code.


Exactly what I am starting to think. I guess Vim has been clouding my mind.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: