it doesn't use natural language processing, it *computes* the answer. 

1. create something very basic, or

2. spend countless hours searching the web for Photoshop tutorials on how to create a bubble or depth effect, then spend even-more-countless hours fighting with Photoshop to implement it, and finally, maybe adapt the image with some external tools to make it be a CSS sprite or whatever)

Yes, 1. is not necessary a bad thing (HN is a good example :-)), but we all know that for most softwares, some attractive eye-candies are useful. Even GMail uses more than a simple <input type="button"> to display their buttons.

So here comes Da Button Factory. It aims at making it easier to create pretty buttons, which are one of the key elements of an user interface (especially on the web), in an quick and human-friendly way (not tons of options/menus/concepts like in an image processing program). And because using plain image files on the web often sucks, it (will) provide solutions that makes good use of CSS.

Currently it's just a beta. There is only a very simple CSS solution implemented. It may looks ugly in some browsers. Things are not polished.

But I would be very glad to hear any comments of yours on this "draft". Do you find it interesting? Do you have any critics/ideas about it? Did you notice any bugs or problems?

Oh, and I am french, so please excuse me for any grammar/spelling mistake in this post, and don't hesitate to correct me, of course :-)

So what? They've outsold the X-box 3 to 1 and the PS3 7 to 1, and unlike either of them, they're making a significant profit rather than subsidizing the hardware. The Wii has already won its generation hands down and has generated enough profit to fund a more powerful successor.

Turns out nobody but console geeks cares about the architecture. And at a couple of hundred quid a pop, I'm sure most Wii owners will be more than willing to upgrade to a new version when the hardware is upgraded. They're not upgrading a small computer, they're upgrading a console.

PS3/XBox, on the other hand, have take the road of literally building a whole, powerful computer in a box. The market has shown that this is a less successful way to build consoles - whatever console geeks may have to say about it.

(Were you really being serious?)

If you want to get this past python-dev you'll need to explain the benefits, here's a start:

1) Lower cognitive load: Users can understand blocks but the extra naming/reference is one too many things for their brain stack to handle.

2) More descriptive: with blocks the first line says "I'm about to define a function for use with X" instead of the existing way which says "I'm defining a function. Now I'm using that function with X."

3) Show me: take a chunk of an existing project (stdlib is best) and rewrite it with the proposed block syntax. You get to cherry pick the example so if the new version doesn't read much cleaner than the old version maybe the idea isn't so hot.

I'm -1 on the idea but if you want to change my mind you have to make an argument that doesn't start with "In Ruby..."

I think that's the point shimonamit is making.