Control

Frankly speaking, I don’t really understand the passion for the new Apple iPad (an " iPhone on steroids"?). It’s a beautiful-looking machine but it also jails its user in the “Apple ecosystem”. It’s just consumerism. Apple has a record of launching beautiful-looking devices and shiny products. In the beginning of the years 1980s, they popularized the computer mouse and the graphical user interfaces as we know them today. In the beginning, one would love the simplicity of use of Apple computers and software, especially compared to the MS-Windows or GNU/Linux versions at that time (I’m speaking of the years 1990s). The end-user was then at the center of the “computer experience”. But now, it seems the end-user becomes a (paying) consumer, nothing else. ...

In software development (as in many other fields, like paper or thesis writing ;-)), you often need a revision control software to effectively manage all the changes made to your source code (or sections and chapters). It’s even more important if you work with other people on the same files, on different versions of the same sources, with people in different locations and with different systems. The problem I currently try to solve (or, at least, try to bring a solution to) is the following … The system doesn’t initially use any revision control software. People are able to edit any file they want, one at a time (file locking which is very annoying). Basically, there is only one version of a file per project: the current one. If another project tries to merge the same file from another project, someone has to manually review all the lines in order to see what should remain and what should be left. In order to reach a previous version of a file, you have to manually remove lines marked with the patch reference at a specific location on some lines (it does work in some programming languages and not at all in all others). In fact, a rudimentary revision control system exists but it’s completely outside the development environment. When a file is modified, it’s name is entered in a “patch system” with the reason why it was modified (when you are lucky). If you forget to enter its name, the system can’t do anything for you (since it’s not aware of anything). ...

I don’t know how I stumble upon this report of a conference ( English translation) from Avi Alkalay but I liked 2 schemes he showed. In this first scheme (left), I like the way it reminds you that “Open” is not only about software, source code. But now that more and more people are aware of the benefits of Open Source software, it’s interesting to also stress the other sides of openness: open standards (like OpenDocument), open hardware, open architecture. In the second scheme (below) is about the trend from private control / closed access to public control / open access (apparently from Rebecca Henderson; it could be interesting to find this whole presentation from 2004). ...

Quuxlabs is releasing the alpha version of GeoPolis, a web service to gather and show the ongoing police control. More info can be found on the project website and on the Quuxlabs blog. I made some comments regarding the service accuracy, automation, security and independence but I’ll be glad to use the service once I’ll be able to drive again. Btw, in the same topic – watching the watchdogs, my map of cameras in Liege (see announcement and update) is now located on the CCLV website. The database management is also handed over to them. Moreover Christophe Cattelain is now systematically taking photos of those cameras in Liege and he publishes them on Flickr …