hippiefahrzeug

this is absolutely amazing!

you may also like:

- axess: https://www.discogs.com/Axess-Chamaeleon/release/544829 https://www.youtube.com/watch?v=qkcvDi_J-Ks

- Danger in Dream: https://www.discogs.com/Danger-In-Dream-Entrance/release/555... https://www.youtube.com/watch?v=7qHqMh2pono

- Christopher Franke did some great solo stuff after his time at TD.

great tip, thanks!

There really isn't such a restriction.

I sometimes need containers with several services, and that's perfectly fine if it makes the setup simpler. Services can be dynamically enabled/disabled for instance with daemontools. As a matter of fact, docker brought new life to djb's daemontools for me. This makes it possible to conditionally add even an sshd to my containers (just by mixing in a directory with the run configuration), so I can go into them and check what's going wrong.

And when things need to be hardened up, just drop the corresponding service directory.

This 'an average 4 year old can use an iPhone better...' makes me cringe every time I hear it, especially when it comes from proud parents who think their offspring is a genius. The geniuses here are the engineers who made the device usable by the 4 year old, not the other way around.

As many others have mentioned, the secret sauce is probably quite simply this: No ads, no trackers, no js libraries. I use Firefox with the 'disconnect' plugin. On HN, disconnect stays completely inactive, nothing to be blocked, just good old html to be rendered with a sprinkle of css. It's beautiful, it's the way it should be.

thanks for this. I always have to hold myself back when one of the worst language features is being seen as something positive. Now I feel I don't have to rant.

good one. it's what one famous blogger calls the 'elop effect': http://communities-dominate.blogs.com/brands/2011/08/coining...

This reminded me of an article I've read a long time ago which had a really strong impact on me. I've just found it by googling a couple of words that were still in my head after all these years.

Here it is (probably not where I originally read it): http://www.nbcnews.com/id/21643646/ns/health-behavior/t/what...

I've followed a policy of using djb's software whenever possible over the years. Unfortunately qmail shows its age and may no longer be a good choice these days, but then again, who runs their own email server? :)

daemontools and ucspi-tcp are still some of the best tools to dig into. I love multilog (part of daemontools) which solves problems I didn't even know exist. e.g. I had a pool of servers and wanted to collect all the logs in one place... the way multilog names files makes this a simple rsync task, and you can just concatenate and sort, it even works for multi-lined output.

Since I started using docker, djb's tools got a new life for me. I manage all services within docker containers with daemontools.

I'm not sure what you mean by the last sentence. That wasn't entertainment. That was an ultra handy feature which I miss to this day. You could have several fullscreen applications, switch between them easily or just have a peek onto what's going on by dragging the screen down a little bit. It's like a tiled desktop on steroids. Amiga's Multitasking was great (considering the resources).

There are two ways:

1. You run the db and its files inside a container and regularly export a DB dump like so (example for postgres):

docker run --volumes-from db -v $(pwd):/backup ubuntu:trusty sh -c "cd /var/lib && tar zcvf /backup/backup.tgz postgresql"

(I don't recommend this)

2. You run the db inside a docker container and mount a volume for /var/lib/postgresql into docker. This I find is the best way. the db files remain on your host and you can easily maintain the DB (runtime) and files separately.

Adjust to whatever DB you're using.

I'm not sure why I need to tell you all this. :) I was replying to "What are some problems that get solved better when using Docker?".

We have many images, and we build them in a CI setup using jenkins. I used to run jenkins inside docker and build images within that docker, but this turned out to be a problem. (Mainly more and more resources were used up until the disk was full.) Now it's just jenkins installed on the host building images, starting them and run integration tests.

One thing I'd like to point out are OS upgrades, security patches or generally package updates. With docker I just rebuild a new image using the latest ubuntu image (they are updated very frequently), deploy the app, test and then push the new image to production. Upgrading the host OS also is much less of a problem because far fewer packages are installed (i.e. it's just docker and the base install).

While I can't speak for someone else, I find myself in the same place: I have 16GB in my mid 2010 MacBook and it's not enough when you develop with Xcode (incrementally eats memory up to and over 1GB), have an IntelliJ (~1.5GB) up while having one or two ubuntu VMs running (each 4 GB). Add to that the fact that Chrome eats a terrible amount of memory and all these developer tools running at the same time (kaleidoscope, sourcetree, db browser, xemacs, sublimetext, etc) have their demands as well, and I find myself running out of memory all the time. Fast paging doesn't do the trick.

