I think there is a niche for a programmer's browser. I often think something half-way between a web browser and the old Lisp and Smalltalk machines.
Oh, it's called Emacs (being half-serious here)
I cannot continue working on my add-ons
21–30 of 218 posts
Re: I cannot continue working on my add-ons
#22Earlier quoted context omitted.
Oh, it's called Emacs (being half-serious here)
Emacs can already embed a webkit widget, but much more work would be needed to make interaction with the widget "emacsy". At the moment all you can do with it is send JavaScript snippets to it to make it change internal state. It would be great to intertwine this more with Emacs so that e.g. completing-read could be used on the DOM.
Re: I cannot continue working on my add-ons
#23A change like this is how you do that. Good job, Mozilla.
Re: I cannot continue working on my add-ons
#24Isn't Firefox open source? Can't you just fork the project and start your own browser, where all these changes don't get made? Is the real concern about forking the userbase and ecosystem, and the fork won't have the critical user base to become self-sustaining? Edit: added paragraph for clarity.
Re: I cannot continue working on my add-ons
#25Earlier quoted context omitted.
Maintaining a fork of a large browser is extremely difficult, especially for coordinating and merging vulnerability fixes.
Do no other extension developers have this issue?
Re: I cannot continue working on my add-ons
#26If this WebExtensions move makes Tab Mix Plus stop working (I use multi-row tabs extensively) then I will no longer have any reason to continue to use Firefox. I put up with it's poor performance and instability merely for this one feature. Nobody needs a clone of Chrome; we already have Chrome.
Re: I cannot continue working on my add-ons
#27Earlier quoted context omitted.
Maintaining a fork of a large browser is extremely difficult, especially for coordinating and merging vulnerability fixes.
Do no other extension developers have this issue?
Re: I cannot continue working on my add-ons
#28Re: I cannot continue working on my add-ons
#29Incompatible version changes drive away users and developers. The uncertainty that comes along with a planned update in which compatibility is not guaranteed makes us all shy away from developing in that application at all, not just on the old version.
Microsoft always seemed to do a good job at maintaining compatibility over its versions. Most applications that used to run on Windows still do, although there are a lot of exceptions. Python's change to the print statement broke everything, though the fix was easy; most of the time the fix is not easy - and even when it is, nothing works until someone gets around to the fix.
I appreciate the need to move forward, and sometimes you have to break stuff to make it better, but these incompatible changes just destroy momentum. It's a shame to see it happen.
Re: I cannot continue working on my add-ons
#30If this WebExtensions move makes Tab Mix Plus stop working (I use multi-row tabs extensively) then I will no longer have any reason to continue to use Firefox. I put up with it's poor performance and instability merely for this one feature. Nobody needs a clone of Chrome; we already have Chrome.
I also wish chrome would stop prepending http:// everytime i copy an ip from the url bar.