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

Something that drives me nuts is how stateful about:config options are. If you set them once, either through about:config or using a user.js, they will stay like that forever unless you explicitly unset them.



Wow, totally disagree. Instant-persistent-on is a much better and more intuitive experience than old "Cancel, Apply, Ok" settings paradigms.


Oh no, persistency is great. But the problem is how non-functional their implementation is.

Say I write a user.js file with a few options. I can't have the typical dotfile model, where removing options from this file will lead to defaults on the next run. I need to unset them. Explicitly.

Thus, using a dot file to set up Firefox (user.js) is incredibly clunky and people don't use this much.


Firefox actually retains all the default values for the preferences, and bolds the ones that are set to non-default values.


If you could export the diff, or import settings, that would be adequate.


Disagree strongly.

There exist good cases for instant persistence, like switching themes when you want to see the effect immediately before you decide.

Other than that it's really nice to be able to cancel everything when you realize you've messed up.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: