Hacker News new | past | comments | ask | show | jobs | submit login

> 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




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#issuecomm...


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


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.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: