I always have doubts about if I am using the "right" language and framework and while I'll never be completely sure it does make sense some times. Chris McDonough the creator of BFG:Repoze is talking about when it's appropriate to create a new framework. I'm not anywhere close to that kind of stuff but Casey Duncan adds some comments referring to Zope 2 (the application that became a framework) and the Zope Toolkit ( meta-framwork ). Casey's descriptions are very close to my experience of these projects.
A few paragraphs from Casey's comment.
One would be the application that becomes a framework. This would of course be our old friend Zope2. Since frameworks are almost applications, it seems like this should not be too problematic. Technologically it probably isn't, you could just pull out some of the hardwired application policies and features and somehow make them pluggable. But the practice of developing an application is often done with a different mindset on reuse, and whatever apis exist are designed only with the convenience of the application in mind. Often expediency is the order of the day, because folks largely don't care how horribly factored an application is underneath, so long as the paint on the outside is nice and glossy. So the focus is on an end-user that is different from the end-user of a framework, and thus making it into a framework after the fact leads to a big impedance-mismatch. OTOH, application do have one very strong benefit, they do something useful already. So using an application-turned-framework to build an application that is largely similar to the original one should be a cake-walk.
Another framework pitfall is the meta-framework. I think we all know which one I mean ;^). This is the polar opposite of the application-turned-framework. This framework has never been an application, and cares little about such things. It is a jig for building tools, a hammer factory, or maybe even a tool for building a tool factory, or maybe...nobody knows. The cool thing about the meta-framework though is that smart people, with an unnatural grasp of the abstract, can build their own frameworks out of it, and those frameworks might even have a discernible goal. And maybe those frameworks can be leveraged by normal human-brained application developers, even.
Thursday, March 18th
I'm rooting for KY and hope they go all the way but all I really hope for are some good games without the officials getting in the way. If you want, you can take a look at my bracket.
As usual someone has put up a page on Wikipedia that has a lot of good information. It also looks like they are going to be posting the results so it should make it easy to find out what's happening (wihout a lot of ads).
If you want to learn more about the Kentucky "WildCats" here is another page from Wikipedia that has more information about the members of the team.
Some times you look at a page, it looks interesting and you wonder what's behind that page. Looking at the HTML headers often reveals interesting things about the site like what web server they are using, maybe what languges (php, python, ruby) and even more.
Safari doesn't have a built in way to look at those headers so here is a little applescript that does the trick. It depends on curl but Mac OS X ships with curl so this shouldn't be a problem.
tell application "Safari" to set theURL to URL of document 1 set cmd to "curl -I " & theURL do shell script cmd display dialog result
There is this large flat space which almost seems surrounded by mountains. The Wasatch rise up sharply in the east. The mountains are still snow covered. From SLC I can't make out any towns or buildings but you can see some towers on the closest peaks. Flying in on a plane kind of robs you of the experience "How did I get in here and how am I going to get out"
Below is just a small movie which I took with my Casio camera and then converted to MPG4. I dont' know yet if Windows user will be able to see it.
Distributed software development largely relies on a mental division of labor that is hierarchical: intelligent work is specialized to the design group, code writing is given to a less skilled group, and debugging and maintenance to an even less skilled (and lowly paid) group.
Check the source
On the Commons is a group dedicated to the concept of some form of shared wealth. What I thought was interesting was this list of thinkers and activist. Do you recognise them?
I was looking for the concept of intellectual technologies when this showed up. Can't read a lot of things on this site because they are in French but this one posting is enough for me. Lots of good ideas of how and why the net changes teaching and learning.
This particular explosion of technology has has profound consequences for how we organize production. It has consequences for the type of goods we value. We used to live in an economy in which the canonical source of value was an ingot of iron, a barrel of oil or a bushel of wheat. Such economies were based on knowledge just as much as our economy is, but the knowledge was of how to create a useful, physically-embodied good. We are moving to an economy in which the canonical source of value is a gene sequence, a line of computer code, or a logo. As Chairman Greenspan (1998) has often emphasized, in such a world, goods are increasingly valued not for their physical mass or other physical properties but for weightless ideas (see Coyle (1998)). In such an economy, what you know matters more than how much you can lift.