Social economy: Difference between revisions

From zooid Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
----
{{SH_Rev|3630|20100622031552|User:Rparungao|File:Logo.gif}}{{SH_Properties|}}
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
{{SH_Categories|}}
----
=[http://ehyloxame.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://ehyloxame.co.cc CLICK HERE]=
----
</div>
== Critisisms of Drupal ==
 
I would call Drupal the software I love to hate, but it's more simply the software I hate. In my peer group I seem to be in the minority for loving the rigour of Java based systems, which I think is completely appropriate for any system that is meant to be constantly built on and redesigned over long periods of time. Systems based on fine grained standard components are easy to build on, robust, and provide all the customization you could wish for.
 
Unfortunately Drupal has caught on with my typical client, the smaller non profits who can't depend on an IT department. So I'll try to constructively criticize it here. I would love for this list to become completely outdated as Drupal tackles these problems. All of them have been mentioned as &quot;to dos&quot; by the Drupal &quot;executive&quot; for several major versions, with no progress.
 
No data model or high level API - api.drupal.org is documentation, not an api. When the top-down API changes, code just breaks, often without warning. Manipulating &quot;entities&quot; using array references and text symbols is a one way ticket to hair-pulling debugging, bad quality data, and porting pain. It inherently creates queries that are incredibly complex the kind thing models and APIs were designed to solve, but can't be used with Drupal. So code is built that the developers themselves barely understand, is inefficient and difficult to build on.
 
As an example, a project I'm working on with a university was originally, after some angst, targeted for Drupal 6.x. After some months of work, it was decided to switch back to Drupal 5.x, even though t's not the current version, because some key modules don't yet work with Drupal 6.x. But guess what, by the time the project is done, Drupal 7.x is likely to be out. So, because of the drawbacks of PHP and Drupal, nothing is compatible, resulting in a littered field of abandon ware, outdated documentation, things that half work. This isn't how Java projects work.
 
Of course, Drupallers think working with this kind of code is high-tech, but it's really macabre.
 
No relational support. With CCK (which is a reinvention of what a real CMS is, though it has the most interesting potential), this is amplified. Data integrity is out the door, and you have to reverse engineer your own designs.
 
And most of all the disingenuousness, the intellectual dishonesty of the lead developers. They are happy to sit back while Drupal is covered with acclaim, when most of them are pretty hardcore and know about the real problems and lack of design, the fact that Drupal basically builds on arbitrary hooks, switches, massive use of arbitrary text for logic, and entity design that are all gigantic steps back from what solid programming tools provide. There isn't a piece of documentation that isn't filled with superlatives, yet in reality decades old wheels are being reinvented with more attention to hype than care. And for some reason many Drupal mid level developers act as uncritical apologists, though if you search at all you can find endless posts inquiring about incompatible versions and the many hacks required to get normal things done.
 
[[Drupal OO Discussion]]
 
http://www.inertweb.com/2008/12/21/how-i-learned-love-drupal - a fair article that's &quot;for&quot; Drupal. Though he still completely glosses over all the advantages of using decades of well designed software in favour of something that always does things its own way.

Revision as of 19:11, 16 November 2010

Originally posted to the Visible Government mailing list on the topic of "economic benefits of open data."

My belief is that many of the most important benefits won't exactly be "economic" but will be more significantly transformative (though we won't always notice it — "the whole world turns upside down in ten years, but you turn upside down with it," Spider Robinson).

http://www.longwoods.com/audio-video/video/1/377 provides fascinating cues of how the economic service model of care doesn't scale to upcoming challenges, and top government advisors are recommending social media solutions to problems like knocking on senior's doors to make sure they're ok.

Person repairs a pothole

Projecting a bit, I'd like to see involvement change from "fixmystreet.com" to "letsfixourstreets.com." letsfixourstreets could start with local people organizing to fix potholes in their alleys. Material sourced openly, an experienced volunteer from across town, a few people on the block spending Saturday afternoon lifting a shovel instead of going to the gym, fixing a problem that would otherwise get tied up in red tape and exaggerated costs.

As it become more formalized and trustworthy, "the government" could become more of a certifying body and reliable transparent bookkeeper to support these efficient, neighbourly projects.

There are immense challenges in this idea. I'm very much for the benefits of organized government, and must acknowledge the benefits of bodies like unions, where these changes would be highly disruptive. And, of course, I'm living in a techno-utopian bubble which the majority of people wouldn't relate to.

{{#widget:YouTube|id=184NTV2CE_c}}

Still, I can't help think many elements of our current economy and civic models don't make much sense after so many generations of incredible development and world-wide effects, largely between the poles of Silicon Valley possibilities and China economies of scale. And often feel we're heading toward a "survival of the bureaucratiest" dystopia.

There are clear signs of this movement in what's being called "Collaborative Consumption." Creating trust to do things like rent personal vehicles on sliding scales based on the quality of experience.

I do understand "economic benefits" make open data easier to understand by many players. But if you're not appealing to a government or corporate agency, it's interesting to look past extant models.

It's also worth talking about personal energy. Many people have great ideas, but keeping them going in a highly competitive world (even amongst socially focused developers) isn't easy. This is one reason I'm so keen on the Semantic Mediawiki combination. Compared to completely custom software bases (which are sometimes necessary), it makes it easier to track, understand, and participate in a base's development. It's based on Wikipedia, which is a tremendous force on its own. Add to the mix structured data and interactive views (not to mention the developing RDF exchange layer) and a lot of great systems can be created using open data sources and SMW. http://canbudget.zooid.org/wiki/Main_Page is one I meant to share that was put together as a demonstration based on G8/G20 data as discussed on this list.

Which brings me to my third topic, and I'm sorry to run on. OpenCongress.org has a base of political players based on Semantic Mediawiki, for example http://www.opencongress.org/wiki/United_States_Democratic_Party

Marc Lombardi diagram of people and organizations connects responsibility Theyrule.net graph of people and organizations connects responsibility

My feeling is it's timely and appropriate to create shared public databases for these sort for public participants — public and private companies, government units and representatives, and individual people when they have public interaction. Mark Lombardi and theyrule.net explored these ideas, and my feeling is, past the unnecessary conspiratorial air, they will generate constant public interest and have great value in opening up relevant information, and also help to connect efforts in a "wetry.org" way. Canbudget helps to explore this in pages that add information and costs on pages like http://canbudget.zooid.org/wiki/2010/G20 Now I'm working on tools to discover relationships and present them effectively.



RSS

Blikied on Nov 16, 2010