weblogs.mozillazine.org— A recent front page Digg story complained about Mozilla removing Places from Firefox 2.0. Ben Goodger explains all the good stuff that Ff 2.0 *WILL* have.
Apr 29, 2006View in Crawl 4
holy s**t, wow. you guys completely misinterpreted me.i'm on your side!! i use firefox.i know png is a fantastic format and has been around awhile despite IE's like of support for it. i was just commenting that he knowingly used it on his blog while ie displays it incorrectly. it's obviously because anyone who visits his blog most likely is using firefox, i get that.but thanks for accusing me of being a dumbass user of IE guys. (I HATE ALL VERSIONS OF IE!)
dasch, that may be true but Places was no where near being releasable. They'll need to build in a usable old-style Mozilla bookmarks mode before they can release it. Too many people rely on that (me being one of them) to change to a more disorganized manner.
@dasch I know it is part FF design not to include modern browser features out of the box. And I still think this is a design flaw/error. Who want to have features removed/not included in a product just to keep the box lightweight (which BTW it is not) and end up with something hardly usable out of the box. in short - FF is marketed as "safer, faster, better" (than IE) and the UI seems to have evolved only to mimic IE UI and that was achieved back phoenix 0.5 ( <a class="user" href="http://community.wvu.edu/~ast002/mozilla/historyfx.html">http://community.wvu.edu/~ast002/mozilla/historyfx.html</a> )- opera is a free, lightweight, fast, secure, reliable, usable, accessible, standard compliant, fully featured browser.a shame that the mozilla suite is now discontinued to promote FF. Too many marketing around FF, concerned web user and web builders who are not already sick of FF marketing, FF fanboys, FF religion, FF related abuse and deceptions (example: www.ie7.com ) might very well get tired of waiting for FF to add features.my advice to the web users: don't stick to only one browser, learn to use multiple browsers, so you're not browser-dependent and if one fails you you can still use another one without having to unlearn what you're been used to.
I have a question on giving support for Vista Themes priority 1 status, which I assume means "cannot ship without". "P1 A2 NSITheme support for Windows Vista API"Since Vista seems to have been slipping its schedule by one-quarter-per-quarter for the past few quarters, is it not more appropriate to make this a "priority 2" feature?Holding up Firefox 2 for Vista 1.0 seems like a shame. Nobody is going to miss Vista theme support - if they do not have Vista to run it on!It is dangerous to build calls to beta software into production code. You never know what changes will take place between the beta and the finally shipped product. You do not even know if the feature/API will wind up being there at all, as evidenced by feature drops that have already happened to Firefox 2 and Vista.Conversely, everybody is going to enjoy a built-in spell-checker for text fields. So much text content is being entered into browsers these days because of their use as PIMs, growth of social web, and an effort to transfer some traditional desktop apps to Ajax apps.Firefox 2.1 seems like the perfect release for putting in Vista-specific features, if Vista has shipped by the time that version of Firefox is under way.
mrassmanApr 30, 2006
holy s**t, wow. you guys completely misinterpreted me.i'm on your side!! i use firefox.i know png is a fantastic format and has been around awhile despite IE's like of support for it. i was just commenting that he knowingly used it on his blog while ie displays it incorrectly. it's obviously because anyone who visits his blog most likely is using firefox, i get that.but thanks for accusing me of being a dumbass user of IE guys. (I HATE ALL VERSIONS OF IE!)
schradeMay 1, 2006
dasch, that may be true but Places was no where near being releasable. They'll need to build in a usable old-style Mozilla bookmarks mode before they can release it. Too many people rely on that (me being one of them) to change to a more disorganized manner.
worbdMay 1, 2006
Opera had a close button on each tab before Firefox did. Safari did it first, though. Or some IE shell?
kilgorecarpMay 1, 2006
I can wait on places. I just hope that they provide some improvement to bookmark handling in this release.
izzieMay 2, 2006
@dasch I know it is part FF design not to include modern browser features out of the box. And I still think this is a design flaw/error. Who want to have features removed/not included in a product just to keep the box lightweight (which BTW it is not) and end up with something hardly usable out of the box. in short - FF is marketed as "safer, faster, better" (than IE) and the UI seems to have evolved only to mimic IE UI and that was achieved back phoenix 0.5 ( <a class="user" href="http://community.wvu.edu/~ast002/mozilla/historyfx.html">http://community.wvu.edu/~ast002/mozilla/historyfx.html</a> )- opera is a free, lightweight, fast, secure, reliable, usable, accessible, standard compliant, fully featured browser.a shame that the mozilla suite is now discontinued to promote FF. Too many marketing around FF, concerned web user and web builders who are not already sick of FF marketing, FF fanboys, FF religion, FF related abuse and deceptions (example: www.ie7.com ) might very well get tired of waiting for FF to add features.my advice to the web users: don't stick to only one browser, learn to use multiple browsers, so you're not browser-dependent and if one fails you you can still use another one without having to unlearn what you're been used to.
johnnysoftwareMay 2, 2006
I have a question on giving support for Vista Themes priority 1 status, which I assume means "cannot ship without". "P1 A2 NSITheme support for Windows Vista API"Since Vista seems to have been slipping its schedule by one-quarter-per-quarter for the past few quarters, is it not more appropriate to make this a "priority 2" feature?Holding up Firefox 2 for Vista 1.0 seems like a shame. Nobody is going to miss Vista theme support - if they do not have Vista to run it on!It is dangerous to build calls to beta software into production code. You never know what changes will take place between the beta and the finally shipped product. You do not even know if the feature/API will wind up being there at all, as evidenced by feature drops that have already happened to Firefox 2 and Vista.Conversely, everybody is going to enjoy a built-in spell-checker for text fields. So much text content is being entered into browsers these days because of their use as PIMs, growth of social web, and an effort to transfer some traditional desktop apps to Ajax apps.Firefox 2.1 seems like the perfect release for putting in Vista-specific features, if Vista has shipped by the time that version of Firefox is under way.