NotHereToPlayGames

You were the only one with your panties in a bunch

Skins have zero "perceptable" difference on GUI load time. The differences we are talking about are only 0.006 to 0.011 seconds. The human eye cannot process visual data faster than 60 frames per second. 0.006 seconds is basically 167 frames per second and 0.011 seconds is basically 91 frames per second. The GUI load time difference needs to exceed 0.017 seconds before the human eye can process the visual difference. And that would be the eyesight of a professional baseball player that can see the spin of a 90mph fastball. The rest of us are lucky to detect 40 frames per second and that puts the GUI load time difference way up at 0.024 seconds - more than TWICE our worst-case measurement. For reference, video data is generally 24 frames per second and while there has been Massachusetts Institute of Technology studies that the brain can subliminally respond to one frame of those 24 frames per second, the eyes do not "see" that frame. Our GUI load time difference has to hit 0.042 seconds to be equivalent to 24 frames per second -- 4 to 7 times higher than they are at! Skins have zero "perceptable" difference on GUI load time - it's all Placebo Effect. And no effect on performance overall.

It's not installed according to here -- https://www.math.uh.edu/mathonline/JavaTest/JavaTestPage.htm (this test in v11 where browserspy incorrectly claims java is installed, when I close v11 then I will test again in v13.5). edit: same thing in v13.5... browserspy claims it is installed, the JavaTestPage says it is not...

"Enabled" and "leaking/active" are two different things. Do we have a way to test if P2P connections are being made?

Here's a comparison of en_skin / iframe / skin (which I'm calling "skinless") to dark theme to xp theme. These are GUI Load Times as timed by PassMark AppTimer - timed twelve GUI load times per theme. The only thing I'd really conclude definitively is that a dark theme INCREASES your GUI load time. The XP Theme was the only skin that didn't have its slowest load times above 0.5 seconds. I suspect that if I ran 100 instead of just 12 that "skinless" and "XP" would basically diverge into a dead-heat tie but that "dark" would still come in dead last.

Where are you seeing this from?

