I think you hit the nail on the head there.
Although I think part of the point of collaborative editing is that one individual can't claim all of the results. That's part of the deal.
1. Never seen that problem, and have been using the Firefox 2 branch for months.
2. Wait for Firefox 3, when the rendering system will be given a major overhaul.
Slashdot Mirror
Stability problems are getting better every day. http://blog.mozilla.com/metrics/2010/04/08/dramatic-stability-improvements-in-firefox/
No, they haven't. It's not fully optimized and tested yet.
It's worth noting that crash rates have been driven down significantly recently. They are indeed addressing the instabilities and tackling the problem like you demand. Pretty graphs and charts (also read the comments from Mozilla devs): http://blog.mozilla.com/metrics/2010/04/08/dramatic-stability-improvements-in-firefox/
Firefox also provides tags for bookmarks and live bookmark search (using tags, URL, or title) in the AwesomeBar. There's no excuse.
This is being investigated, in fact. Work is being done to use Direct2D for hardware acceleration in Vista and 7. https://bugzilla.mozilla.org/show_bug.cgi?id=527707
At least this hints that there isn't a trivial way of breaking RSA, AES, or the other popular systems.
Random number generation issue?
The rendering and networking side of Mozilla browsers are most definitely C++. The JavaScript bit is the user interface side.
I think you hit the nail on the head there. Although I think part of the point of collaborative editing is that one individual can't claim all of the results. That's part of the deal.
1. Never seen that problem, and have been using the Firefox 2 branch for months. 2. Wait for Firefox 3, when the rendering system will be given a major overhaul.