|start | find | index | login or register | edit|
by earl, 5759 days agoHerr Pavlu feiert indem er JVM Class Files analysiert und produziert dabei gleich hoechst interessantes.
Nomic: "If law-making is a game, then it is a game in which changing the rules is a move. Law-making is more than changing the rules of law-making, of course, and more than a game. But a real game may model the self-amending character of the legal system and leave the rest out. While self-amendment appears to be an esoteric feature of law, capturing it in a game creates a remarkably complete microcosm of a functional legal system."
Nomic is published as Appendix 3 in Suber's book "The Paradox of Self-Amendment: A Study of Law, Logic, Omnipotence, and Change", which illustrates a (at least philosophically) very interesting aspect of legal systems (I'm inclined to say "a cybernetic aspect", but then ...).
In widely discussed news, Six Apart released Movable Type 3.0 with a major change in licensing terms. Those changes resulted in a loud (and foreseeable, imho) outcry of Movable Type's user community. Mark Pilgrim, certainly one of the top high-profile Movable Type users, switched to WordPress and wrote a piece as part of the switching in which he comments Six Apart's move and passionately argues pro Free Software:
"Freedom 0 is the freedom to run the program, for any purpose. WordPress gives me that freedom; Movable Type does not. It never really did, but it was free enough so we all looked the other way, myself included. But Movable Type 3.0 changes the rules, and prices me right out of the market. I do not have the freedom to run the program for any purpose; I only have the limited set of freedoms that Six Apart chooses to bestow upon me, and every new version seems to bestow fewer and fewer freedoms. With Movable Type 2.6, I was allowed to run 11 sites. In 3.0, that right will cost me $535.
I totally agree. Still, making money for a living in a free software environment becomes a more important issue to our industry by every day.
Gavin King on EJB 3.0: "EJB 3.0 adopted a POJO-based entity bean programming model, very much similar to what we use in Hibernate. Entity beans may be serializable. They will not need to extend or implement any interfaces from javax.ejb. They will be concrete classes, with JavaBeans-style property accessors. Associations will be of type Set or Collection and always bidirectional, but 'un-managed'."
"We propose to change the semantics of object-oriented dispatch, such that all calls to "open" methods are dispatched dynamically as usual,but calls to "non-open" methods are dispatched statically if called on the current object this, but dynamically if called on any other object. By specifying a method as open,a developer is promising that future versions of the class will make internal calls to that method in exactly the same way as the current implementation. Because internal calls to non-open methods are dispatched statically, developers can change the way these methods are called without affecting subclasses." - Jonathan Aldrich: "Selective Open Recursion: A Solution to the Fragile Base Class Problem." [via LtU@]
|earl.strain.at • esa3 • online for 6927 days • c'est un vanilla site|