v13 build 2206 (my v13), v13 build 2250 (Humming Owl's v13), and v13.5 build 1030 (and I assume build 1060) are all the same exact Chromium engine => Chromium 86.0.4240.198.

On ALL of my machines! From a single-core Sempron 3100+ running x86 SP2 (I currently have Win 2000 on it but still hunting for drivers) to two Core 2 Duo's both on x86 SP3 to one Core 2 Quad on Win10-LTSB/Win7/XP-SP3 triple-boot to one i7-4770 on XP x64. But it's not "every" morning - but 1 morning in 5 is waaaayy toooo much! Especially when v11 does everything I've ever asked it to do!

As far as "squeezing the turnip" goes, the next step towards axeing all remnants of unnecessary code and shrinking down to as small as possible would be to remove any-and-all code pertaining to "dark mode" and perhaps even intentionally crash if end-users attempt to restore it by putting puzzle pieces in from different puzzles.

The next planned v13.5.x rebuild is to update from 13.5.1030 to 13.5.1060. But it's a gigantic undertaking to have to do all of these changes every time the Chinese updates their build. v13.5 locks up on my computer the first launch every morning so it hasn't been a huge priority because I don't use it because of those lockups. Will .1060 resolve that? Unknown as I have a gigantic preference towards v11. With v12 riding its coattails.

Talk about irony that this hit the Unread Content list of links for this morning. I resurrected an ancient AMD Sempron 3100+ from the grave a couple months back in order to test 360Chrome on XP x86 SP2. Ran a few tests and concluded ZERO benefit to keeping x86 SP2 around. Tried (in vain) to get four different forks of Chromium OS running on this ancient beast - CloudReady, FydeOS, ArnoldTheBats, and NayuOS. Every single one will boot up to their logo screen then ends up in an infinite loop of reboot cycles only getting as far as the logo screen. I can still probably figure it out but opted to save that project for a later day. Literally ~40 minutes before stumbling into your post, I have Windows 2000 installing on that AMD Sempron 3100+

I could find ways to "patch" but then I would be accused of spreading viruses because those patching mechanisms would throw flags in "anti-virus" programs. And it's not really worth the time, effort, and hassle for such a tiny user-base.

That will not increase our numbers. We know that because Humming Owl does "advertise" outside of MSFN. Our "breed" isn't 'dying', it's already "dead". "Older NT-Family OSes" is simply NOT something where we have X number of folks today but X+1 tomorrow. We are not "dying", we are "dead". We are using these "Older NT-Family OSes" from the grave, not from some new underground waive of the future bringing in new recruits with each new generation of computer user. The "general populous" has ZERO interest. LESS than ZERO. Doesn't bother me, I like being "unique", "the same as everyone else".

Truth be told, I think 360Chrome has already reached its PEAK. Even with official Pale Moon axing Mypal, NM28, and BNavigator, there hasn't exactly been any newcomers to the NT-Family Browsers sub-forums. Just the same ol' same ol' "holdouts" that pledge an allegiance to Mozilla and cross their fingers that Roytam can get Basilisk/Serpent to do what 360Chrome has already demonstrated that it can already do. We're at the point where even if the next 360Chrome rebuild printed bitcoins, we still couldn't add to the number of people that use it. Though the same goes for Roytam's builds from what I can see - we haven't added new users, we just keep rolling along with the same exact user-base we basically had two years ago.

That is what is called a "Placebo Effect". I timed with and without skin and the skin does not affect load time or render time. Pure Placebo.

Because it would require the standard and the ungoogled resources.pak which is just over 5 MB for v13.5. The way that I "was" doing my dark theme would have require another resources.pak. Still digging into that and should be able to remove that resources.pak but there is no way around not having a standard and an ungoogled. And you wouldn't catch me using standard if my life depended on it. While other users would say that same thing about ungoogled because it forces you to manually install extensions as opposed to visiting the Chrome Web Store.

I was leaning in that direction also, once I realized how much file size storage was going to be required.

The drawback is going to be file size. !'m 90% done with the v13.5 changes and its file size increased from 70 MB to 88 MB. So that should put v13 at an increase from 69 MB to approximately 87 MB, v12 at an increase from 76 MB to approximately 94 MB, v11 at an increase from 67 MB to 85 MB, plus however I can puzzle SP2 versus SP3 and we're looking at somewhere around 350+ MB for an "all-in-one" 360EE. If users are downloading all four versions anyway, then we might as well make it one large download. The file names will clearly indicate what belongs with which so users could always remove items they have no use for. Another drawback could be extensions that work in v13/v13.5 but do not work in v11 - I do not know if this exists, to be perfectly honest, as all eight of the extensions that I use work in all four of my rebuilds. But part of my "all-in-one" end-in-mind is ONE profile that you can run in any one of my four rebuilds.

lol, I'm aware. That was just a quick-and-easy mockup using nothing but spreadsheet cell borders because my first copy-and-paste into the forum reply box didn't "stick the landing".

I rarely (only once in the last two years) log into my Win10 of my triple-boot setup. My Win10 partition is 1607 LTSB. Does anyone know if the DNSAPI.dll hack needs performed on LTSB? Also, I'd be curious to see the list of Windows services that you lock down.

Regarding Dev Tools reverting to Chinese in versions newer than v13 build 2206 -- new incognito window Dev Tools will also always revert to Chinese. Exists in original Chinese so carries over to anybody-and-everybody that rebuilds anything newer than v13 build 2206. Have not found any way to hard code default to English.

I've deleted DcBrowser. Don't have any use for it, sorry.

And I knew that was the icon you were hiding, I would have bet money on it

Agreed. The MSFN crowd really is very unique. And extremely rare. We really are very tiny in the grand scheme of things. I knew of MSFN long before becoming a member. And it was official Pale Moon dropping support for XP that landed me here as a member. But I feel like I was the ONLY person that landed here when official Pale Moon dropped XP. Fast forward and we saw what offical Pale Moon continued to do for XP. But did people flock to MSFN? Nope, we had two new members, maybe three. But for a day or two and they're not here anymore. I may be overexaggerating but you can follow that logic. 25 million or so XP users worldwide and you only need to take one shoe off to count all of the XP users active here at MSFN.