|
|
Subscribe / Log in / New account

GNOME Shell to support a "classic" mode

GNOME Shell to support a "classic" mode

Posted Nov 23, 2012 9:35 UTC (Fri) by nix (subscriber, #2304)
In reply to: GNOME Shell to support a "classic" mode by ebassi
Parent article: GNOME Shell to support a "classic" mode

Oh no. Firefox extensions? FF's treatment of its extensions would be the reason I stopped using Firefox after nearly a decade of using nothing else: the extensions became useless because FF repeatedly broke all its extensions every few weeks, nobody could keep up, and eventually all the extensions I relied upon to keep FF usable fell into disrepair (I hear it's better now, but it's too late, I moved away). Chrome, with an actual extension API rather than a big ball of mud, has never broken an extension for me in a year and a half of use with dozens of extensions, despite massive progress in that time.

So if GNOME is modelling its extension API on FF's, it's not a good sign. If it models it on FF's except treats it like an API and doesn't break it at the drop of a hat, that might work better.

(Again, I don't really know how Emacs has avoided implosion despite using the same 'big ball of mud, everything is available' approach as FF extensions do. I suspect it is simply treating its interfaces like a programming language designer would, i.e. extremely conservatively, taking *decades* to deprecate *anything*, so by the time your extension moves from using deprecated interfaces to breaking because they're removed, the app itself is too obsolete for anyone to care about it anymore. It only just broke old-style backquote, for instance, and that started emitting deprecation warnings something like fifteen years ago.

Perhaps if people would consider that they are kicking all their users every time they deprecate a stable interface it might help. I understand that Emacs developers ritually cut off and sacrifice a body part to the cons gods every time they intentionally break anything that external Lisp is relying on :P That attitude might help too, but it seems to be almost unique in the 'just break it dammit' free software community right now.)


to post comments

GNOME Shell to support a "classic" mode

Posted Nov 23, 2012 9:51 UTC (Fri) by ebassi (subscriber, #54855) [Link] (3 responses)

Again, I don't really know how Emacs has avoided implosion despite using the same 'big ball of mud, everything is available' approach as FF extensions do.

because you're obviously ignoring the fact that the emacs users are putting up with a big ball of elisp with obscure commands that require three keyboards to actually be used successfully, which means that they are capable of getting out of the mess by themselves, and they'll probably enjoy doing so - whereas people installing Firefox and GNOME extensions are much more likely not to be software developers or humungous geeks.

GNOME Shell to support a "classic" mode

Posted Nov 23, 2012 19:37 UTC (Fri) by nix (subscriber, #2304) [Link] (1 responses)

The thing is -- generally there isn't a mess. Not even if you load a dozen weird things that have probably never been loaded simultaneously before in the history of the universe. That's what's odd...

GNOME Shell to support a "classic" mode

Posted Nov 30, 2012 20:20 UTC (Fri) by njs (subscriber, #40338) [Link]

And perhaps Gnome 23 will have the same property... ;-)

(Also emacs' UI is pretty flat and decoupled to start with, since it consists mostly of keybindings. It's much easier to merge 10 extensions' keybindings than it is to merge 10 extensions' arbitrary fiddlings with status bars, menus, etc., and those things change from release to release too.)

GNOME Shell to support a "classic" mode

Posted Nov 23, 2012 19:39 UTC (Fri) by nix (subscriber, #2304) [Link]

btw, it is clear from your sarcastic response that you too are not interested in figuring out how it is that some software can be apparently tightly coupled and yet not break all the time, despite working on software with the former property yourself. Curious. Apparently poking inaccurate fun at Emacs is more interesting than thinking about it.

GNOME Shell to support a "classic" mode

Posted Nov 23, 2012 10:18 UTC (Fri) by dlang (guest, #313) [Link]

you may want to notice that the chrome extensions API doesn't allow some things to be done that are done in firefox (this is one of the reasons noscript doesn't exist for chrome)

Firefox also has an extensions API, and things that use that are very stable. But Firefox didn't start with an explicit API, instead extensions are allowed to muck with anything in the browser, and ones that do are extremely sensitive to any changes in the browser (potentially including compile options)

as in everything, there are tradeoffs


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds