3 ms·

Pretty wise comment about web extension support by the main dev here: https://github.com/atlas-engineer/nyxt/issues/2875#issuecomment-1482996905 https://github.

Pretty wise comment about web extension support by the main dev here: https://github.com/atlas-engineer/nyxt/issues/2875#issuecomment-1482996905 https://github.com/atlas-engineer/nyxt/issues/2875#issuecomm...

mikae1 2y ago
> People tend to think in terms of what they could lose, and not in terms of potential gains. It's easier for users to take familiar extensions to a new browser, than having to learn how to use an analog. How is this thinking wise? What are the potential gains and analogs for the end (without having to learn how to code)? What is the analog to Bypass Paywalls Clean and Cookie AutoDelete as an example? If writing new extensions in Common Lisp was so easy, why do they only list two extensions as available?[1] Nyxt and qutebrowser target power users but leave out WebExtension support. I think they'd be a lot more popular if they didn't. [1] https://nyxt.atlas.engineer/extensions https://nyxt.atlas.engineer/extensions
- trenchgun 2y ago
  They do not leave out WebExtension support, they are working to get there: > We're focusing on #2989 since it will allow running Nyxt on macOS and support WebExtensions. https://github.com/atlas-engineer/nyxt/issues/2875#issuecomment-2414725149 https://github.com/atlas-engineer/nyxt/issues/2875#issuecomm...
  - trenchgun 2y ago
    Like, they are working on it right now. Or the prerequisite, to get electron version of Nyxt working. https://github.com/atlas-engineer/nyxt/issues/3544 https://github.com/atlas-engineer/nyxt/issues/3544
- Valodim 2y ago
  Did you interpret the comment as an argument for not having web extensions and recreating the features builtin instead? Because I'm fairly sure it's saying the opposite, even the last you quoted.
Valodim 2y ago
Another interesting one, about whether or not to build on electron: https://github.com/atlas-engineer/nyxt/issues/2989#issuecomment-1584909937 https://github.com/atlas-engineer/nyxt/issues/2989#issuecomm...
deleted 2y ago
[deleted]

mikae1 2y ago

> People tend to think in terms of what they could lose, and not in terms of potential gains. It's easier for users to take familiar extensions to a new browser, than having to learn how to use an analog. How is this thinking wise? What are the potential gains and analogs for the end (without having to learn how to code)? What is the analog to Bypass Paywalls Clean and Cookie AutoDelete as an example? If writing new extensions in Common Lisp was so easy, why do they only list two extensions as available?[1] Nyxt and qutebrowser target power users but leave out WebExtension support. I think they'd be a lot more popular if they didn't. [1] https://nyxt.atlas.engineer/extensions https://nyxt.atlas.engineer/extensions

trenchgun 2y ago
They do not leave out WebExtension support, they are working to get there: > We're focusing on #2989 since it will allow running Nyxt on macOS and support WebExtensions. https://github.com/atlas-engineer/nyxt/issues/2875#issuecomment-2414725149 https://github.com/atlas-engineer/nyxt/issues/2875#issuecomm...
- trenchgun 2y ago
  Like, they are working on it right now. Or the prerequisite, to get electron version of Nyxt working. https://github.com/atlas-engineer/nyxt/issues/3544 https://github.com/atlas-engineer/nyxt/issues/3544
Valodim 2y ago
Did you interpret the comment as an argument for not having web extensions and recreating the features builtin instead? Because I'm fairly sure it's saying the opposite, even the last you quoted.

Valodim 2y ago

Another interesting one, about whether or not to build on electron: https://github.com/atlas-engineer/nyxt/issues/2989#issuecomment-1584909937 https://github.com/atlas-engineer/nyxt/issues/2989#issuecomm...

deleted 2y ago

[deleted]