hydrabrowser.com

Browsing the web the other day (looking for Hydra of course, as I am still in the phase when every new page that mentions Hydra and every new user excites me…), I stumbled upon a post in Google groups where some overzealous Firefox admirer openly accused me of making false accusations against Mozilla and Firefox. Actually, the person in question quoted a line from my ‘Hydra Aid’ manifesto, which says the following:
“In the meantime, I ran across a page that lists Firefox myths. I won’t go into the quarrel and the statements listed there should be taken cum grano salis, but one thing draw my attention - I was stunned to see that Firefox is making millions of dollars per year and is - in fact - a real cash cow for its founders! How on earth do they succeed? The answer was simple - through affiliation. They’ve affiliated with Google (don’t know if there are any others companies included…), and made a real fortune out of the deal…”

Now there is no accusation at all in the above, is it? In fact, maybe it would be some if the above statement was a lie, but I did my homework and googled a bit about the subject before I wrote the above lines. My search didn’t last long, as I found a direct link to the Mozilla’s corporation (or Foundation, I’m not sure which is it, but it doesn’t matter though, as the two are in fact the same…) financial audit performed by Hood & Strong LLP - certified public accountants. The document in question can be found at Mozilla’s web, so it’s by no means a well hidden secret kept from the eyes of the public. If you read the document yourself, you’ll see plain and clear that Firefox (Mozilla) earned 75 millions USD in 2006 from royalties - i.e. from it’s search box affiliated with Google, Amazon etc. Quite amazing, isn’t it? And still there are people out there who feel offended when someone says that they’re making money from their browser, as if they shouldn’t have, and as if the fact that they’re quite profitable makes the product less worthy… Software - no matter if it’s open source or a closed proprietary system - cannot be made in the cave by a bunch of bearded-hippie-lonesome programmers and offered to the public for free. Making of the software costs money. Mozilla spent 11,000,000.00 USD in 2006 just for software development, and it’s quite a sum of money if you ask me (it would be interesting to see how much money is mighty MS investing in their browser - just wild guessing here, but I think it’s at least double…). Hosting and distributing software also costs money… Providing help and support costs money…

All in all, we have a classic win-win situation here for Mozilla and Google (and the users, so it’s actually a triple win…). Google profits from this cooperation are huge, so it’s no wonder they’re strongly pushing Firefox on the market, while at the same time hurting their greatest opponent, the mighty Microsoft. I can only imagine Firefox’s profits for 2007, since they probably tripled their user base since the time the audit was made (if they’ve tripled the profits as well, the numbers go up to the stunning sum of 225 millions USD in 2007!?) .

There’s absolutely nothing abnormal in a software such as Firefox being profitable. The only abnormal thing in this story is the reaction of that certain admirer who didn’t even bother to look for the facts himself, taking the formula ‘open source = freedom = no money’ for granted. On the other hand, I would certainly wish to see people from Mozilla taking a step forward and giving some of those profits away to charities, in the true spirit of open source philosophy, making their community really proud of being a part of something as noble and right. If I can do that as an independent and small developer, why wouldn’t they do the same?

As you probably know already, Hydra is more than a browser- it’s a charity project as well. Hydra is - in fact - Robin Hood of software world - taking from the rich companies and giving to those who need it the most - children. There are two main aspects of Hydra Aid , first, there is a donate-per-download principle, where each new Hydra install brings 0.10 US$ to charities. Once Hydra reaches a million downloads, 100,000.00 US$ is donated, and the cycle starts again. Second is the profit share, where 50% of all of the remaining profits is being donated to charities. First can be the reason to download and try Hydra, and second can be a reason to continue using it, as it is not only beautiful, but also very interesting and useful piece of software. How can you contribute to the project? You can download and install Hydra, it costs nothing… You can continue to use Hydra, and whenever you make a purchase using our referral links, a part of your purchase goes to charity (see Hydra Business Model for further explanation). You can also help design a logo for Hydra Aid project, or you can actively contribute by bringing more users to Hydra Aid. If you think that you - as an individual - cannot do much, you’re wrong! If you have at least two friends who use the Internet and are more or less tech savvy, you can try to persuade them to give Hydra a chance, and even more - you can try to persuade them to bring their two friends as well - by the time the chain reaches 20th level, there will be over million Hydra Aid contributors (actually, this looks a lot like those much hated chains of fortune, which is very unfortunate thing - please do not spam anyone, as there’s nothing more damaging to the image of the product, and please don’t make people download Hydra only because of charity aspect - in a long term that would be fatal for the project…).
Here you can follow the download progress, so far it’s rather modest, but hopefully more people will join as we move along. You can download Hydra here . If you have problems downloading, please use the download page over on Download.com, as they have much more bandwidth on their disposal.

Thank you for being part of Hydra Aid.

Current downloads: 1450 (998550 to go…)

(this is a copy of a post that can also be read at http://hydrabrowser.blogspot.com/)

Well, these first few weeks since I made Hydra public pretty much have shown me the way Hydra should develop in the future. First and foremost - reducing the memory footprint. I am running a battery of tests (using memory profiler found at http://memprofiler.com/) to discover where all this memory goes, and for now discovered two important things:
1. there’s not much I can really do about it, as Garbage Collector really does its work rather well and doesn’t allow messing around much;
2. I can achieve some effect by regularly reducing application’s working set and thus swapping memory - in fact, that’s exactly what Hydra already does when minimized, and achieves great results in doing so (reducing memory consumption from 120 MB to 16MB, or 6-7 times…).
I’m not entirely happy with both statements, and I’m really frustrated with the current state, so in the next couple of weeks I am going to battle and hopefully will reach some acceptable level of memory consumption. I’m aware there are a lot of improvements I can make in code itself (especially regarding string handling, where I have the option to use string builder more often, instead of allocating strings directly, but I somehow doubt it’ll add some significant improvements over the current state of things). I’ll also try to document my findings here, since it might be of some use to my fellow programers. In order to track progress, let’s document the situation as it is, before any of the optimizations took place.

This is the image taken immediately after Hydra is started, picture speaks for itself… Hydra’s working set occupies 54 MB of RAM.

Here is another screenshot - this time there are two open tabs. Performance penalty is drastic, as each loaded tab adds incredible 25 MB load on application! Microsoft warns about the webbrowser control as insatient memory eater, but this is way to much…

And now the incredible change, as Hydra is minimized, the working set gets freed up - the result is amazing - from 102 MB to 7 MB in a second! Of course, this is rather elusive, as the application will request this memory back again once it gets reactivated.
Much more important information about the memory consumption can be obtained from the PerfMon tool that can be run from the Run command (Start->Run>>Perfmon>>OK). In order to track a process using Perfmon, right click the counters list and choose ‘Properties’. Click on ‘Add’ button, and then under ‘Performance object’ select ‘Process’ instead of ‘Processor’. In the list of active processes choose the process you wish to track. In the ‘Counters’ section choose ‘Working Set’ and ‘Private Bytes’ counters and add them to active counters. In my case, I decided to track Hydra, Firefox and Internet Explorer (you’ll notice that IE has significantly larger values than Hydra and Firefox, in its defence I can just say that its session was quite long, and it’s rather natural for an app to accumulate more memory usage when it runs longer).

Here you see the results - Hydra is losing when compared to Firefox, while it has an advantage relating to IE. In fact, Hydra would take about 5-10% more memory than IE under the same circumstances.
Well, this concludes part one of this great saga, I’ll update you on the progress as it goes

Greetings from Hydra Team!