tag:blogger.com,1999:blog-13777170.post4133003167985090012..comments2024-03-11T02:35:50.848-05:00Comments on grand stream dreams: Patch, Patch, Patch!Unknownnoreply@blogger.comBlogger4125tag:blogger.com,1999:blog-13777170.post-70002050956223404232015-02-16T19:10:22.940-06:002015-02-16T19:10:22.940-06:00@ Firefox Extension Guru - I'd say you are not...@ Firefox Extension Guru - I'd say you are not really missing that much. It is really geared more to the audience that uses the "F12" tools. <br /><br />I like keeping it close as though I don't do much website work, the performance tools that are normally used for monitoring page-element loading, also come in super-handy for troubleshooting network performance.<br /><br />Cheers!<br /><br />--Claus V.Claushttps://www.blogger.com/profile/11692921474310162470noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-59603207354692942852015-02-16T18:53:06.807-06:002015-02-16T18:53:06.807-06:00Have not had a chance to play with the Developer B...Have not had a chance to play with the Developer Builds. Don't really have much free time on my hands as I use to.FF Extension Guruhttps://www.blogger.com/profile/13582647004716743827noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-69129369907603682182015-02-14T18:14:42.038-06:002015-02-14T18:14:42.038-06:00@ FF Extension Guru - Yes! I've only had a few...@ FF Extension Guru - Yes! I've only had a few extensions not play well when an update comes down. I completely lean to having a more secure/updated browser over any inconvenience of a particular plug-in not working.<br /><br />Way I see it, any developer providing an extension they really are committed to will maintain their product for compatibility.<br /><br />If a developer fails to update it for build compatibility after a month or so then I'll jettison it and either find an alternative that will or just work around it.<br /><br />I am very supporting of the Mozilla update schedule and am glad it keeps rolling on. I should keep an eye on the change log, but usually don't bother too much unless something "breaks".<br /><br />I really like the way the Firefox Developer's build handles the update availability notifications. Have you had a chance to play with it? I've got it installed along side my primary public release Firefox build and shift between the two.<br /><br />Cheers,<br />--Claus V.Claushttps://www.blogger.com/profile/11692921474310162470noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-20705931894418565602015-02-08T17:44:00.026-06:002015-02-08T17:44:00.026-06:00Yes, keeping the browser updated is important. But...Yes, keeping the browser updated is important. But yet so many people I run into get annoyed by the six-week update schedule of Mozilla. Some people turn off the updates (and then wonder why they have so many problems). I like that Chrome does the silent updates as it one less thing that requires my attention to maintain. But, yet again there are people who refuse to use Chrome for that very reason. <br /><br />Getting back to Firefox, people are annoyed because the update breaks their add-ons. They are quick to blame Mozilla when in fact it is the add-on developers. These developers have about 4-months from when the Firefox release is in the Nightly stages to release. Of course the majority of the complains are from people using add-ons long abandoned by the developer. FF Extension Guruhttps://www.blogger.com/profile/13582647004716743827noreply@blogger.com