In my opinion, reStyle does not stand a chance in competing with current Stylus and Stylish in terms of in-site styles, these extensions are just way ahead in user experience. I think it could keep the option for using it for these sites - just like userContent.css in Firefox - but it would be used by users who prefer to install more UI styles and maybe just a few content styles.
However, where it does stand a chance is in user interface customization.
For example, the previously highly popular Classic Theme Restorermoved out of AMO and into GitHub because of "Mozilla's hostility" and other arguments against AMO and deprecating XUL.
Similar thing happened with the creation of r/firefoxcss due to the crappy userstyles.org redesign and overall matter of Stylish no longer having UI styles option.
That's where reStyle comes in. It is on AMO, it is semi-automated and it has active development.
I think we should do as much as possible to make using it effortless, including
In my opinion, reStyle does not stand a chance in competing with current Stylus and Stylish in terms of in-site styles, these extensions are just way ahead in user experience. I think it could keep the option for using it for these sites - just like userContent.css in Firefox - but it would be used by users who prefer to install more UI styles and maybe just a few content styles.
However, where it does stand a chance is in user interface customization. For example, the previously highly popular Classic Theme Restorer moved out of AMO and into GitHub because of "Mozilla's hostility" and other arguments against AMO and deprecating XUL. Similar thing happened with the creation of r/firefoxcss due to the crappy userstyles.org redesign and overall matter of Stylish no longer having UI styles option.
That's where reStyle comes in. It is on AMO, it is semi-automated and it has active development. I think we should do as much as possible to make using it effortless, including
What do you think?