I am fascinated by JavaScript and its rise in Drupal and the web in general and I am looking for a system to do some visual hacking with my 30000 or so public photos on flickr.
So I spent a couple of hours with the Lively Kernel which is JavaScript all the way down instead of turtles! It might not be what I am looking for but it sure is clever.
Here are my notes (I attempted to pick out the nuggets of gold from the mailing list and forum (now closed, bring on the wiki please!)):
It's 2007 and a well funded company like Facebook can't implement secure RSS feeds (RSS feeds served over SSL and protected by HTTP Basic Authentication). Aaargh how many years have we been blogging about the need for secure RSS feeds and that security by obscurity doesn't work? (Answer: since at least 2004) (And I am not impressed by the Facebook Chief Privacy Officer's apologia; sorry the technology exists, 37 signals does it for example with Basecamp so implement it !). If RSS feeds over SSL with HTTP basic authentication are too much of a technological challenge :-), allow the feed URLs to be revoked like flickr does for its guest pass URLs.
FROM » Facebook’s data feeds a data leak? | Lawgarithms | ZDNet.com:
QUOTE
So where’s the data leak? Here’s where. These feeds are public. All one needs in order to view and use them is the feed’s URI. There’s no requirement that a reader or user of the feed be the “friend” of individuals whose data is in the feed, or even that the person be logged into Facebook. Are you following me?
END QUOTE
The iPhone has launched and despite all the doubters by and large works and is a success (at least in the USA). This is the future for the entire computer industry not just mobile devices. Touch and magical interfaces are in. Interfaces using a stylus and menus are out. And above all user experience is the driving force for selling anything with software from June 29, 2007 on. Thank goodness Apple is kickstarting user experience innovation in the computer industry again!
I finished Dreaming in Code several weeks ago. Amazing, must-read book for both people in the software industry and those not. I finally have a book that I can hand to my parents and other non software people and say: "Read this and you will finally be able to understand the crazy business I am in". Highly Recommended! I will now read everything Scott Rosenberg writes because I am a big fan of his insightful but easy to read prose!
Also recommended: Ellen Ullman's Close to the Machine and Tracy Kidder's The Soul of A New Machine. Classics but not essential for those not in the biz.
Something for open source doubters to think about!
From Nicholas Carr on opensource talking about The Ignorance of Crowds:
QUOTE
END QUOTEWe shouldn’t dismiss lightly the propensity for opensource to innovate, to augment innovation and to accelerate innovation, for the following reasons:
The diversity inherent in the crowd creates long-tail effects, and this causes the bazaar to come up with stuff that the cathedral wouldn’t consider; in cases where the cathedral does consider the innovation, the bazaar is often faster and cheaper; and finally, while tight coordination by central authority seems a worthwhile thing, we should not forget the number of camels designed by committees.
In fact that’s one of the key stanchions of opensource communities. They don’t do camels.
At shdhvan on Friday, Liz Henry (who is most excellent and knowledgeable by the way!) and I started riffing on forums and communities and came up with the following pseudo-manifesto for social software:
Surprise, surprise, most wikis and most content management systems and blog systems like Socialtext, Drupal and Wordpress do most of the above things; most forums don't. Which is why forums make me uncomfortable; lots of forums have great content but they are impossible to follow, ugly and have really bad 1990s style URLs replete with question marks and ampersands which are not hackable.
I love Lightroom so much so that I am a 'small e' evangelist for Lightroom and hate Photoshop but like driving a car, I guess I'm going to get over my loathing of Photoshop's horrendous user interface and non digital photographer oriented features and eventually buy CS3. I am still hoping that Lightroom team eventually re-imagines Photoshop! And yes, I share Tim's ambivalence about Lightroom's non open sourced nature. I think that all apps like all mainstream operating systems will eventually be built around an open source core like Mac OS X is built around BSD and how Lightroom is built around Lua and sqlite.
FROM ongoing · Lightroom and Open Source:
QUOTE
Over the last few years, I’ve become something of an open-source triumphalist, drifting to the conclusion that (on the engineering side) it’s the best way to build software and (on the business side) it’s a better way to monetize it. I have to confess that Adobe Lightroom has kind of shaken my convictions. Certain elements of its UI and design (for example, the crop/rotate tool, and the nondestructive editing paradigm) are qualitative steps forward in the state of the art. Furthermore, I can’t think of a single good business reason for Adobe to open-source it. I guess the conclusion is obvious: for the foreseeable future, both models of software building and marketing are going to march along; neither is doomed.
END QUOTE
Interesting idea for a sustainable model for Free and Open Source Software. Not sure it would work!
From i repeat myself when under stress (free software business model solved) (longer form):
QUOTE
When commercial software is free software -- publicly licensed -- the customer for that software can always get what they want by working with a coop or NPO. This means that the customer can always get their software by paying a fair share of the cost of development.
It's very fine that the customer can always get the free software they need by paying a fair share of the cost of development but that is a problem for developers who want access to investment capital. A developer who wants access to investment capital must have a good chance of returning a profit -- not merely breaking even on cost of development.
So my proposal is that some developers can be paid in shares of their customer's stock instead of cash.
If you issue stock, it is usually easy to grant someone else some of your stock in a way that costs you less in cash than it would cost to buy that same stock.
Now if a developer, paid in stock, immediately sells that stock for cash -- they earn just the cost of production but no profit on top of that.
On the other hand, if a developer paid in stock holds on to that stock, and the customer of the developer's program flourishes, the stock will rise in value. Later in time, the developer can sell the stock and get back the cost of development, plus interest, *plus a profit*.
A free software developer who can make a profit that way has access to investment capital. Such a developer is truly on an equal footing with proprietary developers, from an economic perspective.
END QUOTE
Awesome! I look forward to all Web 2.0 apps using cookie-less Ajax login code.
From 2006, the year HTTP authentication broke - the weblog of Lucas Gonze.:
QUOTE
A few months ago a fellow named Jean-Michel Hiver posted that you could in fact do a clean and modern log-in browser interface using only AJAX methods. He didn't provide any code or much other information, but he did provide a few hints to show how it was possible to write code. I took about 45 minutes to trace his steps and verify that it was true, and it did indeed seem to be possible.
It was one of those HOLY SH*T moments. 100% of user-friendly browser apps use cookies for authentication rather than HTTP, despite the potentially huge advantage of HTTP. If Jean-Michel's point is correct, and it almost certainly is, almost all new browser apps will end up incorporating the new style.
UNQUOTE
Awesome, I might actually check this out in my "copious free time"! Well I probably won't but I'd like to :-) !
From AAS Feature: Nokia Python's Flying Circus.:
QUOTE
Steve Litchfield presents an introduction to the latest (and potentially most powerful) way of creating S60 applications.
UNQUOTE