![]() ![]() The Firefox codebase had been partially rewritten to support multiprocessing - this allows Firefox to be a noticeably faster.įirefox was losing a lot of users because it was painfully slow when compared to Chrome, a browser which had multiprocessing from the start. but most importantly, it was not compatible with "e10s" (multiprocess) Firefox.it perhaps gave too much control to developers (making Firefox unstable).had cross platform support, so an extension written for Firefox would mostly work with Chrome (and didn't need a full rewrite)Īlso the legacy API also had some big issues:.However, Mozilla had some very good reasons for doing this, namely, the newer API: Users and developers were furious as some addons simply couldn't be ported over to the newer API. The legacy API gave developers a huge amount of control over the browser which allowed them to completely change how the browser looked and behaved, but the new API was not nearly as capable. ![]() good?īack in Firefox 57 (released late 2017), Mozilla deprecated their older legacy extensions API in favour of the newer WebExtensions API. If you're short on time - skip to But now Google wants to deprecate another API. For example, a phone may have an camera API which allows developers to interact with the camera of that phone. A note to non-technical readers - an API (application programming interface) allows developers to hook into code which has been provided to them. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |