Pythoneer

Actually I do only want to know about objects in my application, I don’t really need a relational database in the common sense below my application. It’s just one more level where data have to be mapped to something unnatural. So why should I not start looking a bit closer into real object storage, like db4objects does it. I will have to take the time, may be I can cut another unnecessary layer of complexity from my application.

The technology is always making us take a detour, simply because it is not really a human thing to use. How human is it to communicate with each other by converting our interaction signals (voice, gestures, …) into digital streams of multiple zeros and ones. This is so awkward and simply feels unnatural. The same applies to writing web applications.
First we are limited by the capabilities of the browser. Then we have to support all the browsers, that in turn again implement the same technology in different ways. Beyond the browser we have to communicate over a dumb protocol, which does not allow for real interaction and actually makes us covert our data in a way so that we can send them over the protocol. Next and probably the worst of all, is we are trying to use those data in a way that has a completely different way of modeling the data then the actual usage case does it. Wouldn’t it be ideal to auto-determine what and how to persist data, states and combinations of them by “scraping” the user interface that is created for the user? Why do we have to map the user interface first to some low-end technology, some markup, later convert it into data streams, use it with objects and finally persist it in a completely different final format, in a database. Oh man, this seems soo much overhead and error-prone. But I am getting too philosophical. Back to work …