Winapp2.ini

that doesn't sound like a difficult change to make to the debugger now that the infrastructure for alphabetization and numbering checks is. I'll work on expanding their reach to the exclude keys soon

That's probably a question for the devs. Possibly even a bug? It's weird to me that you'd see inconsistent behavior with ExcludeKeys given the same formats.

I believe back_track is referring to the alphabetization of the entries in the CCleaner application pane, where it prioritizes entries with spaces over those without. (eg. Origin* comes after Origin Installers*, but based on the bottom set of entries, I imagine that Origin * would precede Origin Installers* ). Changing entry names however restores their disabled state because CCleaner does not detect that an entry's name has been changed and instead detects it as a new entry, requiring the end user to reconfigure their settings after any name changes (via the UI or via ccleaner.ini)

It does appear the application no longer works. It does still generate files if run, however, despite its non-working state. Tested with the version found on FileHippo. I'm all for removing it since any reasonable user would probably have uninstalled the non-working application (Soluto themselves seem to have moved on to some slightly different business model using the same name)

I'll do an audit for CCleaner overlap after the upcoming refactor Also for the interested, I've recently updated WinappDebug with some nifty new features (including checking alphabetization of FileKeys, RegKeys, and entries, numbering for FileKeys, RegKeys, Detects, and DetectFiles, and some checks to make sure RECURSE and REMOVESELF entries are formatted properly) It also spits out the number of entries in the file at the end. Running it on the current release is a doozy... (Side note: that number drops really quickly while actually fixing the errors, assuming you remember to check your numbering..... - it also doesn't really handle numbers too well either.. )

A bit late but Stylo is ready for testing in nighty... https://blog.nightly.mozilla.org/2017/07/25/stylo-is-ready-for-community-testing-on-nightly/ in my experience, very few issues with it. No generally perceivable difference in rendering or performance (yet) QFEN: 17: https://ehsanakhgari.org/blog/2017-07-28/quantum-flow-engineering-newsletter-17 18: https://ehsanakhgari.org/blog/2017-08-04/quantum-flow-engineering-newsletter-18 19: https://ehsanakhgari.org/blog/2017-08-11/quantum-flow-engineering-newsletter-19 TWIF: 21: https://blog.nightly.mozilla.org/2017/08/02/these-weeks-in-firefox-issue-21/ 22: https://blog.nightly.mozilla.org/2017/08/16/these-weeks-in-firefox-issue-22/ PEN: 9: https://dolske.wordpress.com/2017/07/24/photon-engineering-newsletter-9/ 10: https://dolske.wordpress.com/2017/08/01/photon-engineering-newsletter-10/ 11: https://dolske.wordpress.com/2017/08/04/photon-engineering-newsletter-11/ 12: https://dolske.wordpress.com/2017/08/13/photon-engineering-newsletter-12/ Photon is pretty near complete at this point WebRender Newsletter #1: https://mozillagfx.wordpress.com/2017/08/16/webrender-newsletter-1/ I've been testing WR for some time, still pretty buggy, but lots of promise. 64 Bit is now the default on 64bit windows: https://blog.mozilla.org/firefox/firefox-64-default-64-bit-windows/ There's also some new test pilot experiments: https://testpilot.firefox.com/experiments?utm_source=testpilot-dev

​ ​ ​ this page: https://hardware.metrics.mozilla.com/#detail-browser-share-os-32-64 suggests that around 22% of active firefox installs are on 32bit OS' (thus cannot even install 64bit software), so I don't think Mozilla will be dropping 32bit support anytime soon. As you said, this is more geared towards migrating 32bit fx on x64 hardware to 64bit fx. I don't think they'll be extending the 52 ESR beyond its expiration date of August 2018 ​ ​

Based on the discussion there, seems to be primarily a stability choice to move to 64bit. ​ Moving to 64bit alone doesn't carry (m)any performance enhancements, but it does allow for better security (ASLR) and fewer out-of-memory situations (64bit applications use by default more memory due to the larger register size required by 64bit which is a bit of a regression, but the upper limit of total memory use for 64bit apps is much higher than 32bit ones) Also, PEN #9: https://dolske.wordpress.com/2017/07/24/photon-engineering-newsletter-9/ Edit: ​Firefox Roadmap for Flash End of Life: ​https://blog.mozilla.org/futurereleases/2017/07/25/firefox-roadmap-flash-end-life/ ​ Stylo is Reader for Testing in Firefox Nightly: https://blog.nightly.mozilla.org/2017/07/25/stylo-is-ready-for-community-testing-on-nightly/ Make Firefox Better With Pioneer: https://medium.com/firefox-context-graph/make-firefox-better-with-pioneer-10c82d0f9301

Migrating 32bit Firefox installs on 64bit Windows to 64bit installs: https://groups.google.com/forum/#!topic/mozilla.dev.platform/hlCGG_Hib1w Switching to TaskCluster Windows Builds on July 26th 2017: https://groups.google.com/forum/#!topic/mozilla.dev.platform/pOSncDUVids PEN 8: https://dolske.wordpress.com/2017/07/05/photon-engineering-newsletter-8/ TWIF 20: https://blog.nightly.mozilla.org/2017/07/19/these-weeks-in-firefox-issue-20/ QFEN: 15: https://ehsanakhgari.org/blog/2017-07-07/quantum-flow-engineering-newsletter-15 16: https://ehsanakhgari.org/blog/2017-07-21/quantum-flow-engineering-newsletter-16 ​ ​

​ I miss that blue theme.

Some updates... QFEN: 11: https://ehsanakhgari.org/blog/2017-06-02/quantum-flow-engineering-newsletter-11 12: https://ehsanakhgari.org/blog/2017-06-09/quantum-flow-engineering-newsletter-12 13: https://ehsanakhgari.org/blog/2017-06-16/quantum-flow-engineering-newsletter-13 14: https://ehsanakhgari.org/blog/2017-06-23/quantum-flow-engineering-newsletter-14 TWIF: 19: https://blog.nightly.mozilla.org/2017/06/21/these-weeks-in-firefox-issue-19/ PEN: 5: https://dolske.wordpress.com/2017/06/08/photon-engineering-newsletter-5/ 6: https://dolske.wordpress.com/2017/06/15/photon-engineering-newsletter-6/ 7: https://dolske.wordpress.com/2017/06/22/photon-engineering-newsletter-7/ Date/Time inputs enabled on Nightly: https://blog.nightly.mozilla.org/2017/06/12/datetime-inputs-enabled-on-nightly/ Firefox Focus on Android: https://blog.mozilla.org/blog/2017/06/20/firefox-focus-new-to-android-blocks-annoying-ads-and-protects-your-privacy/ An Inside Look at Quantum DOM Scheduling: https://hacks.mozilla.org/2017/06/an-inside-look-at-quantum-dom-scheduling/ Introducing HumbleNet: https://hacks.mozilla.org/2017/06/introducing-humblenet-a-cross-platform-networking-library-that-works-in-the-browser/ Designing for Performance: https://hacks.mozilla.org/2017/06/designing-for-performance-a-data-informed-approach-for-quantum-development/ Powerful new additions to the CSS Grid Inspector: https://hacks.mozilla.org/2017/06/new-css-grid-layout-panel-in-firefox-nightly/

TWIF 18 https://blog.nightly.mozilla.org/2017/06/06/these-weeks-in-firefox-issue-18/ Activity Stream Newsletter June: https://mail.mozilla.org/pipermail/firefox-dev/2017-June/005463.html

Very strange, not sure what happpened but will fix. Likely an issue with GitHub formatting and copy/paste

https://github.com/MoscaDotTo/Winapp2/issues/89 I issued a pull request that broadly extends support to all the Chrome variants across non-google-specific Chrome entries (consequence of this report that some were missing Chromium support) I didn't check these against whether or not the paths actually exist, but I think it's a safe bet that they do.

All CSS properties supported by Gecko now supported by Stylo: https://groups.google.com/forum/#!topic/mozilla.dev.servo/9jZtdX1pAQA Race Cache with Network: https://groups.google.com/forum/#!topic/mozilla.dev.platform/fvCmc6kR9Uk PEN #3: https://dolske.wordpress.com/2017/05/30/photon-engineering-newsletter-3/ PEN #4: https://dolske.wordpress.com/2017/05/31/photon-engineering-newsletter-4/ Goodbye PNaCL, Hello WebAssembly! https://blog.chromium.org/2017/05/goodbye-pnacl-hello-webassembly.html including this because Mozilla is heavily involved in WebAssembly and one of its precursors, asm.js. Hooray open standards! Aurora gets swapped out for Nightly on the Play Store: http://www.androidpolice.com/2017/05/30/mozilla-replaces-firefox-aurora-play-store-listing-firefox-nightly/

Are We Slim Yet is dead, all hail are we slim yet http://www.erahm.org/2017/05/25/are-we-slim-yet-is-dead-all-hail-are-we-slim-yet/amp/

Agreed

TWIF 17: https://blog.nightly.mozilla.org/2017/05/25/these-weeks-in-firefox-issue-17/ Also, the movement of DevEdition users to the Beta Channel will happen Soon™

https://github.com/MoscaDotTo/Winapp2/issues/87

Firefox 54 may see 4 content processes on by default (up from 1): https://bugzilla.mozilla.org/show_bug.cgi?id=1367244 the number of content processes can be modified by the user in about:config with dom.ipc.processcount or through a panel in the preferences (I've seen mockups but this module hasn't yet landed in Nightly) PEN 2: https://dolske.wordpress.com/2017/05/23/photon-engineering-newsletter-2/ Preview Form Autofill in Nightly: https://blog.nightly.mozilla.org/2017/05/23/preview-form-autofill-in-firefox-nightly/

Firefox 53.0.3 released: https://www.mozilla.org/en-US/firefox/53.0.3/releasenotes/

Photon Engineering Newsletter #1: https://dolske.wordpress.com/2017/05/18/photon-engineering-newsletter-1/ Data Science is hard: Anomalies pt 3: https://chuttenblog.wordpress.com/2017/05/18/data-science-is-hard-anomalies-part-3/ QFEN 10 https://ehsanakhgari.org/blog/2017-05-19/quantum-flow-engineering-newsletter-10

TWIF 16: https://blog.nightly.mozilla.org/2017/05/10/these-weeks-in-firefox-issue-16/ Some mockups for Photon on Android: http://imgur.com/a/sNBkR QFEN #9: https://ehsanakhgari.org/blog/2017-05-12/quantum-flow-engineering-newsletter-9

52 ESR should still work for another year

The WebExtensions API is meant to replace the current addon model, but they don't plan to turn it on by default until it has reached feature parity with Chrome's API in order to make it easier for chrome extension developers to port their extensions to firefox I believe they're moving the front end UI code from XUL to html/css (part of Quantum DOM?) and in doing so removing a lot of customization. I think userchrome.css will still be functional, I think more advanced themes that rely on XUL functions will not be.