Leaderboard

Months have gone by and I've had to do without Aero Glass for Win 8+ on several work machines. I thought that as long as I made the Title Bar size a bit smaller I could get used to it, and it IS usable but... Ugh, I can't tell you how many times I've clicked the wrong chrome to get to a window that's partly behind another one, just because I can't differentiate one window from the other. Microsoft has made Windows ugly and basic, and by outlasting people who want otherwise have forced it on us. Microsoft will get no love from me for turning something nice into something stupid. Sure, if they had another new system available that would do it all better - but they don't, and they won't. The desktop metaphor with keyboard, mouse, and monitors was - and is - actually very good still for getting work done. But those who understood how to optimize it have fallen by the wayside and now we have Marketeers whose prime function is to "reduce expectations" in charge. Kind like how you can't buy a car that's not a shade of black or earth tone any more. -Noel

Unfortunately things aren't working out with Brave: And I have identified two conditions that may cause a system to lock up; first, running chrome_pwa_launcher.exe from Brave's folder or attempting to use Netflix in Firefox 68 ESR and later. In the second case, it seemed to be due to GetCurrentPackageId, which is a Windows 8 function. Firefox also does exhibit completely different behaviour if tricked into thinking it's on 8.x, as most UI elements don't work in that case. You can disable buggy functions by opening your local copy of a dll in ExportTableTester, and simply changing "XXXXFunction" to "XXXXFunctio_". But Electron-based Visual Studio Code seems to be in a better place. The only thing holding that back is my incomplete implementation of Shell_NotifyIconGetRect. All I have to do for that one is add a chunk of the function (as in a part that is separated from the rest), two subroutines with a chunk each, as well as a couple of new qword values in the data section. Luckily, all of its imports are accounted for in the Vista version. I can't think of a good, modern Chromium browser to try. It seems that they are all undesirable in some way, and their only good purpose is to view heavily-DRMed content that roytam1's or Tobin's browsers can't handle. With the expanded complexity of the project in mind, I have scrapped the idea for the tutorial. I am working on alternative means of distribution for the kernel extensions. Please contact me for more information.

Well said, bro. Windows 10 is a pile of $hit by any measurement. AeroGlass is the only thing that makes it tolerable as far as I am concerned. Nothing will ever make it a truly good product. The Redmond Retards are losers that have completely lost their way and couldn't find their a$$es using both hands. All they produce in garbage now. Their nonstop streak of failures started with Windows 8 and there is no end in sight to their stupidity.

... Being slightly pedantic, but the URL query parameter should be: disable_polymer=1 Be that as it may, the query no longer works for the main YT homepage, https://www.youtube.com/?disable_polymer=1 (classic style is not restored), but still works for independent video URIs: https://www.youtube.com/watch?v=W-z7hoEWaH4&disable_polymer=1 A Google-bot SSUAO however does, as of this writing, work in both cases... [I'm using just "Googlebot/2.1 (+http://www.googlebot.com/bot.html)"]

Ah, I follow. I have mixed feelings about e10s. In my experience running single process does not fare awfully well with multiple hefty CSS/js tabs. That was really my biggest issue with Pale Moon in the past. (that and there not a being a single modern password manager developed specifically for it, which was rather sad considering its extensive extensions library otherwise) On the other hand, EIGHT default content processes is rather insane. I've really taken a liking to running 2 content processes. It holds up in the long haul without crashing the browser, and RAM usage is reasonable. Not light, but reasonable. Have you tried Auto Tab Discard and MySessions btw? Those extensions are absolutely essential for me. I'm happy to report 78 isn't insane like I was expecting, CSS can really work its magic on the interface. But I'm hoping Alex will do something about that megabar to set it apart from mainstream ESR. I'm sure its at least on his mind with other users on Reddit orbiting him about the topic

Well I loved ESR 60 because I could still allow single-process without the use of environment variables. It ran quite solid. It was modern enough to like using with an OS like Windows 8, but it was customizable using userChrome.css to make it more like a modern-looking classic browser. I liked ESR 68 too, but for quite awhile when saving a file on Windows 8, the browser would freeze for as much as twenty seconds while creating a new folder in the process. This made me start really wanting to revisit ESR 60. It was just so trouble free. I am also using Waterfox Current right now, with good results, and it's on ESR 68 right now. In fact the file/save issue seems to have been remedied for the most part. But in September, Alex will rebase on ESR 78. At that point, e10s CANNOT be disabled AT ALL. Plus I will have to hope that Alex will reverse the new address bar simplifications.

