I don't get that. Why people like the Opera vkb better.

They have approximately the same keys, except the FastSMSEvo one is bigger buttons. The only problem is FastSMSEvo has a couple of bugs and isn't as integrated into the browser. *Shrug* To be fair I neve got why people practically orgasmed over the Opera VKB since it came out. From an actual usability perspective it's about as useful as an iPhone VKB. I.E. not that useful. Admittedly most of my qualms with the Opera vkb are present in the FastSMS one, but at least I know the dev plans to work on at least one of them. With Opera you have to hope they take your feature request and use it.

The problem is that MicroB is not just FireFox - it's FireFox's web engine, the Mozilla engine I think they call it, after the group that produces it (hence "Mozilla FireFox" being the full browser name for FireFox, as Chrome's is "Google Chrome", etc) vs. their browser's name.

The engine, however, works just fine as is. It doesn't nead much tweaking. The thing that doesn't work fine (or at least that most people want modified/tweaked) is the user interface - and that - all the parts you actually interact with, in other words - isn't open. So the bits most people actually want to modify don't exactly work. As for plugins, there's a critical mass of power users vs. normal users that has to be present before power users feel like putting out easy-to-use stuff for things they can already do. On the N900, the power users are happy with greasemonkey scripts and the like. (Although, I suspect the UI being closed source does make making plugins that need UI input/display-space difficult.)

Never really liked single click to zoom, especially on Opera. It basically means that the page will load normal but before I want to click on anything it'll zoom in to whatever amount it's set to first. When I press something, I want it to use normal click behavior, not something completely different. At least double-click on a non-link makes sense to me, and doesn't collide with default normal actions.

That said I'm a strong believer in users having choices - you should be able to set what clicking does what.

As a general commentary on zoom though, I love MicroB's approach. I love swirl to zoom, as it works with one finger instead of two, and I love the MicroB double click to zoom because it inteligently (at least as much as it can) tries to fit the zoom to the shape of the element you're double-clicking. One of my great annoyances with Opera's zoom was just that - it makes this assumption that you'll always want to zoom in the same amount regardless of what webpage you're on. (This is my main problem with people liking Opera so much. Just like people liking the iPhone, it's people liking something that works nicely at the cost of much in-my-opinion-must-have flexibility and usability. And just like the iPhone, it makes me feel like people are fitting thselves to like the tool instead of expecting the tool to be good for them.)

Anyway, I used Opera a few times in portrait mode, though I honestly didn't love the experience that much. Since FastSMSEvo started working correctly with the browser, I found that I don't even think about using the Opera Browser for anything, and at this point, I'm not sure I'm ever going to use it (to the point where I've thought about deletingh it to free up rootfs space, which is very odd for me - I am very much a fan of running more than one browser at once, for logging in to the same site with different accounts, and just for having options when some page doesn't load).

But yeah. I get that there's a list of people who like the way Opera is set up, I just wish that the people who make these programs would think about broad categories of users instead of just one or two that they perceive as the majority. Yes it makes the code more complicated, but not by much I'd argue.