What is the actual advantage of AppCode these days? (Just purely from a user experience point of view.) When I tried it a hile back it kept switching back to XCode for UI Changes, and since the editor for obj-c didn't seem that much better than XCode (and also somewhat more sluggish), I just stopped going back to AppCode after one of these many times it sent me to XCode.

For the record: I love the other Jetbrain IDEs (i.e. RubyMine and Intellij)

Sorry, but that's just mindboggingly stupid. They could have done something (slightly) more interesting, e.g. xyz.shouldIlearnIt.com and replace the xyz in the answers by whatever the string in the hostname was.

As it stands, this unjustified hate in a particular technology comes across as childish.

I appreciate your engagement in this discussion, but you can't be serious now: Of course the iPhone was a game changer, but that doesn't reset everything to 0. Nokia's brand recognition, Nokia's relationships with telcos and their vast distribution channels... these things don't go flying out of the window just because of the iPhone, and it certainly wasn't a disadvantage.

As for Nokia killing Symbian: To publicly announce a year before you actually ship the next product, that your current products are now obsolete - huge mistake! I don't think there is any dispute on this.

But we digress: I strongly believe that if you do it right there is money to be made as an Android vendor (don't forget those emerging companies from China, Huawei, xiaomi,...), but there is no money in WP. Nokia did a brilliant job with their Lumias, but they just won't sell without the right OS.

Nokia was massively larger than Motorola. (Look at historical market cap data. In year 2000: Nokia > $200B vs Motorola ~$80B).

Nokia was the market leader in smartphones before they went WP. They were larger than Apple and Samsung combined and then some more. Motorola wasn't a big factor in the smartphone business. Google bought them for their patents, certainly not for their mismanaged smartphone strategy. So, Motorola went from 0% smartphone market share to roughly 3% with Android. (Nothing to write home about, but you can't blame this on Android.)

Nokia on the other side was at 34% when they decided to go all in on WP, and look where they are now: 3%. Nokia's fall is of historic proportions. Motorola's fall doesn't even come close.

Remind me: which company has just been sold for peanuts after trying the WP strategy?

People want smartphones. WP phones are the cheapest entry level smart phones (such as Nokia 510, 520, 610, 620) they can afford in eastern europe.

You see WP devices 'a lot' (that is: you get to see them once in a while) over there, but these are mostly owned by people who wanted some sort of smartphone. Also a lot of them are quite annoyed that there are no apps.

I think Elop's greatest achievement is to sell people the "There is no money in being an Android vendor"-lie. And people are actually buying it.

WP market is much much smaller, so, by becoming a big player in this market, which Nokia achieved in very little time, they became in fact a big player in a market where there really is no money.

Had they instead of this focused on becoming a big player in a market that actually matters, e.g. the Android market, then Nokia may still (or again) be worth a lot. (But then they wouldn't be a cheap take-over target for Microsoft.)

With Nokias connection to telcoms, they could have easily achieved a big chunk of the android market share.

I just couldn't read past the "who're"...

regarding smoothness: any phone in the show room will feel smooth. that's really no achievement. how does it feel after heavy use, lots of data and apps installed? (of course, the latter won't be causing a problem on wp)

Well let's see: Nokia instead choose to go into the WP market which back then was lingering at around 4% market share, and managed to get 70% of all WP sales which still is at merely 6% market share (while competing with samsung, htc, lg, etc.). Congrats, well done!

Imagine if instead they went for android, and took that 70% market share in the Android space? It was possible for them to do in the WP space, why should it not have been possible in the Android space?

As I see it, they wasted their engineering abilities to gain a big chunk of an unimportant market, rather than shooting for the big fish, because their idiotic CEO puts Microsoft's interests before Nokia's.

I've never seen a business person use a WP phone. Never. And I do get to talk to quite a lot of them. It's iOS most of the time with very few Androids. WP is simply not a factor. There are markets/territories where WP is doing quite well, especially in low income countries because you get them quite cheap. But when I say 'doing quite well', I mean: You actually get to see them in 1 out of 10 phones.