What are you missing from ESR 60 if you don't mind my asking? I've mostly noticed old about:config prefs disappearing, but very few changes on the outer shell. I'm on 68-based WF Current atm and am rather comfortable with my userChrome styling. I even tested ESR 78 with an updated version of the same script and replicated the same look almost to the letter. But I don't think customcssforfx is quite optimized for 78 yet having suffered some slight padding issues, that and the megabar looking a bit... Less than stellar. Makes one appreciate ESR since it gives us tinkerers time to patch up Mozilla's quirkiness before it's dropped in our lap. I'll hold on lighting my torch until/if userChrome is completely depreciated. Presumably Waterfox would reverse such a change though, even going so far as to restore some styling properties to allow extension-based themes again. SR is actually working to port their DeepDark from Classic to Current, more info on their Twitter. Nevertheless reading this makes me awfully curious to grab a copy of 60 and test it to compare changes since (bit of an IE7 / FF3 vibe going here)

That really doesn't seem his style. It's the same thing every time an update breaks aeroglass. Crickets, lots of waiting, People in the forums keep freaking out, asking about an update, demanding bigmuscle address their concerns. He ignores them all. Then a month or two later an update drops. Then a few months later Microsoft breaks it again. Rinse/Repeat. Sure it'd be nice to get faster updates, but I think I'm only in this for $10 at this point. I think I bought $5 license one, used it on 2 pc's. Then I bought a new one and didn't want to wait for 30 days to reuse a deleted key, so paid another $5. I don't feel like he owes me a lot for $10. Especially when i've been using it for years. I tried the only other competition I'm aware of (Windowsblinds) but I didn't like it.

We have absolutely no idea how long it takes. It could take a full week or it could take 12 hours. We have no idea. This is what I mean with speculation. Did he ever share any info regarding what it takes to update? How big of a chance is there even that this can cause bugs? And if a lot of bugs can be there does he have a very solid way of fixing these with some kind of debugging software perhaps? And having an application without bugs is pretty logical yes. I don't see how that changes anything in this particular situation. We still don't know how much testing is actually done each update. Also, the application is not free. If you can pay for it how is it free? Unless you can pay for the application and your payment changes nothing. You would have the exact same feature set with no downsides. That's what we call an donation. This is clearly a trial/demo. Anyway, I appreciate what BigMuscle is doing because I think this isn't an easy task. He is probably doing this for himself and a small group of people. At least I think so. Like I said, I'm speculating just as much as all of you. I just wanted to get this off my chest. I understand most of the people present on this section of the forum will probably disagree with me or think I don't appreciate what he has created. There is no need for me to make everyone uncomfortable (hopefully I didn't) for a long period of time with replies going back and forth. I really don't want that. The world is already in a full epidemic at the moment. So I just wanted to share what I think, considering this thread was somewhat steering towards the topic. So yeah, be safe and sorry for waltzing in here with my skepticism. I'm just a user like all of you and I can be a bit harsh with what I say. Good day everyone! EDIT: Thinking about it a bit more, I think I might've been a bit too harsh/distrustful. See it as simple food for thought for now, or something. I'm probably overthinking things.

FWIW, I've built the same multi-monitor layout on 3 different desktop systems so that I don't have desktop reorganizational issues when I RDP from one system location into another. Still to this day sometimes Visual Studio will swap its panels from the left to the right side monitor. With Windows 10 usually the icons end up okay, though, on the central (larger) monitor. Honestly, I think Microsoft should have delayed or just canceled Win 10 2004 and kept working on stabilizing and tuning 1909. This all-too-often 6 month turnaround that breaks everything that's not vanilla Microsoft, like Aero Glass for Win 8+, is just ludicrous. -Noel

@Dibya: I think targeting "fast paced" technology such Browser is impossible... it's always employ cutting-edge ones (virtualization, memory management, MT) thats beyond XP scope. If any it would be more and more "disabled features" if it allowed to run on XP. BTW I think I'd abandon patchless idea.. hooksubsystem itself is hackish and might be restrictive, I can't use redirection manifest either as having another "kernel32.dll" often trigger DEP. Not to mention I get chicken-egg situation as my dll (the xp kernel32 part) is just forwarder not even wrapper, the redirection manifest would meant any dependencies (dll) would call the fake kernel instead of just the executable.