3 ms·

Saka keys on Firefox has been a suitable replacement for me.

by gfodor 9y ago

nindalf 9y ago
Not me personally, but there will always be a vocal minority who will complain about having their workflow broken. Any replacement will be missing some critical feature. For a person affected by this, it is a painful experience having their entire workflow broken so they resort to dire warnings on forums such as this one ('Firefox is finished without <my niche plugin>'). In this case, I think Firefox made a good choice in modernising the codebase and the extension APIs. In 2 years we'll find out if the vim people were right or they were indulging in hyperbole.
- iterati 9y ago
  Less "dire warnings on forums" and more "slow development pace for required pieces to make my workflow even possible again". Here's an issue opened June 9 that hasn't been addressed by the Mozilla team and hasn't had any updates in a month: https://github.com/cmcaine/keyboard-api/issues/1 https://github.com/cmcaine/keyboard-api/issues/1 Here's the request for a better keyboard API (referenced in the above) that's been open for over 2 years with no end in sight: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 I'm sure the new FF is going to make some users happy, but as you said, having your workflow broken is quite painful, and the Mozilla team has known about this for years but still not made the upgrade path bearable.
  - DiThi 9y ago
    > with no end in sight Except an already developed patch and proposal that needs some time from the main devs to be reviewed. For a long time they were very busy making FF bearable for 90% of the users. Now that it's released we'll see if this issue is as stuck as you imply.
    - iterati 9y ago
      I guess we will, but with the slow pace that any of this was (not) done over the last number of years, I'm not holding my breath.
CaptSpify 9y ago
eh... I use it now, and it's OK. It's missing a ton of features that Vimperator had, and it will likely never get them.

Saka keys on Firefox has been a suitable replacement for me.

by gfodor 9y ago

Saka keys on Firefox has been a suitable replacement for me.

Not me personally, but there will always be a vocal minority who will complain about having their workflow broken. Any replacement will be missing some critical feature. For a person affected by this, it is a painful experience having their entire workflow broken so they resort to dire warnings on forums such as this one ('Firefox is finished without <my niche plugin>'). In this case, I think Firefox made a good choice in modernising the codebase and the extension APIs. In 2 years we'll find out if the vim people were right or they were indulging in hyperbole.

iterati 9y ago
Less "dire warnings on forums" and more "slow development pace for required pieces to make my workflow even possible again". Here's an issue opened June 9 that hasn't been addressed by the Mozilla team and hasn't had any updates in a month: https://github.com/cmcaine/keyboard-api/issues/1 https://github.com/cmcaine/keyboard-api/issues/1 Here's the request for a better keyboard API (referenced in the above) that's been open for over 2 years with no end in sight: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 I'm sure the new FF is going to make some users happy, but as you said, having your workflow broken is quite painful, and the Mozilla team has known about this for years but still not made the upgrade path bearable.
- DiThi 9y ago
  > with no end in sight Except an already developed patch and proposal that needs some time from the main devs to be reviewed. For a long time they were very busy making FF bearable for 90% of the users. Now that it's released we'll see if this issue is as stuck as you imply.
  - iterati 9y ago
    I guess we will, but with the slow pace that any of this was (not) done over the last number of years, I'm not holding my breath.

CaptSpify 9y ago

eh... I use it now, and it's OK. It's missing a ton of features that Vimperator had, and it will likely never get them.