Slashdot Mirror


Is Mozilla Ubiquity Dead?

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."'"

148 comments

  1. Open Source Projects by sopssa · · Score: 4, 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.

    1. Re:Open Source Projects by Anonymous Coward · · Score: 3, Funny

      At least when [insert big company] does get this working they wont be able to patent it stop others doing it.

    2. Re:Open Source Projects by FooBarWidget · · Score: 1

      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.

    3. Re:Open Source Projects by sopssa · · Score: 4, 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.

    4. Re:Open Source Projects by wizardforce · · Score: 1

      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.

      --
      Sigs are too short to say anything truly profound so read the above post instead.
    5. Re:Open Source Projects by Lunix+Nutcase · · Score: 3, 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.

    6. Re:Open Source Projects by Thinboy00 · · Score: 5, Funny

      Wesnoth isn't "shitty" nor "mediocre"

      --
      $ make available
    7. Re:Open Source Projects by wizardforce · · Score: 1

      "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.

      --
      Sigs are too short to say anything truly profound so read the above post instead.
    8. Re:Open Source Projects by lymond01 · · Score: 3, 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.

    9. Re:Open Source Projects by Thinboy00 · · Score: 2, 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. The only reason FOSS exists is because someone went to the trouble of writing it. If it is stagnating or nonexistent and you want it, write it yourself! If you don't care enough to do so, don't whine about how no one else is either.

      --
      $ make available
    10. Re:Open Source Projects by Anonymous Coward · · Score: 1, Funny

      True it is not shitty nor mediocre, it is in fact both shitty and mediocre.

    11. Re:Open Source Projects by iNaya · · Score: 1

      If a tree falls in the woods and I don't hear it, do I care? No.

      Classic.

      --
      The Unicode standard is over 20 years old. Why does Slashdot not support it?
    12. Re:Open Source Projects by DragonWriter · · Score: 2, Interesting

      It happens to a lot of OSS projects.

      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.

    13. Re:Open Source Projects by gencha · · Score: 1

      Thou shalt not close parenthesis with an emote!

    14. Re:Open Source Projects by Anonymous Coward · · Score: 0

      Just out of curiosity, what is so "shitty and mediocre"? I like criticism as much as the next guy but maybe you could try actually explaining yourself. Just saying.

    15. Re:Open Source Projects by Wizarth · · Score: 2, 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?

    16. Re:Open Source Projects by Anonymous Coward · · 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?

    17. Re:Open Source Projects by Anonymous Coward · · Score: 0

      Yeah, it's like registering an account on Slashdot to post insightful comments and then realizing that your nickname backwards reads ASS P.O.S., which by itself would cause anyone intelligent to abandon it, but you decide to keep it, because you're writing bullshit comments all the time, so you're just being true to your nickname. You came here to be insightful, but you're just spreading bullshit that gets modded insightful.

    18. Re:Open Source Projects by drooling-dog · · Score: 1

      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...

    19. Re:Open Source Projects by Winckle · · Score: 2, Interesting

      Tell that to the nethack devteam.

    20. Re:Open Source Projects by westlake · · Score: 1

      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.

    21. Re:Open Source Projects by Simmeh · · Score: 1

      Warsow's code is GPL, it's a great game.

    22. Re:Open Source Projects by sopssa · · Score: 3, 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, 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.

    23. Re:Open Source Projects by Anonymous Coward · · Score: 0

      I've played every variation of Civ, and Openciv is easily the worst. It's basically unplayable.

    24. Re:Open Source Projects by Blakey+Rat · · Score: 1

      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.

    25. Re:Open Source Projects by Lotana · · Score: 3, Informative

      What about Wesnoth though? What's it based on?

      http://en.wikipedia.org/wiki/Kohan:_Immortal_Sovereigns

    26. Re:Open Source Projects by Draek · · Score: 2, 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 you'll have to play it a dozen more just to test the changes you're making.

      And that's, also, why there's such a plethora of great multiplayer F/OSS games out there. Warsow in particular not only looks gorgeous, it's also the best arena shooter since UT2004 in terms of gameplay and that's because, when the devs improve the game, they improve it for *them* as well, not just for everybody else.

      --
      No problem is insoluble in all conceivable circumstances.
    27. Re:Open Source Projects by Blakey+Rat · · Score: 2, Informative

      It's extremely derivative of the Warlords series of games: http://en.wikipedia.org/wiki/Warlords_(game_series)

      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

      So now you know.

    28. Re:Open Source Projects by aflag · · Score: 1

      Is that a sign that working isn't fun?

    29. Re:Open Source Projects by Anonymous Coward · · Score: 0

      In general, like most Open Source software, the point is not innovating but freeing something.

      In the case of games the situation is aggravated because unlike developers which have a culture of selflessly contributing to interesting projects(not all of them of course), artists in general expect to be paid for any scribble they draw on toilet paper or any distonal song they sing/compose.

      At best you could gather free artistic talent for one good Open Source game. In practice most games get 0 to 1 artists(that might not even be very talented), and that is the main problem.

      Good looking games with great stories and/or great gameplay would attract developers like shit does flies. Good code isn't enough for games.

    30. Re:Open Source Projects by Jurily · · Score: 1

      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".

    31. Re:Open Source Projects by tadariusven · · Score: 1

      Firefox is the best. Moreover while conceptually, Taskfox and Ubiquity might seem similar, Raskin noted that Taskfox is actually quite different than Ubiquity. http://www.articlesbase.com/health-articles/ultimate-max-burn-review-free-trial-now-1809994.html

    32. Re:Open Source Projects by DragonWriter · · Score: 1

      With proprietary projects there will always be coders, and the existing coders will stay coding, because there is income involved with that.

      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 "profitable".

    33. Re:Open Source Projects by Anonymous Coward · · Score: 0

      Warsow in particular not only looks gorgeous

      lolwut? It's graphics are horribly blocky, cel-shaded crap.

    34. Re:Open Source Projects by zefciu · · Score: 1

      Yeah. Like with MS BOB. They are still coding. I think someone mistakes "Free beer" with "Free as in freedom" again. The fact, that something is open source doesn't mean, they don't make money on it. And the fact that some project was dropped shows it had poor response on the market. It doesn't matter if it was OS or prioprietary.

    35. Re:Open Source Projects by Anonymous Coward · · Score: 0

      Yeah, I'm going to post this AC, but here's the simple truth:

      Battle for Wesnoth looks like it stepped out of 1994.

      Jesus, guys, I'm not knocking the gameplay, and I'm not saying you need good graphics to be fun, but it's not a graphical tour de force by any stretch of the imagination.

      The most popular open source games are almost entirely clones of existing games (ref: Frozen Bubble), community supported open source ports of dead games (ref: Alliegance, Quake) or just plain weak (ref: pretty much everything else.)

      The problems are, of course, simple for anyone who has worked in the industry to point out. Most programmers make terrible designers, and skilled artists are cheap but they don't work for free.

    36. Re:Open Source Projects by Razalhague · · Score: 2, Insightful

      Clones (mediocre or not) are another thing that isn't exclusive to open source.

    37. Re:Open Source Projects by Anonymous Coward · · Score: 0

      Maybe it's about time that designers and the like realize that working on open source games could possibly boost their reputation and thus their career?

    38. Re:Open Source Projects by Rockoon · · Score: 1

      You have forgotten that what developers are willing to invest time in is a form of artificial selection that does not reflect what the market-at-large wants or needs.

      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 than FOR industry professionals or grandma.

      Grandma isn't going to fork the project.

      --
      "His name was James Damore."
    39. Re:Open Source Projects by compro01 · · Score: 1

      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!~

      --
      upon the advice of my lawyer, i have no sig at this time
    40. Re:Open Source Projects by Blakey+Rat · · Score: 1

      I don't mind that they're clones. I just mind that so many Linux users claim they're original in threads around here.

    41. Re:Open Source Projects by Blakey+Rat · · Score: 1

      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 Unreal engine/scripting engine, including sound, physics, and AI? Or someone who's built yet another half-done open source clone of Quake III?

    42. Re:Open Source Projects by Blakey+Rat · · Score: 1

      http://www.warsow.net/media/0.5/1280px/06.jpg

      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

      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 projectile of some sort?

      5 years ago, these graphics might have looked awesome. Now the characters are ok (only because they are highly sylized, and because that style has been popularized by games like Crackdown, Team Fortress 2, etc), but the maps are pretty bad.

      Here's what you're comparing it to, Unreal 2004. (The Unreal 2.0 engine. I'd like to remind you that the Unreal 2.0 engine has been superseded by Unreal 3.0 for, what, 3 years now?)

      http://linux.softpedia.com/screenshots/Unreal-Tournament-2004_1.jpg

      Look, the pipes are actually round!

    43. Re:Open Source Projects by Radtoo · · Score: 1

      You could say this is true for games. Yes.

      Perhaps this is because the biggest need in open source gaming, for a long time now, has been to get better game mechanics than commercial games, not better graphics. Having more fun with the game is surely worth some work, but just better graphics - not so much, apparently. Maybe if it become really easy to do better graphics it will change (I'm thinking primarily of blender, cheap & powerful 3d rendering hardware and specialized tools like makehuman if I say this). At least things sure have changed a lot for fonts and icons on desktops, since both now have great open source tools enabling the creation of these.

      However, right now, for arts and graphics, you should look at the demo scene. That is where the open-source and/or indie combination of it all happens. Just not in games.

    44. Re:Open Source Projects by BitZtream · · Score: 1

      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.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    45. Re:Open Source Projects by Anonymous Coward · · Score: 0

      Well, if no open source developer is interested in coding further, and no closed source company can make money, then yes, we're in a dead end.
      How do we get out of this situation?

  2. Ubiquitous by pitchpipe · · Score: 4, Funny

    ... the project is no longer being actively developed.

    You might even say that Ubiquity is not Ubiquitous.

    --
    Look where all this talking got us, baby.
    1. Re:Ubiquitous by Anonymous Coward · · Score: 0

      You might even say that Ubiquity is not Ubiquitous.

      Try it this way:

      You might even say that Ubiquity...
      *dons sunglasses*
      ...is not ubiquitous.

      YEEEEEEAAAAAAHHHHHH!

    2. Re:Ubiquitous by icebike · · Score: 4, 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.

      --
      Sig Battery depleted. Reverting to safe mode.
    3. Re:Ubiquitous by c0d3g33k · · Score: 1

      Exactly. And further, people that tend to make grandiose proclamations like this frequently and conveniently neglect the technical "how", which often ends up being a huge amount of work if not virtually impossible. I've seen the pattern many times in the context of big data warehousing projects that are supposed to magically unify all knowledge in the company and make everything better. They never do. This smells like the same kind of "if we wish hard enough, it will happen" project.

    4. Re:Ubiquitous by blackest_k · · Score: 1

      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.

    5. Re:Ubiquitous by Anonymous Coward · · Score: 0

      how about NOOOOOOOOOOOOOO

    6. Re:Ubiquitous by Anonymous Coward · · Score: 0

      Was that the Who? And why do you keep taking off and putting on your sunglasses?

      [Horatio mode] Because Mr. Coward.....(puts on sunglasses and pauses)....I'm cool[/Horatio mode]

      YEEEEEEAAAAAAAH!

      My late mother once asked me while watching the show: "What is up with that sunglasses thing he does?"

    7. Re:Ubiquitous by Yaztromo · · Score: 1

      "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) (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 be changed. Not that there was any real notification that it had changed and that my plug-in had to be updated, but having watched it relatively closely, I discovered the update after a week or so, updated my plug-in, and went on my merry way.

      At some point later (after some time), I went to check Herd out of curiosity to see how many people were using my plug-in. And you know what? They dropped it from Herd, and replaced it with someone else's ROT-13 encoder plug-in! From that point on, I wanted nothing to do with keeping my plug-in updated. There was no notice to plug-in developers when API changes that required plug-ins to be rewritten were made (and these were made in virtually every single Ubiquity release!), no notice of being dropped off Herd (which was the way most people found plug-ins) or reasons why, nothing.

      I did keep it up to date on my personal Firefox install, but you know what? I virtually never used it. I eventually let Firefox drop it when I installed Firefox 3.6. It simply wasn't useful enough. And 99.999% of people out there don't want to type commands to do things. It was always more of a "web hackers tool", and positioning it as anything else was just silly. Couple that with the fact that Ubiquity wasn't particularly friendly to those same "web hackers" (at least it wasn't to this old hacker...) that were writing plug-ins for it, and it was pretty much destined to go nowhere.

      So good riddance, I say. Ubiquity promised the moon, but was only ever useful to those who weren't afraid of a command line for 1% of their usual tasks. Hopefully the developers involved in the core project will learn some lessons from it moving forward for their own sake.

      Yaz.

    8. Re:Ubiquitous by wvmarle · · Score: 1

      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 development. Or similar projects would be around to try and do the same. There are plenty more adblockers, for example.

      I have never tried Ubiquity, it may be a nice experiment, may have its uses, but is either not good enough or ahead of its time (rest of software/hardware not good enough yet). Too bad, and smart lead dev to try the idea seriously for two years, see it's leading no-where, and move on.

    9. Re:Ubiquitous by buchner.johannes · · Score: 1

      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).

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
  3. In a nutshell by 93+Escort+Wagon · · Score: 5, Insightful

    Remember Mozilla Ubiquity?

    No.

    --
    #DeleteChrome
    1. Re:In a nutshell by Nerdfest · · Score: 1

      Well I do, and I hope it stays at least supported. The shortcuts for mapping, mailing, and translating are very handy. I also frequently use the 'define' command when reading. I generally have 60+ tabs open, and use the tab selection command. When someone asks "just how many freakin' tabs do you have open?", I use the 'count-tabs' command.

    2. Re:In a nutshell by Anonymous Coward · · Score: 0

      me thinks your using the wrong tool for the job.

      Nothing against ubiquity, just 60? tabs open. I track hundreds of web sites, using tabs isnt the solution.

       

    3. Re:In a nutshell by patro · · Score: 1

      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.

    4. Re:In a nutshell by Bill,+Shooter+of+Bul · · Score: 1

      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.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    5. Re:In a nutshell by Anonymous Coward · · Score: 0

      > When someone asks "just how many freakin' tabs do you have open?", I use the 'count-tabs' command.

      and I can just imagine the smug smile on your face. bet you use linux as well.

    6. Re:In a nutshell by Neil+Hodges · · Score: 1

      I generally have 60+ tabs open...

      Why?

    7. Re:In a nutshell by forpeterssake · · Score: 1

      I sure hope it continues. It took a while to wrap my head around it, but after a while it was the most useful Firefox extension I used, second to AdBlock. Maps, emailing, web searches, image searches, calculator tasks, translations—Ubiquity was my go-too source.

  4. Follow best practices by BhaKi · · Score: 4, Interesting

    If the code written so far is well documented, there should be no problem for anyone to continue development.

    --
    The largest prime factor of my UID is 263267.
    1. Re:Follow best practices by farble1670 · · 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.

    2. Re:Follow best practices by Ltap · · Score: 2, Insightful

      Indeed. The healthiest open-source model seems to be to have different programmers on the development team who differ a great deal; if one has to leave, the other could take over, so that the project could be sustained through introducing new developers. But a single programmer picking up old code and trying to work through it by himself, especially something that would be as tangled a mess as this probably is.

      --
      Yet Another Tech Blog
      (but so much more, including game and movie reviews)
      http://yanteb.peasantoid.org
    3. Re:Follow best practices by afabbro · · Score: 1

      If the code written so far is well documented,

      Nope, it's open source.

      --
      Advice: on VPS providers
    4. Re:Follow best practices by Anonymous Coward · · Score: 0

      As opposed to closed source that may very well be the same but nobody will fucking know since IT'S CLOSED SOURCE!! What maroon.

    5. Re:Follow best practices by Anonymous Coward · · Score: 0

      Amen to that. I once developed a web framework for a corporation that handled things like personalization, profile management, page-level security, etc. I also had the good fortune to have the time to document (in Word!) the entire framework, with code snippets and line-by-line examples of how to configure and use it. People never the less failed to read the documentation and started to fork the codebase when they felt they needed a feature that wasn't avilable. 9 times out of 10, the feature *was* available, and they just didn't take the time to understand the framework - which, incidentally, was built to adapt to future needs.

    6. Re:Follow best practices by drooling-dog · · Score: 1

      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.

    7. Re:Follow best practices by Great+Big+Bird · · Score: 1

      Sir, while I appreciate your insight, I believe your entire post is as unmaintainable as the code that you are discussing would become. You lack any proper sentence structure making it very difficult to understand what you are trying to do. I recommend, as a start, that you should use some capital letters at the beginning of a sentence; and, read up on proper comma use.

    8. Re:Follow best practices by Anonymous Coward · · Score: 0

      Anecdotal and flamebait worthy, but in my experience almost all OSS programmers tend to be hobbyists at best. Driven by results and not a passion for programming. Very few could be called more than a mediocre programmer.

      And it's the same experience in the corporate world. But where the difference lies, is that all of the gifted programmers I have met knows that their work has actual (monetary) value, and generally don't have the time or motivation or desire available to dedicate to large-scale OSS projects.

      Looking forward to the "but some people aren't driven by money" comments. I hold the same answer to that as I do for "does money buy happiness?" - the answer to both is yes, but not absolute; i.e., money will always hold *some* motivation and give *some* happiness, but not always enough.

      And generalizations are always unfair, so I'm twisted as to whether I have a point.

    9. Re:Follow best practices by morie · · Score: 1

      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

      --
      Sig (appended to the end of comments I post, 54 chars)
    10. Re:Follow best practices by SharpFang · · Score: 1

      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 some way, and optionally with a whole bunch of similar small modules attached to specific big modules (GUI module -> screens, database module -> transactions etc). Each of these big modules may be a class or a group of classes, distributed over one or several, or a hundred files. You need to understand what they do, how they are called, what comprises the entirety of the module, what purpose it serves and how it achieves its ends. It's almost never obvious from code comments. A good drawing helps. How often will you see a program structure diagram attached to any Open Source project?

      Most software developers have these in their heads when they work on a program, and if a new person joins a project, they help them build it in their heads, tutoring them. But when a project is left in a repository, it really needs such documentation...

      On the other hand, if you lack enthusiasm to continue developing your program, will you find enough to document it that well?

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  5. one for all, and all for one by ozzy85 · · Score: 1

    That's sad! I really wanted it to be a plugin for in all web browsers, if not built into them to create smooth and efficient waves when web surfing.

  6. Why are we surprised? by Ltap · · Score: 3, Insightful

    Ignoring whether or not it being free software makes a difference - every software company tried its hand at it in the 90s. Their main justification for dropping it was that "the technology isn't advanced enough". It all seems to be part of an attempt to copy Star Trek's tech and use voice commands for computers. In reality, voice commands are incredibly inefficient and imprecise, and it's virtually impossible for a piece of software to try and sort through accents, dialects, and mumbling to guess at the true intent.

    --
    Yet Another Tech Blog
    (but so much more, including game and movie reviews)
    http://yanteb.peasantoid.org
    1. Re:Why are we surprised? by Ltap · · Score: 0, Offtopic

      My apologies. The summary lead me to believe that this was voice recognition. I guess I should RTFA more often.

      --
      Yet Another Tech Blog
      (but so much more, including game and movie reviews)
      http://yanteb.peasantoid.org
    2. Re:Why are we surprised? by Miseph · · Score: 0

      "I guess I should RTFA more often."

      LOLOLOLOLOLOL!!! gud 1 brah!

      --
      Try not to take me more seriously than I take myself.
    3. Re:Why are we surprised? by Anonymous Coward · · Score: 0

      I think your original point still stands; natural language commands have always seemed like a nice idea, but have never quite worked in practice. Whether those natural language statements are delivered as text, or as speech which is converted to text, is not really significant.

  7. I could see this one coming... by Jugalator · · 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.

    --
    Beware: In C++, your friends can see your privates!
    1. Re:I could see this one coming... by Anonymous Coward · · 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?

  8. Mozilla don't focus on getting Labs ideas out by PybusJ · · 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 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.

    What they do have going for them is the collection of extensions and the new ideas from Mozilla Labs; if they don't get them out to the wider audience then their competitors will copy and popularise the best of them, essentially benefiting from free R&D.

    1. Re:Mozilla don't focus on getting Labs ideas out by icannotthinkofaname · · Score: 1

      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 just need to browse the web. Each one will get its market share, and my guess is that in the long run (that is, as time t approaches infinity), it will probably stabilize.

      * We can further divide Chromium's users into users of Chrome (those who have sold their souls to Google or just don't care enough to avoid the spyware components) and users of Iron (the geeks who know what's in Chrome and think they're doing their parts to keep Google out).

      --
      Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
    2. Re:Mozilla don't focus on getting Labs ideas out by Jim+Hall · · Score: 1

      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 web interface does some of this for you already, for example by recognizing phrases in an email that indicate an appointment, and giving you a link in the right-hand side to add it to your calendar. It does the same with addresses.

      I often use the links that GMail shows me when I buy something online, and the vendor emails me a shipping notification. GMail recognizes a UPS (or FedEx, or USPS) tracking code, and gives you a link - right there - to go check on the shipping status of your order.

      So in a way, the functionality of Ubiquity has made it into a product, just not by Mozilla.

    3. Re:Mozilla don't focus on getting Labs ideas out by BZ · · Score: 1

      > 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.

    4. Re:Mozilla don't focus on getting Labs ideas out by Killer+Orca · · Score: 2, 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/

    5. Re:Mozilla don't focus on getting Labs ideas out by Anonymous Coward · · Score: 0

      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.

      I see you haven't looked at the chromium code...

  9. Not surprised by Aladrin · · Score: 2, 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.

    --
    "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
  10. Was really useful, but buggy by chetbox · · 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 and cleaning up after an update became a bit of a mess. I don't know if others had the same experience?

    1. Re:Was really useful, but buggy by Martin+Blank · · Score: 1

      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, 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 the geeks rarely use it.

      --
      You can never go home again... but I guess you can shop there.
    2. Re:Was really useful, but buggy by floodo1 · · Score: 1

      I hope that you realize that Firefox has this nifty feature called "keywords" that you can use to make searches in the url bar....it's had this for as long as I can remember. They're stored in the default directory: Quick Searches

      So, what you do is find the text input box of any search that you use frequently. Right-click the box and select "Add a Keyword for This Search...", this will bring up the bookmark dialog. Here, pick a name, and type in whatever shortcut that you'd like to use ( in your example "gm" ) into the keyword field. Save it anywhere, or the Quick Searches folder for consolidation purposes.
      Now goto the address bar, type "gm xxxxxxxx", hit enter.........instant google maps searches.

      Sometimes sites like google maps do weird things with their text input boxes and this doesn't work..... If google maps is giving you problems try this url http://maps.google.com/maps?q=%25s&f=q&hl=en &nbsp&nbsp if you like to use something other than english, then change the "l=en" part or just get rid of it.

      Personally I use this "i" for google images, and "g" for google, or "yt" for youtube.
      Makes searching the internet much more convenient, and it's already built-in!

      --
      I KUT J00 M4NG!!!
    3. Re:Was really useful, but buggy by chetbox · · Score: 1

      Oh yes, I'm very much aware of this nifty feature (which Opera had many moons ago...). However I think the value of ubiquity came from the ability to subscribe to feeds of commands (potentially many from a single feed) that get regularly updated with new features. Oh yes, and it's *really* easy to create your own and make them as interactive as you like.

    4. Re:Was really useful, but buggy by Martin+Blank · · Score: 1

      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.

      --
      You can never go home again... but I guess you can shop there.
  11. Not quite a killer app, but not too far off. by blattin · · Score: 1

    I remember being rather excited when I first saw the demo for it. Now I generally only use it for translation and mapping. Anyone else think Ubiquity is screaming for speech recognition?

    1. Re:Not quite a killer app, but not too far off. by nycguy · · Score: 1

      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!

  12. How does this get me more beamtime? by WillAffleckUW · · 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.

    --
    -- Tigger warning: This post may contain tiggers! --
    1. Re:How does this get me more beamtime? by DarkOx · · Score: 2, 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.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    2. Re:How does this get me more beamtime? by WillAffleckUW · · 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.

      --
      -- Tigger warning: This post may contain tiggers! --
    3. Re:How does this get me more beamtime? by DragonWriter · · Score: 1

      Natural language has always been a fad

      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.

    4. Re:How does this get me more beamtime? by c0d3g33k · · Score: 1

      It's imprecision is also the cause for most of the problems throughout recorded history. It's not the best form of expression, just the easiest for the most people.

    5. Re:How does this get me more beamtime? by Anonymous Coward · · Score: 1, Insightful

      It never occurs to you twits that if you feel a need to state the obvious, it's because you missed the point. I know, such considerations detract from feeling that the obvious is obvious only to you because you're special just like Mama always said you were.

      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. Natural language queries (AS INPUT TO A COMPUTER - just for you so you don't get confused again) are a fad that comes up from time to time.

    6. Re:How does this get me more beamtime? by lennier · · Score: 1

      Lisp? That's like the anti-COBOL. Used *for* natural language processing, not so much natural language in its syntax.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    7. Re:How does this get me more beamtime? by Anonymous Coward · · Score: 0

      Natural language can be as precise as any formal language. How do you know which is the old and new in a changePassword(s1, s2) function? You look it up in the documentation which is written in natural language...

    8. Re:How does this get me more beamtime? by Anonymous Coward · · Score: 0

      Why does the natural language fad keep coming back? Because computer languages can't adapt to changing conditions and therefore become obsolete; the flexibility of natural language gives it higher survival fitness.

    9. Re:How does this get me more beamtime? by DragonWriter · · Score: 1

      Natural language (AS INPUT TO A COMPUTER) has always been a fad.

      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.

  13. Anonymous Hero by Anonymous Coward · · Score: 0

    Trust me, open source doesn't do well with user experience, interaction, graphic designers and researchers. You want a good product around open source, let open source community build code while hired designers/researchers do their job. All successful useful products go through iterative design process with a lot of user testing, usability testing. Ubiquity is a bad user experience product, throw it one interaction designer, one graphic designer, two-three user experience designers and a couple of researchers you have useful product Ubiquity Pro( $5 )

  14. Re:Blame The Underachieving Niggers by AlmondMan · · Score: 1, Troll

    You sir, should be shot.

  15. Pity by etherlad · · Score: 2, 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.

    --
    Soylens viridis homines es
    1. Re:Pity by I+confirm+I'm+not+a · · Score: 1

      Latest release works with Firefox 3.6

      --
      This is where the serious fun begins.
    2. Re:Pity by Anonymous Coward · · Score: 0

      Version 0.1.9.1 still works fine.

    3. Re:Pity by etherlad · · Score: 1

      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.

      --
      Soylens viridis homines es
    4. Re:Pity by I+confirm+I'm+not+a · · Score: 1

      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 ;-)

      --
      This is where the serious fun begins.
    5. Re:Pity by etherlad · · Score: 1

      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!

      --
      Soylens viridis homines es
    6. Re:Pity by Anonymous Coward · · Score: 0

      It has been for a while
      http://getsatisfaction.com/mozilla/topics/when_will_ubiquity_support_firefox_3_6b4

      Cheers,
      @Blu3fish

  16. What's the point? by martin-boundary · · Score: 1

    The unix shell is much better at interacting linguistically with a user than a browser with a bolted on keyword system. Use the right tool for the job, like Surfraw.

    1. Re:What's the point? by joek1010 · · 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.

  17. I'll be honest: I hope so. ;) by Hurricane78 · · Score: 1

    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 be implemented right in the URL bar. (Or search field for people who prefer that. [Although I don’t know why.])

    Then again, if you think that thing trough to the end, you gonna end up with a general property/option box and a general communication protocol between servers and clients. And such general solutions are great because they usually offer huge emergence (the ability to do much with little interface complexity).
    But we already have that. More than once. And the newest standard is XForms.
    Doesn’t make much sense to cram it into the browser UI itself though.

    And I haven’t even talked about how when you think it trough to the very end, you just end up with algorithms and data structures again.

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
    1. Re:I'll be honest: I hope so. ;) by Hurricane78 · · Score: 1

      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. :)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    2. Re:I'll be honest: I hope so. ;) by maxume · · Score: 1

      If you think it trough, you are likely swine.

      --
      Nerd rage is the funniest rage.
  18. Vimperator by DaveSlash · · Score: 1

    Vimperator replaced Ubiquity in my browser.

    --
    Burn FAT not OIL
  19. Problem imo was, by Anonymous Coward · · Score: 0

    for he kind of things i tried to do with it, i can do already with the search engines i installed, and keywords.
    In fact, i remember trying out the examples and i had to type more. "w Firefox", is imo pretty fast.

  20. Not surprising by cecom · · Score: 1

    Can't say I am surprised. I had never heard of it before, so I diligently clicked all the links in TFA. Yet, within a couple of minutes I still wasn't able to figure out what it was. There were not very useful comparisons with "Launchy", which I haven't heard of either. May be I need to see a live demo to "get it", or may be it is too ahead of its time, or may be it is just garbage. I really don't know, but either way it isn't surprising that it hasn't caught on.

  21. Ditto here by Abcd1234 · · Score: 1

    I fiddled with Ubiquity for a while, but when I discovered Vimperator, I found I never used the darn thing.

  22. Commands in a browser by h4rr4r · · Score: 1

    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.

  23. Archy by lyinhart · · Score: 1

    I hope that Raskin resumes work on Archy, a really promising zooming user interface project started by his dad long ago.

    --
    Freedom is drinking a beer in the park when you're supposed to be at work.
  24. Natural selection by Anonymous Coward · · Score: 0

    Dying out is a good thing. It's natural selection at work. This is why open source development is more agile and, in the long run, will produce better results than proprietary software development.

  25. Rolled into the next firefox? by Anonymous Coward · · Score: 0

    I thought I read somewhere it was being phased out of an addon because it was being rolled into the official firefox codebase and appear in the next major version. I really liked it, and while it seemed problematic (ie simply not working) for me, I'd like to see it continue.

  26. I loved Ubiquity by cupcakewalk · · Score: 1

    'twasn't much, but I had hoped for Ubiquity everywhere, not just he browser. It needs to be an OS add-on.

    --
    -J
    1. Re:I loved Ubiquity by Anonymous Coward · · Score: 0

      Check out Enso at humanized.com
      I believe it was made by the same people, it's like a Desktop version of Ubiquity, with launch, language and other kinds of commands.

      It's kind of dead now, since the team working on it went off to work on Ubiquity (iirc). There is an OpenSource version that is more up to date, though, but that is also not being worked on anymore.

  27. Ubiquity was just proof that even good projects.. by msimm · · Score: 1

    Ubiquity was just proof that even good projects can make bad decisions. It was DOA. It interestingly solved a problem by doing something no-one needed.

    --
    Quack, quack.
  28. What? by Anonymous Coward · · Score: 0

    "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."

    What?

  29. Re:Blame The Underachieving Niggers by Anonymous Coward · · Score: 0

    I will agree that the vast majority of American blacks that I have met were little more than unintelligent scumbags and thugs. There were a few decent ones and even a few very sharp ones, but sadly far too few.

    European blacks are a different matter. Many of them are actually good, honest people.

  30. Nooooooo! by RHaddon · · Score: 1

    Ah no!! I love Ubiquity it's the best tool out there for translating or getting dictionary definitions coincidentally when surfing the web

  31. Mod parent up! by tulimulta · · Score: 1

    Mod parent up. Weave is great.

  32. HNGH by Anonymous Coward · · Score: 0

    Sigh, first Enso and now Ubiquity?
    God damn.

  33. Re:Blame The Underachieving Niggers by imakemusic · · Score: 0, Troll

    Or C, the successful black employer?
    Or D, the single, fat, white man sitting at home with his wife who is pregnant with their fifth child waiting for the next welfare cheque?
    Or E, the successful black politician who was popular enough to be elected as the leader of the most powerful nation on earth (with the backing of most of the international community) and is trying to clear up the mess left by his white predecessor who had to cheat his way into power.

    Fuck you and your racism.

    --
    Brain surgery - it's not rocket science!
  34. Ubiquity by lennier1 · · Score: 1

    Can't help it but that name always makes me think of the Ubuntu installer instead of a Browser module.

  35. I wouldn't blame Open Source by gjt · · Score: 1

    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 extension, but a built in feature (Firefox too). If it's built-in, as opposed to an add on, more users will have access to it and web site developers will have a bigger audience to code verbs for.

  36. Awesome Bar by Anonymous Coward · · Score: 0

    Ubiquity inspired the Awesome Bar, which turned out to be useful enough for many. For others, Google has many commands that fill such needs that Ubiquity is considered as reinventing the wheel.

    1. Re:Awesome Bar by TheReal_sabret00the · · Score: 1

      It's nothing like the Awesome Bar. That said, it was a incredibly awesome. Unfortunately the development was bjorked. It's still being developed, as far as I can tell there are still two coders working on it actively. But with stuff like the shitty UI getting in the way, it's never really going to be adopted. I love Ubiquity, but can understand why the project has been dropped as the framing isn't quite right.