a better mousetrap #4: integrating on top of CouchDB

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.

Read morea better mousetrap #4: integrating on top of CouchDB

a clueless start to node.js

node.js is a technology that has been on my “to-try” stack of technologies for quite a while now. There has been quite some fuzz out there recently regarding this framework, and as so far I wanted to have a closer look on what’s possible in JavaScript outside the browser, anyway, it seemed a good reason for dealing with something “new” just for the sake of it, even without immediately having any meaningful use cases at hand… Read on. ­čÖé

Read morea clueless start to node.js

jython in webapps and better scripting support

For quite a while now we’ve been using Jython, a (re-)implementation of the Python programming language that runs on top of the Java VM and along the lines of JSR-223 (Scripting for the Java Platform), in our environment to deal with some use cases which addressed way easier using a scripting language than, in example, using Java code inside a webapp. However, so far our integration left a lot to be desired, so it was about time to get this things improved somehow.

Read morejython in webapps and better scripting support

Locked in?

Es d├╝rfte dem einen oder anderen nicht verborgen geblieben sein, da├č ich das Gros meiner Tage damit verbringe, Software in einer In-House – Umgebung gleicherma├čen zu betreiben, zu entwickeln und auch, irgendwie, in ihrer langfristigen Ausrichtung und Entwicklung zu planen. Ich bin seit ehedem Anh├Ąnger der Idee “Freier Software” (mit gro├čem “F”, wie in “Freie Rede”, nicht wie in “Freibier”…) oder, wenn pragmatischer, technischer, zumindest des Ansatzes von Open-Source-Software-Entwicklung, im Wesentlichen aus denselben Gr├╝nden (offener Umgang mit “gemeinschaftlichem” Wissen, Respektieren der Rechte und Interessen aller Beteiligten, L├Âsen von einem starren und meist falschen “Produzent”/”Konsument”-Verh├Ąltnis und so weiter und so fort). Im Alltag indes zeigt sich, bisweilen, da├č diese Frage zwar interessant und relevant ist, aber letztlich nicht weit genug springt, um gewisse Probleme zu l├Âsen, und auch nicht in jedem Fall allein geeignet ist, um “Lock-In”-Effekte, die ├╝berm├Ą├čige und faktisch nur extrem schwer l├Âsbare Bindung an bestimmte Produkte oder Hersteller, von vornherein zu minimieren.

Read moreLocked in?