A Comment regarding FDM 3.9.6 and "Plug-in for Firefox" maintenance.
Posted: Fri Jul 10, 2015 6:37 am
We recently seem to have a ludicrous situation where FDM's own Plugins keep breaking, are not corrected almost immediately, despite many Forum early warnings of issues, Plugin cannot work with FF x64, and FDM Plug- ins are not Extension Signed so will be blocked by Mozilla with FF40 Release in one Month's time if that is not resolved by then . In the meantime several other Authors add-ons seem to work mostly or in part and in the case of Flashgot is currently allowing me to use FDM with Firefox 40.0b2 (x32 or x64) as it integrates with FDM both with normal downloads and YouTube.. Additionally Flashgot is also Extension Signed.
For furether details, see my Post Re: PLEASE put up all FDM and Firefox problems here! Postby dko » Thu Jul 09, 2015 12:42 pm
Questions are asked on Forum but answered slowly or not at all as to intent and timetable by Developers.
FDM 3.9.* is a truly wonderful app (and would be even if not free). I feel however, it is in serious danger of being killed off by lack of Dev. support to keep it running and dealing speedily with known issues about to hit, because, it seems, of a desire to work on FDM 5, which after quite a long time development peorid so far is still in Alpha, with many features being requested and many issues still being reported. Currently, whilst FDM 5 Alpha it looks great its a long way for being suitable for release. FDM 5 Alpha is CURRENTLY a pale shadow of it 3.9.x which repeatedly have won "best in group" accolades and still do, from the Online Media.
I am only a User not a Developer but it seems to me the adage "if it ain't broke don't fix it" is somewhat appropriate here. I am NOT saying advancements and modernizing is not desirable or very welcome, but I am unsure why a new pretty and easier (for complete novices) GUI Front End could not have been added to the existing 3.9.6 and make other desired advancements around its core code little by little, rather than seemingly starting a new completely new FDM, which still seems years from release and appears to be taking up most of the Dev. Team kindly given free time and resources and interest.
By the time FDM 5 actually launches, how many loyal FDM Users and FDM diehards will have moved on? This has to be a concern. IMO it is absolutely essential to keep the FDM flagship 3.9.* up and running and to avoid its Plug-ins failing with FF Official Releases (and so many FF Betas). I know, and sympathize with FDM Dev.s that Mozilla keep changing things and "moving the playing field" but why are FDM Plug-ins are so much more vulnerable to those changes than other popular FF download add-ons/plug-ins seem to be . Firefox suggest (they would of course ) that if Developers follow their rules, then there will be no or less unexpected issues. How is it other authors seem faster in identifying and avoiding potential issues or just do not seem to have as many issues in the first place as the FF FDM Plug-in has. Is the FDM Plugin not meeting Firefox Development rules or is inflexible to change?
I was recently told by a Mod of this Forum as not being a suitably advanced User to use/try out Firefox Betas BUT NONE-THE-LESS the crashing in FF 39 was known for some weeks and found others (including Usher) and confirmed by me. I have also over recent weeks months reported several potential forthcoming issues. Below are 3 initiated by me
(with the first listed below, Forum readers/members can see FDM Plugin incompatibility with FF39 (Beta) was first reported 7weeks ago by me) The fully working Fix for FF39 Release came out yesterday. (Dev. did tell me that they thought they had fixed it during late Beta stage but a later Beta build broke it again).
Please provide a new compatible plugin for Firefox 39 Beta and 38.0.5 Beta
by dko » Wed May 27, 2015 8:48 am
A "Heads UP" In Firefox 40.0b Candidate Build 2, FDM Plugin Auto Disabled
by dko » Fri Jul 03, 2015 6:21 am
How will Firefox Add-on Extension Signing be dealt with
by dko » Sat Jul 04, 2015 7:20 am
To date no reply has been forthcoming to the last two "important for all Firefox/FDM Users
To be fair with regard to replies, I did ask one (only) of the Mods (who seems to be the fastest and most frequent/likely to reply on Forum) not to reply to me in future as I felt unfairly patronized and poorly spoken to (water under the Bridge)
It would be a kindness if someone on the Dev. Team will tell Users whether, on 11 Aug 2015 (4 weeks time), the FDM Plugin will work with Firefox and also necessary, whether it will be Extension signed by then (or should we seek/rely on other authors' Add-on (Flashgot in my case) to be able to continue using FDM with Firefox after that date.
I will probably be accused of complaining, but all readers please note I am NOT I am mentioning Facts, valid and reasonable concerns, and forthcoming knowns issues which I am sure the Dev. Team are already aware of.
For, all those who do read this Forum, how many more do not? How many get caught out when FDM Plug-ins for Firefox keep falling over when Firefox versions auto update. Already one of two posters have said they are looking elsewhere, and many have queried the apparent preoccupation with FDM5. Are these people complainers and unreasonable Users OR are they reasonable normal Users who have been faster off the mark in actually saying and doing what many others must be wondering by now, more than more frequently, that essentially
"Dev. do not have enough time to Develop and/or fix and what time they do have is a desire to work on FDM5 Alpha not FDM3.9.x. Fixes and associated posts for FDM 3.9.x (version used by almost ALL FDM Users) are delaying and interfering with FDM 5 its development".
BETAS, in this case Firefox BETAs, are of course Released so Developers of associated add-ons or apps can test their apps and be forewarned of potential issues (and for interested Users to have a look if they want) but with FDM Plug-ins these are not being fixed fast enough. In the latest case the fully working FDM plug-in was not available until 1 week after FF39 Release, this essentially, made FF Release owners the Beta testers for FDM Plug-ins which cannot be good (actually they only found out too late. FF Beta users had already previously know of and reported the issue some time before.
It is very easy to slap down or ignore my comments as "another ungrateful User moaning". Hopefully it will be seen as intended as constructive criticism of the way things are currently seem to be going with FDM from a User point of view. It is important that it is remembered that FDM 5 is a long way from Release and FDM 3.* is the [b]ONLY FDM Release around and it is VERY GOOD and worthy of fast (pre-emptive where possible) maintenance.
Example: why is it not already Extension signed this has been known to be coming months ago. I have 30 Add-ons and all but 4 were already Extension signed a month ago. 3 are working not not yet signed (if not signed by ff40 Release they will be blocked by Mozilla). ONLY FDM Plugin has been totally rejected and disabled by Mozilla. This is not good[/u].
Regard to all.
For furether details, see my Post Re: PLEASE put up all FDM and Firefox problems here! Postby dko » Thu Jul 09, 2015 12:42 pm
Questions are asked on Forum but answered slowly or not at all as to intent and timetable by Developers.
FDM 3.9.* is a truly wonderful app (and would be even if not free). I feel however, it is in serious danger of being killed off by lack of Dev. support to keep it running and dealing speedily with known issues about to hit, because, it seems, of a desire to work on FDM 5, which after quite a long time development peorid so far is still in Alpha, with many features being requested and many issues still being reported. Currently, whilst FDM 5 Alpha it looks great its a long way for being suitable for release. FDM 5 Alpha is CURRENTLY a pale shadow of it 3.9.x which repeatedly have won "best in group" accolades and still do, from the Online Media.
I am only a User not a Developer but it seems to me the adage "if it ain't broke don't fix it" is somewhat appropriate here. I am NOT saying advancements and modernizing is not desirable or very welcome, but I am unsure why a new pretty and easier (for complete novices) GUI Front End could not have been added to the existing 3.9.6 and make other desired advancements around its core code little by little, rather than seemingly starting a new completely new FDM, which still seems years from release and appears to be taking up most of the Dev. Team kindly given free time and resources and interest.
By the time FDM 5 actually launches, how many loyal FDM Users and FDM diehards will have moved on? This has to be a concern. IMO it is absolutely essential to keep the FDM flagship 3.9.* up and running and to avoid its Plug-ins failing with FF Official Releases (and so many FF Betas). I know, and sympathize with FDM Dev.s that Mozilla keep changing things and "moving the playing field" but why are FDM Plug-ins are so much more vulnerable to those changes than other popular FF download add-ons/plug-ins seem to be . Firefox suggest (they would of course ) that if Developers follow their rules, then there will be no or less unexpected issues. How is it other authors seem faster in identifying and avoiding potential issues or just do not seem to have as many issues in the first place as the FF FDM Plug-in has. Is the FDM Plugin not meeting Firefox Development rules or is inflexible to change?
I was recently told by a Mod of this Forum as not being a suitably advanced User to use/try out Firefox Betas BUT NONE-THE-LESS the crashing in FF 39 was known for some weeks and found others (including Usher) and confirmed by me. I have also over recent weeks months reported several potential forthcoming issues. Below are 3 initiated by me
(with the first listed below, Forum readers/members can see FDM Plugin incompatibility with FF39 (Beta) was first reported 7weeks ago by me) The fully working Fix for FF39 Release came out yesterday. (Dev. did tell me that they thought they had fixed it during late Beta stage but a later Beta build broke it again).
Please provide a new compatible plugin for Firefox 39 Beta and 38.0.5 Beta
by dko » Wed May 27, 2015 8:48 am
A "Heads UP" In Firefox 40.0b Candidate Build 2, FDM Plugin Auto Disabled
by dko » Fri Jul 03, 2015 6:21 am
How will Firefox Add-on Extension Signing be dealt with
by dko » Sat Jul 04, 2015 7:20 am
To date no reply has been forthcoming to the last two "important for all Firefox/FDM Users
To be fair with regard to replies, I did ask one (only) of the Mods (who seems to be the fastest and most frequent/likely to reply on Forum) not to reply to me in future as I felt unfairly patronized and poorly spoken to (water under the Bridge)
It would be a kindness if someone on the Dev. Team will tell Users whether, on 11 Aug 2015 (4 weeks time), the FDM Plugin will work with Firefox and also necessary, whether it will be Extension signed by then (or should we seek/rely on other authors' Add-on (Flashgot in my case) to be able to continue using FDM with Firefox after that date.
I will probably be accused of complaining, but all readers please note I am NOT I am mentioning Facts, valid and reasonable concerns, and forthcoming knowns issues which I am sure the Dev. Team are already aware of.
For, all those who do read this Forum, how many more do not? How many get caught out when FDM Plug-ins for Firefox keep falling over when Firefox versions auto update. Already one of two posters have said they are looking elsewhere, and many have queried the apparent preoccupation with FDM5. Are these people complainers and unreasonable Users OR are they reasonable normal Users who have been faster off the mark in actually saying and doing what many others must be wondering by now, more than more frequently, that essentially
"Dev. do not have enough time to Develop and/or fix and what time they do have is a desire to work on FDM5 Alpha not FDM3.9.x. Fixes and associated posts for FDM 3.9.x (version used by almost ALL FDM Users) are delaying and interfering with FDM 5 its development".
BETAS, in this case Firefox BETAs, are of course Released so Developers of associated add-ons or apps can test their apps and be forewarned of potential issues (and for interested Users to have a look if they want) but with FDM Plug-ins these are not being fixed fast enough. In the latest case the fully working FDM plug-in was not available until 1 week after FF39 Release, this essentially, made FF Release owners the Beta testers for FDM Plug-ins which cannot be good (actually they only found out too late. FF Beta users had already previously know of and reported the issue some time before.
It is very easy to slap down or ignore my comments as "another ungrateful User moaning". Hopefully it will be seen as intended as constructive criticism of the way things are currently seem to be going with FDM from a User point of view. It is important that it is remembered that FDM 5 is a long way from Release and FDM 3.* is the [b]ONLY FDM Release around and it is VERY GOOD and worthy of fast (pre-emptive where possible) maintenance.
Example: why is it not already Extension signed this has been known to be coming months ago. I have 30 Add-ons and all but 4 were already Extension signed a month ago. 3 are working not not yet signed (if not signed by ff40 Release they will be blocked by Mozilla). ONLY FDM Plugin has been totally rejected and disabled by Mozilla. This is not good[/u].
Regard to all.