If that’s the case, then it really doesn’t matter what we think about Chrome removing visible URLs. What appears to be a design decision about the user interface is in fact a manifestation of a much deeper vision. It’s a vision of a future where people can have everything their heart desires without having to expend needless thought. It’s a bright future filled with seamless experiences. Welcome aboard The Axiom.
I love this post. It’s not only about why Google Chrome might have removed the URL from the browser UI but also more in general what it might mean if the “seamlessness” is overdone. Spoiler: You might have already seen it.
For over a year this blog has been powered by Octopress 2. I learnt a lot about Jekyll and Octopress in the meanwhile and tweaked my system on various occasions. And I still love the system and the ideas behind it. So today I rebuilt my blog with Octopress 3.
It wasn’t an upgrade in the common way. Octopress is no more a full-fledged wrapper around Jekyll but has been split into various components that can be hooked into a Jekyll installation. Have a look at their github profile: there now is octopress, ink, deploy, code-hightlighter and some more.
It is not yet officially released (as of now it’s release candidate 8) – probably also because large parts of the documentation are still missing. So it took me quite some time to get it all up and running, and I’ve likely not yet discovered it’s full potential. Once the documentation and some more explanations are public, I’m happy to write a more extended post on how to use it.
If you encounter any problems with this site be sure to let me know.
For the vast bulk of stuff that most people will want to do on a computer, though, most of the time you don’t need a desktop monster. I don’t think you even need a 15” screen, which is essentially a portable desktop. You just have to use a small screen productively. Matt Gemmel
Ever since I moved to Aarhus four months ago I have been limited to the 13 inch display of my (non-retina) MacBook Pro. Beforehand I thought it would be quite annoying to be limited to this small screen (I have an external 27 inch monitor at home in Munich).
But as Matt writes, it’s mostly a question of what you make of it, and I didn’t miss a bigger display as much as I anticipated. But my workflows changed quite a bit: I run a lot more applications in Fullscreen mode and use on quite a few helper tools to coordinate stuff and switch between programms. Here a short list:
- First off: Alfred for launching apps and invoking various workflows.
- Better Touch Tool enables the Windows-7-style window snapping on my Mac.
- A combination of KeyRemap4MacBook and NoEjectDelay enabled the use of the eject-key (I replaced the optical drive w/ a second HDD some time ago) as an hotkey for iTerm21.
- Furthermore I use HyperSwitch as a finer enhancement for the system application switcher.
Still higher resolutions are always tempting. Especially when dealing with visual stuff, no matter if Lightroom, Pixelmator or just the iOS Simulator, more screen estate equals more productivity in my opinion. For that reason I keep checking out the 13 inch Retina MacBook Pros and I also have high hopes for the rumored 12’’ Retina Air.
Almost two weeks ago I moved from Munich to Århus, Denmark, in order to spend an Erasmus semester here. It’s going to be my last semester as a media informatics student so I want to get as much out of it as possible. These are my first impressions after two weeks in Denmark.
Yesterday I attended the first ever border:none conference in Nuremberg, a conference focused on the mobile we. I really enjoyed the day there and am still have to wrap my head around all the things I learned there. The talks spread over technical and conceptual topics around the web (not only the “mobile” one) and I came home with a long list of things to think about and to try out. Let me try to summarize the talks a bit.