Leaderboard

it consists "MailNews" and "Borealis" (a browser-only Seamonkey application forked by (removed due to request))

@Monroe It stands for Binary OutCast Navigator (browser itself is the Navigator though, as pointed out by roy in the next post, not sure what MailNews exactly is, and Binary Outcast is its creator), it's basically a SeaMonkey fork (made by Matt Tobin as far as I know though I might be wrong), so no, if you're already using Basilisk, then there's really no point in using BOC as well.

New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20181229-83cd9661c-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20181229-83cd9661c-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win32-git-20181229-83cd9661c-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win64-git-20181229-83cd9661c-xpmod.7z Official repo changes since my last build: - Revise lifetime management of IntersectionObservers. (c9d920e9c) - Intersection ratio should be 1.0 for zero-area intersections. (107a68cb1) - Use targetFrame->GetRectRelativeToSelf() as the initial intersection rect. (0626e1cef) - Map intersectionRect to the coordinate space of the target document. (6cfd7509c) - Use content area as the intersection rectangle ... (fa97cddb3) - Fix singed/unsigned type confusion for intersection threshold. (85d43d68b) - [intersection-observer] Calculate areas using int64_t. (7771a8716) - Re-enable intersection observers with WD spec patches. (4319edc1a) - [PALEMOON] Initialize the search service asynchronously from 'about:home' and 'about:newtab' (cb2f0f614) - Merge pull request #919 from JustOff/nsIBrowserSearchService_async_init (bfedd7d40) - Fix crashiness of IntersectionObservers. (3cf7e874f) - Add performance warnings to Deprecated module. (202e78b73) - Add UXP Coding Style guideline document (WIP) (83cd9661c) My changes since my last build: - update libaom to git rev 9b1252eab0616d2c1f6d7990c6256441c0b6483f

I don't know about roytam's version of it, but original Basilisk does not have e10s either:

There are two patches: one is a backport of the official DX11 done by a Russian team (the same team that backported DX10), the other one is a wrapper for OpenGl. The thing is that the backported version has never been finished and it has a very limited compatibility with games. Besides, the Russian team that was working on it dropped the project. As result, @Svyatpro and others ported the Linux implementation to XP: on Linux DX10/11 games go through a wrapper which translates the calls to OpenGl, executes them with the GPU and then it translates it back. Although OpenGl is a fairly good protocol and the translated calcs are "just" Single Precision Floating Point which are perfectly handled by the GPU (both AMD and NVIDIA) due to the large number of 32bit capable units in consumer GPUs (there are a lot of single precision units and half precision units in consumer GPUs and just a few double precision units), unfortunately translating calls back and forth slows the whole thing down. In other words: does it work? Sort of. What do I do if it doesn't? Either help the project yourself or nothing. My memory might not be perfect, though, but I'm pretty sure this was the situation 'till a few years ago, before people started forgetting about it. P.s I don't play games; last time I did was many years ago and I've never been a gamer; the only reason why I use a GPU (other than display a video) is to use OpenCl to speed up Discrete Cosine Transform and Fourier Transform calculations. In other words, I couldn't care less if the latest DX prevents a game from running on XP as I wouldn't be playing it anyway...