Technically you could cut it to length, and reconnect wires by soldering them together. Then cover up the patch with white shrink wrap tubing. It probably wouldn't look "that" bad.
This article is not saying to run your editor inside of a docker container. If you view the link, it is a list of plugins to enable syntax highlighting for Dockerfiles within your favorite editor. I'm going to assume you didn't even click the link before responding to this post.
Just finished reading Tribal Leadership. Opened my eyes to things I had not realized before about life in general and working with teams. I would highly recommend it if you have not read it yet.
This site is very difficult to read on a mobile phone. The header sticks to the top of screen and never goes away, even after scrolling. It takes up at least half my screen.
I use to be in the same boat as you. Even though Google technically owns Waze, and some 'waze' reports show up on Google Maps, Waze is still superior. The main things I like about Waze that GMaps does not have:
* Voice notifications when objects are in road ahead
* Voice notifications when red light camera has been reported ahead
* Voice notifications when police have been reported ahead
Those are the 3 main things I like, though there are other features that Waze have and GMaps does not. The 3 things only work if people have actually reported them, so you'd need to be in an area where waze is used heavily (i'm in SF and it works great).
Docker is similar to a VM, only without all the excess overhead. That very same docker container, could be deployed to production, assuring that your production and dev environments are identical(same web server, same db version, etc). A docker container can be spun up in a matter of seconds on a linux machine. If you're using OS X, it will require a VM to run docker images(see boot2docker), but even with this, it's very low overhead.
To be honest, i've used Docker much more than Heroku so I may be biased. But a quick google search turned up this article, which I think explains the differences well: http://tuhrig.de/docker-vs-heroku/
This may be nit picky, but, when I change pages, it causes the browser to reload and move to top of page. This happens each time I click the next page button. This is very confusing. It'd be nice if the page did not reload, and instead fetched the new results via an ajax call, then updated the view with new results. This should not be difficult.
I'd be interested to see what everyone else has to say. But from my point of view, CLI will always be more efficient. Anything on top of that will only make accomplishing the task slower. Why would I use a GUI when I can automate the task with a script?
It depends on the user, but I find myself with multiple terminal windows open at a time throughout the day. Anytime I get stuck in a GUI app, I feel like I am wasting time.