Firefox 3 was just so slow and breaky compared to Chrome. Also, when Chrome added extensions it caught up to Firefox pretty much immediately. Firefox has this problem where extensions only work in certain versions. So when a new beta comes out, all the extensions will stop working until they update themselves, even if none of the changes would cause them to break. Now that 4 is out, extensions all work again. I don't know if Chrome is faster than FF4 or not, but it doesn't matter. They are both fast enough to be good, and all the necessary extensions work in both. I think Firefox wins just because it has the keyword on bookmark feature that Chrome is probably never going to add.
I'll admit, it looks pretty hot, but I don't know... I'm pretty heavily invested in the googleverse. Though, being able to have my own sync server is appealing.
I'm switching back to Firefox 4. I don't know if it's actually as fast or faster than Chrome now, but its speed is close enough that I don't notice a difference. It also gets some bonus points since TiddlyWiki works in FF without having to do strange things like use a small Java applet and a barely documented command line parameter like Chrome requires. It also supports MathML, which Chrome still doesn't support, and which I use (via LaTeX or ASCIIMath to MathML translators) to put mathematical equations on various notes pages.
Plus, Firebug has been a lifesaver when dealing with the incompetent web programmer my wife has unfortunately been forced to work with.
I'll admit, it looks pretty hot, but I don't know... I'm pretty heavily invested in the googleverse. Though, being able to have my own sync server is appealing.
Yeah. The Chrome sync works better than any sync I've used in the past, but still has flakiness. I'm very interested in running my own sync for reliability and security.
After getting used to the constant march of progress that is Chrome's release cycle, I could never go back to Firefox's "when we get around it" releases.
After getting used to the constant march of progress that is Chrome's release cycle, I could never go back to Firefox's "when we get around it" releases.
I generally don't like to jump on a major update the moment it is publicly available, but within a month or so I will be partaking in the Firefox 4 goodness.
I generally don't like to jump on a major update the moment it is publicly available, but within a month or so I will be partaking in the Firefox 4 goodness.
After getting used to the constant march of progress that is Chrome's release cycle, I could never go back to Firefox's "when we get around it" releases.
Frankly, I haven't been that impressed with Chrome's release cycle. When's the last time they actually offered anything significant? The only thing I can think of is extensions, which was at least a year ago. At least FF4 is a significant improvement over FF3.
After getting used to the constant march of progress that is Chrome's release cycle, I could never go back to Firefox's "when we get around it" releases.
Frankly, I haven't been that impressed with Chrome's release cycle. When's the last time they actually offered anything significant? The only thing I can think of is extensions, which was at least a year ago. At least FF4 is a significant improvement over FF3.
They've a ton of tiny improvements that make the product better as a whole. Internal PDF handling, internal flash handling, more thorough sync... tons of tiny changes that people may not notice come in, but make a big difference.
Do you always want the buggy release software? Sometimes it's a good idea to what for the next version.
The release software isn't buggy. The betas and nightly builds are the buggy ones. The developers have already done all the waiting for you. When it's released that means you don't need to wait anymore. Actually using nightly builds and such, that is madness if you aren't a developer.
After getting used to the constant march of progress that is Chrome's release cycle, I could never go back to Firefox's "when we get around it" releases.
Frankly, I haven't been that impressed with Chrome's release cycle. When's the last time they actually offered anything significant? The only thing I can think of is extensions, which was at least a year ago. At least FF4 is a significant improvement over FF3.
They've a ton of tiny improvements that make the product better as a whole. Internal PDF handling, internal flash handling, more thorough sync... tons of tiny changes that people may not notice come in, but make a big difference.
I'll give you the internal PDF and flash handing, although I don't use the sync features (they don't quite work the way I'd want them to). However, it seems like they keep using whole number releases for them instead of just dot number releases. At least FF3 to FF4 looks and feels like a major change, whereas what changed significantly from Chrome 8 to Chrome 9? I don't remember what was the last version of Chrome without the internal PDF reader, but let's just assume it was 7. Internal PDF is worthy of 7.1, but not an 8.0, IMHO, for example.
Anyway, FF plans to do more frequent incremental changes as well, so it will be interesting to see how it does it.
The release software isn't buggy. The betas and nightly builds are the buggy ones. The developers have already done all the waiting for you. When it's released that means you don't need to wait anymore. Actually using nightly builds and such, that is madness if you aren't a developer.
Yeah, they said Android 2.0 was done when I bought in, it so wasn't.
The only reason I'd switch back to Firefox is if I really needed a toolbar. I installed the StumbleUpon extention/toolbar on Chrome and it was gross. Chrome also has extentions that add better functionality to websites a frequent that, as of my knowledge, Firefox doesn't offer.
I'll try it when I get home, but I doubt I'll ever use it again after the initial test.
I generally don't like to jump on a major update the moment it is publicly available, but within a month or so I will be partaking in the Firefox 4 goodness.
I never understood this thinking.
I would rather continue to use a known quantity (performance, bugs, etc..) than upgrade to a new major version at the risk of being lumped in with all the earliest adopters screaming about some major oversight that wasn't tested for - memory leak, incompatibility, performance issue, etc...
I'm not explaining my thought process very well, but it is along the same lines as to why I don't buy a new video game as soon as it is released. I'll let everyone else deal with the lines (or download wait times), the bevy of early patches that invariably arrive, the sudden need to upgrade computer hardware, etc... while I continue to enjoy the backlog of entertainment that I'll never have enough time for. Then, once things have settled down and a plethora of real-world reviews of the game are available and the game is stable and the price has been cut in half or more then I can confidently purchase and consume the game.
Now if I was a reviewer or developer and needed to have access to the game or new software version immediately for some compelling reason then I would go for it. But when I have something that works, why rock the boat just to be a day 1 adopter? I do want it eventually, but I also want it to be as polished as possible when I consume it.
I would rather continue to use a known quantity (performance, bugs, etc..) than upgrade to a new major version at the risk of being lumped in with all the earliest adopters screaming about some major oversight that wasn't tested for - memory leak, incompatibility, performance issue, etc...
The point is that all that stuff has already happened. All those issues are worked out in the development stages. They are releasing because all of those problems are over. You're just waiting for no reason other than false perception.
The point is that all that stuff has already happened. All those issues are worked out in the development stages. They are releasing because all of those problems are over. You're just waiting for no reason other than false perception.
I think you are jumping onboard under the false perception that everything works properly. Shits happens, and it happens often. I've been burned more often than not with initial release issues.
The point is that all that stuff has already happened. All those issues are worked out in the development stages. They are releasing because all of those problems are over. You're just waiting for no reason other than false perception.
I think you are jumping onboard under the false perception that everything works properly. Shits happens, and it happens often. I've been burned more often than not with initial release issues.
The point is that all that stuff has already happened. All those issues are worked out in the development stages. They are releasing because all of those problems are over. You're just waiting for no reason other than false perception.
I think you are jumping onboard under the false perception that everything works properly. Shits happens, and it happens often. I've been burned more often than not with initial release issues.
The point is that all that stuff has already happened. All those issues are worked out in the development stages. They are releasing because all of those problems are over. You're just waiting for no reason other than false perception.
I think you are jumping onboard under the false perception that everything works properly. Shits happens, and it happens often. I've been burned more often than not with initial release issues.
I've never been burned.
You are both fortunate and in the minority.
Minority in that I don't trust shitty software. Also, I update everything immediately all the time, so I have the fewest bugs and security holes to get fucked by.
Comments
Plus, Firebug has been a lifesaver when dealing with the incompetent web programmer my wife has unfortunately been forced to work with.
Anyway, FF plans to do more frequent incremental changes as well, so it will be interesting to see how it does it.
I'll try it when I get home, but I doubt I'll ever use it again after the initial test.
I'm not explaining my thought process very well, but it is along the same lines as to why I don't buy a new video game as soon as it is released. I'll let everyone else deal with the lines (or download wait times), the bevy of early patches that invariably arrive, the sudden need to upgrade computer hardware, etc... while I continue to enjoy the backlog of entertainment that I'll never have enough time for. Then, once things have settled down and a plethora of real-world reviews of the game are available and the game is stable and the price has been cut in half or more then I can confidently purchase and consume the game.
Now if I was a reviewer or developer and needed to have access to the game or new software version immediately for some compelling reason then I would go for it. But when I have something that works, why rock the boat just to be a day 1 adopter? I do want it eventually, but I also want it to be as polished as possible when I consume it.