Well, what do you know: The GNOME Unix desktop project is about to celebrate its 18th ‘birthday’, anniversary, … by tomorrow, August 15, 2015. I guess there’s more interesting news these days, and I also just noticed while incidentially stumbling across the GNOME web site earlier this morning…
Zweieinhalb Jahrzehnte… Eine der großen runden Zahlen, die das ganze Jahr schon dominiert. Und dazu Bilder, Momentaufnahmen, Videos. Kerzen und Menschen auf der Straße. Ein überfüllter Botschaftsgarten. Züge von Prag über Dresden gen Westen. Menschen, die auf der Mauer tanzen und dies Wochen zuvor vermutlich noch nicht zu ahnen gewagt hätten. Vermutlich sind wir, die wir zwischen Mitte und Ende der 1970er in der DDR geboren sind, eine Art Brückengeneration im Blick auf die Umbrüche des Jahres 1989: Wir sind alt genug, um noch vage zu wissen, wie es sich anfühlt, aufzuwachsen zwischen zwei Systemen, die sich unversöhnlich gegenüberstehen in einer scharf geteilten Welt, auf einem scharf geteilten Kontinent, in einem Land unmittelbar an dieser Teilung, an einer harten, gnadenlosen, militarisierten, eigentlich unüberwindbaren Grenze. Wir sind alt genug, um aus der Schule noch dunkel Begriffe und Denkmuster aus dieser Zeit einordnen zu können. Aber wir sind auch jung genug, um damals, im Herbst 1989, nahezu alle relevanten Entscheidungen im Leben – Schule, Ausbildung, Lebensentwurf, Liebe – noch fast komplett vor uns zu haben. Wir sind jung genug, um bis dahin noch nicht wirklich richtig in Konflikt mit dem herrschenden System gekommen zu sein, um Einschränkungen wie Reise-, Meinungs- und Pressefreiheit wirklich als ernstlich und schwerwiegend wahrgenommen zu haben. Wir wurden in gewisser Weise “frei”, von einen Tag auf den anderen, vermutlich ohne zuvor wirklich viel Unfreiheit empfunden zu haben…
Last week, the Java part of our system went productive after a major runtime update – and it did so not on top of the Glassfish application server we’ve been using so far but rather re-structured into multiple modules embedding a current version of Eclipse Jetty. This is a fairly large change and quite a step, still sort of a work in progress and, after all, once again something worth writing a bit more about…
So, here it is. After being highly anticipated for quite a while, the instagram folks a few days ago finally launched an Android version of their imaging / photosharing app so far only available for Apples iOS platform. As I am pretty much into using my Android phone for imaging, too, I couldn’t help having a look.
And, to cut things short and starting out conclusion first: Though Instagram (on Android) is nice, I so far failed to completely get what its “sweet spot” is all about. I am not completely sure why, but possibly, in the end, this is also caused by false expectations caused by seeing Instagram images floating around for quite a while yet never having worked with the tool so far, at all. So, just to pin down a few points:
- First and foremost, my major misconception about this was that Instagram mainly is a camera / imaging app backed by a small photosharing site. After my first test-driving the platform, including posting few pictures, I came to the conclusion that it actually is exactly vice-versa: It’s a photosharing network accessible via a smartphone app that provides camera and some basic imaging functionalities as well. Generally, there is nothing wrong with that. It’s just that I had something completely different in mind. So, by now, Instagram is not likely to have to compete with Autodesks Pixlr-O-Matic (my #1 imaging app on Android ever since), Magix’ Camera MX, smaller apps like FxCamera or LittlePhoto or paid ones like Vignette. No, it rather is likely to compete with the photo capturing and sharing facilities provided by apps like the official Twitter app, Snapbucket and, most specifically, Flickr. As stated, this is anything but bad, but of course it needs a bit reconsidering what use to make of it.
- Especially comparing to the official Flickr application, I am a bit surprised: Though not offering magnitudes of additional features, the Instagram app is in any possible way bulkier, heavier than the Flickr one: Download of the Instagram app is at least four times the size of the Flickr one. Other than while using the Flickr app, Instagram seems to seriously eat system resources on my phone, and, by now, it also happens to be the first imaging app I ever used that made it into the percentual battery consumption statistics so indeed it seems a wholly different kind of beast on the phone. So far I blame this to being the very first version they do for Android, so maybe this is likely to change in the future.
- With focussing on providing a social network backing the imaging stuff, it didn’t take me long to stumble across pages like this: “iPhone fanbois enraged by Instagram’s Android triumph”, which leaves me with a rather bad feeling about Instagram. So, is it actually Android folks now about to invade some sort of “elite” social network so far exclusively limited to iOS users? Well, I am sure by now there will be a wholly new load of users in and on Instagram, and so will be a whole new load of photos – some will be crap, some will be “good” in whichever way you might want to put it. But having all this tied to a special kind of device seems pointless, and from this point of view, I am glad to actually see there is an Android app. Which still, however, makes Instagram lag behind Flickr or the image sharing stuff in G+ or Twitter a bit (because in all of these platforms I am able to manage my timeline, pictures and all that using an ordinary desktop web browser, too, which is something Instagram either seems to missing or seems not to be all about, after all).
- In some ways, I am a bit reluctant to having even another social network. I mean, after all, what about it? I’m on twitter, I am in G+, I do have accounts in most of the social networks you might imagine (yes, including tumblr), and by now once in a while I see all these networks sort of “partitioning the WWW” into a bunch of more or less disjoint subsystems, knowing that users in one of these networks do have difficulties communicating with users in other networks without too much effort. Sure, I can cross-post from tumblr to twitter, from Instagram to twitter, from Flickr to twitter and all that, but in the end, in most of these situations it’s “monodirectional”, as feedback (if any) ain’t posted back to where the content came. Using Instagram is likely to add even another “insulated” world with rules of its own.
So, ultimately, I think the Instagram folks technically have done a decent job providing the first version for Android, and I am glad they did. As far as I am concerned, I possibly just have to find a meaningful thing to do with Instagram, or eventually consider that staying out of this also might be a valid option (same as I stepped out of other platforms, like Path, for the same reason). We’ll see.
I’ve recently been writing about Apache CouchDB and its various features of interest in our environment, and I will continue doing so as, after working with this platform, I came across a bunch of thoughts I quickly felt like pinning down, either in order to remember them, or in order to eventually have some discussion on that topic as I still consider myself learner as far as both CouchDB and architecture on top of CouchDB is concerned.