Is Mozilla Ubiquity Dead? 148
darthcamaro writes "Remember Mozilla Ubiquity? It was an effort to bring natural language commands to the Firefox browser. Now after almost two years of development and a half million downloads, the project is no longer being actively developed. Project founder Aza Raskin is now working on other projects, including Mozilla Jetpack, so Ubiquity is on the back burner. '"There is huge demand for being able to connect the Web with language — to not have to move from one site to another to complete your daily tasks," Raskin said. "And there is huge demand for anyone to be able to write small snippets of code that lets them command the Web the way they want. Ubiquity gave everyday developers a voice with how the browser and the Web works."'"
Open Source Projects (Score:5, Insightful)
It happens to a lot of OSS projects. Suddenly the developers interest just dies and they start doing something else. Just like in our childhood we coded some funny little game for a day (not that I didn't make some cool stuff back then :) and then started on an another project. It needs more motivation to continue some project past the starting interesting.
Re: (Score:3, Funny)
At least when [insert big company] does get this working they wont be able to patent it stop others doing it.
Re: (Score:2, Troll)
Re: (Score:2)
Why do you talk like this phenomenon is exclusive to open source? It happens all the time in closed source projects too, you just never hear about them because of NDAs or whatever.
Re:Open Source Projects (Score:5, Insightful)
With closed source/proprietary projects it usually happens for different reasons, mostly income being the reason. With proprietary projects there will always be coders, and the existing coders will stay coding, because there is income involved with that. Money is a good motivator to continue doing projects you otherwise would had lost interest on.
Great example of this is really the games. Gaming industry develops some really stunning games, and theres big corporations like EA, Activision Blizzard and Ubisoft and then theres the small indie developers and everything in between. But what about open source games? They're mediocre at best, almost always unfinished, and otherwise pretty much shitty. These are long projects, taking up to 500-2000+ men work years to finish, and the quality difference in that comes from the fact that the developers are paid to have the interest to finish the product instead of jumping to their latest new idea.
Re:Open Source Projects (Score:5, Funny)
Wesnoth isn't "shitty" nor "mediocre"
Re: (Score:1, Funny)
True it is not shitty nor mediocre, it is in fact both shitty and mediocre.
Re: (Score:2)
Like, have you seen the graphics man? You'd never be able to sell that nowadays! No one cares about all that strategy shit anymore, that's soo last decade, we're sophisticated now and demand photorealistic graphics!~
Re: (Score:3, Insightful)
I agree. Neither is OpenCiv.
That said, there are a LOT of open source games that are terrible. But I wonder how many concept pitch games there are that we never see, that are terrible?
Re: (Score:1, Insightful)
Except that OpenCiv is really a clone of an existing game. So its already based off something that was popular. What about Wesnoth though? What's it based on?
Re: (Score:3, Informative)
What about Wesnoth though? What's it based on?
http://en.wikipedia.org/wiki/Kohan:_Immortal_Sovereigns [wikipedia.org]
Re: (Score:3, Informative)
It's extremely derivative of the Warlords series of games: http://en.wikipedia.org/wiki/Warlords_(game_series) [wikipedia.org]
And for the record, since it's often mentioned in threads like this, Frozen Bubble is a total clone of Bust-A-Move: http://en.wikipedia.org/wiki/Puzzle_Bobble [wikipedia.org]
So now you know.
Re: (Score:3, Insightful)
Re: (Score:2)
I don't mind that they're clones. I just mind that so many Linux users claim they're original in threads around here.
Re: (Score:2)
Shitty's a little extreme, but I'm all behind mediocre. If I were playing that game in, say, 1996, then I think it'd be better... now it's just kind of yawn.
I'm sorry we insulted your little pet project.
Re: (Score:2)
With closed source/proprietary projects it usually happens for different reasons, mostly income being the reason.
Never underestimate the power of management capriciousness and/or shifting corporate priorities, though...
Re: (Score:3, Interesting)
Tell that to the nethack devteam.
Re: (Score:2)
But what about open source games? They're mediocre at best, almost always unfinished, and otherwise pretty much shitty.
The game is more than code. More than the game engine.
When you look at the classic Lucas Arts adventures, what you see is a strong sense of story.
Art design and animation. Music. Dialog and vocal performance.
Half-Life brought a strong sense of place to the FPS. Black Mesa felt real as you were moving through it.
Not a dark house ride like Doom.
Re:Open Source Projects (Score:4, Interesting)
But has there been any open source games that are good at story, art, animation, music, dialog and vocal performance? Those are actually the things that are missing in them most of all. As someone here points out [slashdot.org], there's technical problems like path finding etc too, but some of the games are technically ok (like nethack, as the previous poster mentioned). But they all lack that polished art, music and story even more.
Re: (Score:3, Interesting)
Polished art, story and music Battle for Wesnoth, and to top it off it's the best turn-based tactical game ever (HoMM? bleh. KB? good, but Wesnoth is better).
But there are huge problems towards developing story-based open source games, which Wesnoth averts mostly by making it extremely easy for a single man to create a campaign of his own: single-player games you usually play once, twice at most. Hard to keep interested in improving a game when you've already played through it a dozen times, and you know yo
Re: (Score:2)
http://www.warsow.net/media/0.5/1280px/06.jpg [warsow.net]
THIS Warsaw?
No, it looks like somebody tried to rip-off Team Fortress 2 in the Unreal 1 engine. If your engine can't do curved surfaces properly, they could at least not make map designs that rely on them. (Look at the curved pipes, and the undoubtedly-supposed-to-be-round badge on the back wall.)
http://www.warsow.net/media/0.5/1280px/wdm19a.jpg [warsow.net]
Look at this one, it's like Tron 2.0. What's that blocky white thing hovering in the air? Is that supposed to be a proje
Re: (Score:2)
They lack polished code as well, you just generally don't notice since you don't see it and you are being beaten with poor quality story/graphics.
You just don't notice the code is substandard because everything else is.
Re: (Score:2)
Why? Modding already exists for that purpose. The game industry has already solved that problem on their own, they don't need open source to come up with an alternate, shittier solution.
For one thing, modding lets artists and designers work with finished, modern games engines. Whereas your open source solution would involve them digging around in source code for months or years before they could even start on the actual game.
Who's more valuable to a games developer? Someone with an intimate knowledge of the
Re: (Score:1)
Re: (Score:1)
Re: (Score:2)
They're mediocre at best, almost always unfinished, and otherwise pretty much shitty.
That's probably because they don't have code monkeys to whip into 100+ hour weeks before the holidays. Also those games aren't exactly declared "complete".
hese are long projects, taking up to 500-2000+ men work years to finish, and the quality difference in that comes from the fact that the developers are paid to have the interest to finish the product instead of jumping to their latest new idea.
Keyword: finish. Most open source games are so huge in scope/vision that most would-be developers looking at it are scared away for good. Compare the Linux kernel: when it started out, its main feature was that it booted, and Linus explicitly stated in the announcement that it "won't become big like HURD or Minix".
Re: (Score:2)
Actually, proprietary projects often die because of lack of income involved in them. Just because something is proprietary doesn't mean it is bringing in money to support continued development (contrariwise, just because something is open source doesn't mean its not bringing in money.) "Open source" doesn't mean "not profitable", and "proprietary" doesn't mean "profita
Re:Open Source Projects (Score:4, Insightful)
It happens all the time in closed source projects too, you just never hear about them
If a tree falls in the woods and I don't hear it, do I care? No. Open source is generally publicly known, especially if it is a large project, so I do feel a bit of remorse when I know a project has been abandoned by its lead.
Re: (Score:2)
If a tree falls in the woods and I don't hear it, do I care? No.
Classic.
Re: (Score:2)
Yes but the difference between OSS and proprietary software is that if the main OSS developers just lose interest in the project, the project can be forked/development work taken over by another part of the OSS community. The question is whether there is enough interest in the OSS community to resurrect Ubiquity.
Re:Open Source Projects (Score:4, Insightful)
Yes but the difference between OSS and proprietary software is that if the main OSS developers just lose interest in the project, the project can be forked/development work taken over by another part of the OSS community.
Sure in an ideal world. In the real world, though, it just means the project stagnates and dies.
Re: (Score:2)
"Possibly" is better than "can't." A project that doesn't have enouh people to be resurrected by OSS would have even less chance of surviving had it been closed source.
Re: (Score:3, Interesting)
If the product stagnates and dies it means no one cares about it enough to put in the effort it takes to fork and actively lead a FOSS project. Personally, I think that's a good thing because it means most FOSS is either well supported by some sort of community or else it is too marginal to bother with. It means the community serves as a litmus test for quality. If there are three active developers then maybe it won't be as good as if there are 300. Also, bear in mind that FOSS is a volunteer effort. T
Re: (Score:2)
Developers are a breed unto themselves and you can plainly see the effect that this has on (for example) GIMP, where there is a very big market for a decent photo editing and manipulation package (as Photoshop will attest), but GIMP falls way short on the usability/accessibility department. It is because GIMP is written FOR developers, rather
Re: (Score:3, Interesting)
It happens a lot to closed source projects, too, though since it is more likely (in either project) to happen when a project is in a state before it is consider "ready for prime time", its a lot less visible in closed source projects, since they aren't as likely to be widely available at that stage.
Re: (Score:1)
Re: (Score:1)
I wouldn't blame Open Source (Score:2)
I just watched the Ubiquity video again for the first time in years to refresh my memory. It's pretty awesome. But it's also a pretty major project that Mozilla can't really do themselves. Web sites need to implement "verbs" for it to work. And browsers other than Mozilla need to implement it too.
That said, I hope it comes back to life and improves. Hey, maybe this /. post will entice some readers to become Ubiquity developers. Maybe Google can help too and bring it to Chrome - and I don't mean as an extens
Ubiquitous (Score:5, Funny)
... the project is no longer being actively developed.
You might even say that Ubiquity is not Ubiquitous.
Vimperator (Score:1)
Ditto here (Score:2)
I fiddled with Ubiquity for a while, but when I discovered Vimperator, I found I never used the darn thing.
Re:Ubiquitous (Score:5, Interesting)
You might also say that Raskin works from a different definition of "Huge Demand" than the rest of us.
"There is huge demand for being able to connect the Web with language — to not have to move from one site to another to complete your daily tasks,"
Ah, no, Raskin, there isn't a huge demand for this. I don't want to deal with my bank account while logged into Google, and I don't want to have every thing I do on the web done from one place.
"And there is huge demand for anyone to be able to write small snippets of code that lets them command the Web the way they want.
Again Wrong Wrong Wrong. Less than .002 percent of web users have even the slightest desire to command the web the way they want, and even fewer want to "write snippets of code". Its time to expand your world view beyond your hacker-cave.
Ubiquity gave everyday developers a voice with how the browser and the Web works."
"Everyday developers"? WTF? So finally at the end of the quote it becomes clear he was talking about 1/1000th of web users, the people who use the web for development daily, who probably managed just fine without Ubiquity.
This project deserved to die.
Re: (Score:2)
Re: (Score:2)
its not that ubiquity isnt good it is but most people don't know what it is or how to use it.
I use ubiquity mainly for translation if i need a language i use ubiquity to translate in either direction this makes it possible to talk with anyone.
Thing is this is one small part of what ubiquity can do i havent a clue about 99% of its functionality.
Re: (Score:2)
"Everyday developers"? WTF? So finally at the end of the quote it becomes clear he was talking about 1/1000th of web users, the people who use the web for development daily, who probably managed just fine without Ubiquity.
This project deserved to die.
I agree. I was one of those "everyday developers", and one afternoon quickly put together the first ROT-13 encoder for Ubiquity 0.1 (link [me.com]) (probably one of the first 20 Ubiquity plug-ins). I added it to their Wiki, and registered it with Ubiquity Herd. I watched it for some time to see the number of people who were using it, and was happy to see a variety of people doing so. It was simple, well debugged, and worked as expected.
Some time later, they upgraded Ubiquity, and required all of the plug-ins to
Re: (Score:2)
I couldn't agree more.
Half a million downloads may be a lot, but lets put that in perspective. From addons.mozilla.org: over 1.8 bln downloads for 109 mln add-ons in use. That means 17 downloads for one use. Or only about 30,000 users for Ubiquity. AdBlockPlus, the most popular add-on, clocks almost 900,000 downloads weekly, for a total of over 72 mln downloads now. Even geeky NoScript is doing almost 400,000 a week.
If there were really great demand, then someone would have stepped in and continued develo
Re: (Score:2)
90% of the usage of ubiquity can be solved by copy/paste and bookmark keywords (e.g. "maps" -> http://maps.google.com/maps?q=%25s [google.com]).
In a nutshell (Score:5, Insightful)
Remember Mozilla Ubiquity?
No.
Re: (Score:2)
Re: (Score:2)
I generally have 60+ tabs open...
Why?
Re: (Score:2)
Bad for you. It's very useful for quick calculations, translations, map searches, etc. I find it most useful to add tasks effortlessly to my Google Calendar.
I suggest you to try it, because it's quite handy.
Re: (Score:2)
Map searches => Google maps (Not hard, no simplification necessary)
translations => google translator ( Not hard, no simplification necessary)
Calculations => calculator ( Not hard, no simplification necessary)
Its not popular, because it makes already simple tasks, slightly simpler after a gentle learning curve. However those new skills are not portable to other browsers or applications. I said the same thing when it was introduced, and it looks like I've been proved right.
Follow best practices (Score:4, Interesting)
Re:Follow best practices (Score:5, Insightful)
yes in theory. in practice, this what i've seen. even in a corporate environment where people are paid to maintain and enhance the old code, the new developers never quite "get it". they are able to fix bugs and add features all right, but it's done with without a vision of the overall project. the result is the code slowly loses maintainability and eventually needs to be re-written (or tossed).
maybe this is poor engineering, but it could also just be physiological. developers are less interested in code when they do not feel ownership. coming in and learning someone else's methodology that you probably don't agree with or even like is just not fun. when developers are paid to do it, they get the job done but don't follow through with the care they would otherwise have if they wrote the code from scratch.
Re: (Score:3, Insightful)
Re: (Score:1)
Re: (Score:2)
Lesson to be learned: do not only document code, but also project vision, in an inspiring way which does not only reach peoples minds, but their harts as well. Make percieved project ownership viral in some way
Re: (Score:2)
That is what "well documented" really, really comes in.
Not just decent comments on all functions, but a separate document that binds it all together, explaining bigger image of things: the architecture of the project, its flavors, design patterns used (where, why and how), things missing or that could be done better, caveats of "touching this innocent-looking thing will break X", and so on. But above all, the big image of things.
Every sensibly done project is usually up to ten big modules strung together in
Re: (Score:2)
If the code written so far is well documented,
Nope, it's open source.
Re: (Score:2)
Seems a bit counterintuitive, doesn't it? If I'm putting code with my name on it out there for everybody to see, I'm probably going to do my best to make it all purdy-like. OTOH, I've seen more than one corporate environment where upper management cares about nothing beyond "can we ship it?".
Your closed code may indeed be meticulously designed and documented, but unless we can see it we'll just have to take your word for it.
one for all, and all for one (Score:1)
Why are we surprised? (Score:3, Insightful)
Re: (Score:1, Offtopic)
Re: (Score:1)
"I guess I should RTFA more often."
LOLOLOLOLOLOL!!! gud 1 brah!
I could see this one coming... (Score:5, Interesting)
Not trying to be an annoying "see, I knew this" jerk, but really, this project was so far reaching and poorly defined in how much it should cover, that it was hard to even grasp what the end result should be, and thus also how to support the project. I'm not sure about others, but I have a much easier time building excitement for a project I know what the end result is supposed to be like, than something where the focus is on writing abstract documents on how the browser should more easily be able to be told what you want, and better ignore technical URL's... or something.
Well, yeah, that's an awesome idea, and so is being able to speak to an OS in a few words, and not have to go through the annoying process of clicking on five different icons and buttons to get there.
But it's also far reaching in scope, and not enough narrowed down. There were some concrete stuff done in it, but it felt like features sprawling in different directions, with no sense of direction. Being able to surf to Google Maps more easily, etc, but really with the extension wanting to do more. Hmm.. The article goes on with this
While conceptually, Taskfox and Ubiquity might seem similar, Raskin noted that Taskfox is actually quite different than Ubiquity.
"Taskfox is integrated directly into the URL bar and has a simplified grammar," Raskin said. "It's more accurate to think of Taskfox as a separate product which is Ubiquity-inspired, which has the potential to evolve towards a richer, more Ubiquity-like interface."
Rephrased, I think Taskfox has the right idea here. Software sometimes need to evolve from something more simple, but with a well-defined feature set, and *then* into something more advanced. Or you'll get software with ill defined scope in terms of features in practice, with less motivated developers behind it. Like Windows Longhorn. Or Ubiquity.
Re: (Score:1, Insightful)
Perhaps, but with Quick Searches you can do 90% of the things you can with Taskfox. Without that extra layer of magically delicious goodness, what is it, really?
Mozilla don't focus on getting Labs ideas out (Score:2, Insightful)
Mozilla Labs has started out on some great projects but they don't seem able to make it out into wider use. What happened to Weave, it's been kicking around for years? Ubiquity, a great start with developer/hacker interest, but the ball dropped.
I'm worried for how able Mozilla is to compete against the threat coming from Google and Chrome at the moment. Their core browser is falling behind on speed and stability and I think they'll find it hard to catch up given the size/age/complexity of the Firefox cod
Re: (Score:2)
I'm worried for how able Mozilla is to compete against the threat coming from Google and Chrome at the moment. Their core browser is falling behind on speed and stability and I think they'll find it hard to catch up given the size/age/complexity of the Firefox codebase compared to Chrome. Google had the opportunity to start from scratch with the knowledge of all the browser vulnerabilities in the last decade and have a much better architecture for security and stability. It's almost unfeasible for Mozilla to refactor firefox to match.
I'm not too worried about convergence or competition between Firefox and Chromium. The way I see it, someone can only switch from Firefox if they either (a) don't use add-ons, (b) can part with the add-ons that they do use, or (c) can find equivalent add-ons in Chromium's library. So, Firefox is going to be for those who need the all-in-one browser that will make a sandwich for you while a javascript/flash-ridden page loads (provided you install the add-on), and Chromium* is going to be for people who jus
Re: (Score:2)
Mozilla Labs has started out on some great projects but they don't seem able to make it out into wider use. What happened to Weave, it's been kicking around for years? Ubiquity, a great start with developer/hacker interest, but the ball dropped.
Sometimes the idea of a "Labs" is to generate new ideas, but not all those ideas are really something that can be productized.
In the case of Ubiquity, it was a great idea at the time (2008) but not well-defined. As a result, I think it wasn't something that (as defined) could be easily integrated into Mozilla.
Google took a much simpler approach ("Let's present context-sensitive links for a user's email, for things we can recognize") and integrated it into the GMail web experience. Interestingly, GMail's we
Re: (Score:2)
> given the size/age/complexity of the Firefox codebase compared to Chrome
The Firefox codebase was comparable to the Chrome one or smaller, last I checked. Age is an interesting question and hard to measure as parts of a codebase get rewritten. Complexity... a tossup.
Seriously, take a look at both carefully instead of just reading the hype.
Re: (Score:3, Informative)
What happened to Weave, it's been kicking around for years?
It's actually been updated recently; it's at the 1.01 release, but they've changed a lot of the options to customize it or at least access them. I even ditched Xmarks in favor of it because of the tab and history sync, and they're looking to add extensions in future releases.. https://mozillalabs.com/weave/ [mozillalabs.com]
Not surprised (Score:3, Insightful)
At the time, I remember thinking how awesome it -could- be, but how limited it was at the moment.
Then I realized that it was the programmer in me talking... Having to type out written commands to make magic happen? That's the Linux command line and most non-techies are horribly afraid of that.
I can't see it happening... Some of the ideas may be used in a GUI medium instead, but the project as it was ... Well, it was pretty much doomed from the start.
Was really useful, but buggy (Score:2, Informative)
Ha. I just went and read about this myself. Personally I found ubiquity really useful. I loved the way I could select a postcode, press a keyboard combo and then just type "map" to get an interactive Google Map. I especially liked the way I could subscribe to feeds of commands, most of which had a whole host of handy options. The natural language process part of it was simple, but easily good enough for the intended purpose.
The reason I stopped using it was because new versions weren't backwards compatible
Re: (Score:2)
I use a bookmarklet with a keyword for the map function. I just type in "gm 31071" and it jumps to http://maps.google.com/maps?q=31071 [google.com], and it worked for directions as well. I have a number of others including for dictionaries, synonyms, and one that used to work on CFR lookups, but broke at some point in the past and which I haven't fixed.
Maybe I'm missing something in Ubiquity's capabilities, but as others have said, I don't know that people are really screaming out for such things, especially if even t
Re: (Score:2)
I hope that you realize that Firefox has this nifty feature called "keywords" that you can use to make searches in the url bar
Yes, I know. In fact, I stated that in my first sentence.
I use a bookmarklet with a keyword for the map function.
Not quite a killer app, but not too far off. (Score:1)
Re: (Score:2)
Now I generally only use it for translation and mapping. Anyone else think Ubiquity is screaming for speech recognition?
You mean I'll get a better response if I scream "GET ME THE FUCK OUTTA HERE!" than if I type it? Cool!
How does this get me more beamtime? (Score:1)
Cause last time I checked, we invented the web so we could get more beamtime, and this has nothing to do with getting me more beamtime.
Natural language has always been a fad - it comes and goes in cycles, or at least since the late 70s when I started.
Re: (Score:3, Interesting)
Don't you mean the late 50s? COBOL was more or less an attempt at natural language and arguably one of the most successful ones.
Re: (Score:1)
I'm thinking more of the craze for LISP and other languages at the time - learned COBOL, PL/1, PL/C, FORTRAN, BASIC back then and these natural language things seem to come and go every few years.
Re: (Score:2)
Lisp? That's like the anti-COBOL. Used *for* natural language processing, not so much natural language in its syntax.
Re: (Score:2)
Um, what?
Natural language has been pretty popular for longer than all of recorded history, so its clearly not a fad.
Its also been pretty constantly a goal, for quite some time, to get computers to understand something approximating it for human interactions. For pretty obvious reasons -- its certainly a manner in which humans are generally pretty comfortable interacting.
Re: (Score:2)
Re: (Score:1, Insightful)
Natural language (AS INPUT TO A COMPUTER) has always been a fad. That was the context of the statement. Any statements about humans who use natural language to communicate directly with other humans are completely irrelevant, Sparky.
GP was right
Re: (Score:2)
Its been a continuous area of research that has been regularly producing new products and offerings for several decades. There are certainly monents in times where particular approaches or areas of application are transitorily popular and might be remotely fairly described as "fads", but the broad subject itself is very much not a fad, and never has been.
Pity (Score:3, Interesting)
Damn shame. I used it all the time to create tinyurls, to translate text on the fly, and so on. It was a handy little utility, and I was excited with the direction they wanted to go it.
It'd be nice if they could even just do a version update so I could use it with Firefox 3.6.
Re: (Score:2)
Latest release [mozilla.org] works with Firefox 3.6
Re: (Score:2)
Huh. At one point they made 1.9 (I believe) as a transitional release to 0.5, which had a different, mostly incompatible, command structure.
So they've updated 1.9 to be compatible with FF 3.6, but the latest release I have, 0.5.4, remains incompatible.
Odd decision, but if it works, it works. Thanks for the heads-up.
Re: (Score:2)
Just to clarify, that's 0.1.9.1, not 1.9 - if you're happy with 0.5 it may be worth considering sticking with Firefox 3.5. I stuck with 0.1 because I found the new command structure annoying (I could have learned to live with it, but ultimately I'd prefer Firefox to be up to date more than I'd prefer the latest and greatest Ubiq ;-)
Re: (Score:2)
I had no problem with the 0.5 release, but I also prefer an up-to-date Firefox over Ubiquity, so I downgraded.
Thanks again!
What's the point? (Score:2)
Re: (Score:1)
I use Ubiquity all the time for text translation. You just highlight the text, bring up Ubiquity and type translate. IMO this is where ubiquity shines; its hardly bolted on, its a really natural way of instructing the browser to work with the page I have open. Its way more convenient than any other option since I don't have to switch pages/tabs.
I'll be honest: I hope so. ;) (Score:2)
Frankly, the basic idea was not that bad. But everything was awful.
Basically, Firefox with Ubiquity had at least 3 things, to do the exact same thing:
1. The search input field (top right): Choose a search and enter the query.
2. The keyword search (URL field): Enter the keyword (e.g. dict), followed by the query.
3. Use Ubiquity, enter the keyword, and the parameters/query.
Of course, Ubiquity was more. Because it was a generalization of [1] and [2] to GET/POSTs with multiple fields.
But that could have easily
Re: (Score:2)
Dammit! I meant to say “But everything ELSE was awful.”. Slipped right trough the preview, apparently.
Oh, and nontheless, experimenting, and coming up with new ways and ideas, is always a great thing. Even when the result is sometimes bad. Because it always puts us one step forward. :)
Re: (Score:1)
If you think it trough, you are likely swine.
Not surprising (Score:2)
Commands in a browser (Score:2)
Vimperator, the one plugin the keeps me on firefox. Of course the kids won't like it much since it requires the use of the keyboard.
Archy (Score:2)
I loved Ubiquity (Score:1)
Ubiquity was just proof that even good projects.. (Score:2)