LOL, stop being sheep and do your own thing. I am talking about you MS and your stupid childish kindergarten block interface of WIN 10 and all the psychophantic followers who are embracing this flat design paradigm. It’s the core functionality underlying it which should remain constant. The user interface should be totally customizable ( all aspects). I honestly don’t understand the need to screw up the interface for some dreamed up UX vision. I don’t know what others think about the Australias interface (nor do I really care), but I effing hate it with vehemence. Why I use Waterfox? Well, let’s just add one more extension I absolutely prefer (Classic Theme Restorer). Now You: do you use Waterfox? What is your main reason for using it? The version will be different but the browser won't change. Waterfox Classic will continue to support these, and users who run the browser don't really need to do anything at this point. Others liked the idea of running a browser without Telemetry, or need support for certain NPAPI plugins. Waterfox has a loyal following some picked the browser because they want to continue using legacy add-ons that Firefox does not support anymore. The about page does highlight the branch of the browser in the case of the screenshot above, it is Waterfox Classic that was upgraded to the new version. The latest Waterfox Classic version released displays as 2019-10 on the about page already. ![]() Instead, it will introduce new features and options that the classic version does not support. While not mentioned explicitly in the blog post, it is likely that Waterfox Current won't support all the features of Waterfox Classic. Waterfox Current on the other hand will keep up "with the modern web". The core difference between the two is that Waterfox Classic will retain classic functionality but will receive bug and security fixes only. It is the "modern, feature updated branch". Waterfox Current is the second version of the browser. ![]() There are no plans to retire this branch, and is going to be actively maintainted, the same as current. The developer of Waterfox has no plans to retire this branch according to a new blog post on the Waterfox blog. The classic channel, called Waterfox Classic, is the legacy branch of the web browser that will continue to support older standards. Additionally, Waterfox will have two separate channels going forward. The next releases of Waterfox after 56.2.14 and 68.0b1 will follow the new versioning scheme already. The new versioning scheme of Waterfox is YYYY-MM-X with Y=year, M=month, and X=hotfix, whereas the old versioning scheme used X.Y.Z with X=main version release, Y=feature release, and Z=hotfix. The organization wants to release a new version of the Firefox web browser every four weeks instead of the current scheme that has a new release ready in about six weeks on average. Mozilla announced in October 2019 that it would speed up the Firefox release cycle. Waterfox continues to support (some) NPAPI plugins, comes without Telemetry, and bootstrapped add-ons. That's really the only way to ensure everything works (aside from owning physical hardware that is capable of booting into said version).The Waterfox browser is based on Firefox code but there are notable difference between the two browsers. Here's the log output: 09:54:11.451 waterfox Mozilla has caught an Obj-C exception : unrecognized selector sent to instance 0x136655880]Īll occurrences of NSImage drawInRect should be removed to ensure compatibility with MacOS 10.8.5.Įdit: I highly recommend you set up a VM with an older version of MacOS for testing purposes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |