Jump to content

NotHereToPlayGames

Member
  • Posts

    5,181
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. I don't know about for SWITCHING tabs. My issue has more been about CLOSING tabs - especially for very long browsing sessions like you mention versus opening-and-closing the browser for new sessions. Others have posted it also over the years - I really dislike clicking the X on a tab then sitting there and waiting 2 to 4 seconds for the tab to close! This was my biggest issue with NM28 and it is one of several reasons why I prefer NM27. I have not ran Serpent in any very long browsing session to test if this is an issue with Serpent. I am also unaware if it is "still" an issue with NM28 - perhaps others that have reported it in the past will chime in if it is still an issue. I am also open for "better" ways to test page rendering. What I used for the below is the Status-4-Evar and PageTimerLite add-ons. NM27 barely beats Serpent from what I see here -- I did three page loads and posted the averages.
  2. @DanR20 -- Another thing to watch is how fast the GUI loads and responds to mouse-clicks. What good is a browser that renders pages in 100 milliseconds if it takes 10 seconds for the GUI to load? (exaggerating, of course) I use PassMark AppTimer for this -- https://www.passmark.com/products/apptimer/ And again, Serpent is the SLOWEST. Don't get me wrong, Serpent has its advantages (not for me personally, but it depends on what the user uses it for) - but "speed" is not one of those advantages. Browser-choice is ALWAYS a matter of "personal preference" so again, "mileage may vary".
  3. My table is from an i7-4770. My other two desktops are both Core2 Quads and the laptop is Core2 Duo. No matter how I slice it, NM27/Mypal27 is the fastest and Serpent is the slowest. To each their own, you cited earlier that you don't see any benefit to using Pale Moon. Well, what goes around comes around, but I see no benefit to using Serpent.
  4. I run with javascript.options.ion set to false for added security. (which is why my table has n/a for KM76 because it would give an apples-to-oranges comparison)
  5. "Serpent" is the SLOWEST of the browsers being offered here (at least on my hardware, "mileage may vary").
  6. In a nutshell -- Firefox is no longer Firefox. Firefox removed legacy (ie, XUL) add-ons in favor of WebExtensions (ie, Chrome-like) add-ons. I suggest you install this add-on archive then go from there -- https://github.com/JustOff/ca-archive/releases/tag/2.0.3
  7. Perhaps a better explanation is required? I personally don't know WHY we have "regular", "sse", and "ia32". But my reasoning is based on "user base" - ie, my hunch is that 99% of people here can (and should) use the "regular". But there's that 1% that has us (Roy) releasing all three "flavors" every week ??? We have Win98 and Win2000 "flavors" every once in a while - we (Roy) doesn't release those "weekly" (nor should he). So why are we (Roy) releasing sse and ia32 flavors "weekly" when there is such a tiny user base that "require" those flavors ??? Just thinking out loud...
  8. Your avatar (or whatever it's called) says you are on XP so the answer is "neither", use the "real" version that has no SSE or IA32 in the name. Technically the answer is determined by your CPU and not your operating system. Use the "real" version unless your computer is so old that it came with Win 98 or Win 2000. If it came with Win XP then the SSE and the IA32 aren't for you. At least that's how I understand it.
  9. Updated table. Added releases specifically cited as "updated for performance" in upstream Release Notes -- https://www.palemoon.org/releasenotes-archived.shtml
  10. My Stylem styles are basically trial-and-error - but they work, lol. Below is what I use for o.rhost.win - half is for the http://o.rthost.win/gpc/files1.rt/home.html and the other half is for http://o.rthost.win/palemoon/?sort=date&order=desc But I keep it all lumped into one Stylem style sheet. The trick was to set the table width but then oversize the first column width beyond the actual column width but display cells as tables so they don't resize (if that makes sense). @-moz-document domain('o.rthost.win') { #ajContent a {text-decoration: none !important;} #container { padding: 0 !important; text-align: center !important;} #footer {display: none !important;} #g_body p {display: none !important;} #header {display: none !important;} .foot {display: none !important;} .list { position: absolute !important; top: -1px !important; width: 99.4% !important;} a[href*='.asc'] {display: none !important;} a[href*='http://o.rthost.win/gpc/files1.rt/'] {display: none;} a[href*='http://o.rthost.win/gpc/files1.rt/arctic'] {display: block;} a[href*='http://o.rthost.win/gpc/files1.rt/iceape'] {display: block;} a[href*='http://o.rthost.win/gpc/files1.rt/palemoon'] {display: block;} a[href*='http://o.rthost.win/gpc/files1.rt/pm'] {display: block;} li {height: auto !important;} table { margin-left: 10% !important; width: 80% !important;} th.t, td.t {display: none !important;} th.m, td.m {text-align: center !important;} th.n {padding-left: 10px !important;} tr {height: 16px !important;} tr td.n a[href*='/palemoon/palemoon-27'] { background-color: lightgreen !important; display: table !important; padding-left: 10px !important; text-decoration: none !important; width: 140% !important;} tr td.n a[href*='/palemoon/palemoon-28'] { background-color: palegoldenrod !important; display: table !important; padding-left: 10px !important; text-decoration: none !important; width: 140% !important;} tr td.n a[href*='xpmod-ia32'], tr td.n a[href*='xpmod-sse'], tr td.n a[href*='win64'] { background-color: palevioletred !important; position: relative !important; z-index: 1 !important;} tr td.n a[href*='sources'], tr td.n a[href*='pm28xp'], tr td.n a[href*='src'], tr td.n a[href*='msvcr'], tr td.n a[href*='lav'], tr td.n a[href*='loader'] { background-color: palevioletred !important; display: table !important; padding-left: 10px !important; position: relative !important; width: 140% !important; z-index: 1 !important;} ul li {list-style: none !important;} }
  11. Bummer, that's what I was afraid of - I was hoping there was some sort of "conditional child" CSS selector I found a cheat that works close enough I suppose. Ultimately I would have preferred to fully hide ia32, sse, and win64 rows within the table to cut down on full-page scroll. Opted for just keeping all rows then elevating z-index to "hide" last-modified and size cell text for ia32, sse, and win64 rows instead.
  12. Same here if seeking 100% functionality on Google Voice (making phone calls for example). I have to use VirtualBox + Win7 + Chromium v79 (other versions work, that's just the one I use but don't recall why at the moment) for 100% functionality. NM27 and NM28 do not select "To" names/numbers from contacts drop-down when sending sms messages. NM27 and NM28 do not download .csv files from some of my Google Sheets (some work, others do not). BNavigator works perfectly for sms messaging and .csv files. But I cannot make phone calls from BNavigator.
  13. I feel like I'm missing something obvious and maybe somebody here can assist. I use a custom style sheet for Roytam's Index page - http://o.rthost.win/palemoon/?sort=date&order=desc So that it looks like this - ie, I hide win64, ia32, and sse links and highlight v27 in one color and v28 in another color. My question is what am I missing to hide or highlight the entire row (include last modified, size, and type)? Here's the pertinent portion of the custom style sheet - Thanks in advance if you have any suggestions.
  14. Nope, NM27 has worked for EVERYTHING that I've thrown at it. Google Voice is the one exception that doesn't work in NM27 but it also does not work in NM28 (granted, I have not tried for a few months if any recent updates have resolved this). So I use BNavigator for Google Voice.
  15. Here's what I got for several NM 28 versions. These are with javascript.options.ion set to false. There's way too many versions to include them all, so I took my preferred v28 (approx 28.2.2) and then every three months from there. If there is a needle in the haystack that truly shines among the v28's, I have no quick way of finding it. green = best group of three... followed by light green... red = worst group of three... followed by orange...
  16. The 2018-09-22 seems to be the best NM28 on my end. I haven't focused my table too heavily on comparing v28's throughout the months - my experience has been that 2018-09-22 is about as good as it gets as far as v28. But v27 beats it hands down and I have other reasons to also prefer v27. Truth be told, I no longer use any of Roytam's builds but I run benchmarks on new releases every weekend and if they don't beat my current default browser then I delete them and move on. I should also point out that my recommendation for NM 28.1.0a1 2018-09-22 (I have one-day difference due to Roytam's Time Zone and my Time Zone) had MUCH more to do with what I will call "click-lag" as it did with benchmark numbers. As far as benchmark numbers go, all of the NM 28's basically lump together relatively close to each other and all of the NM 27's basically lump together relatively close to each other. With the 27's scoring BETTER than the 28's. I should add that if you prefer the about:config option of javascript.options.ion set to false that NM 28 especially has gotten slower and slower over the years (the Kraken 1.1 benchmark is a good one that shows that, I may upload another table in the next day or so to demonstrate).
  17. You really have to answer this one yourself. You ask 50 people, you'll get 50 different answers. You ask 5000 people, you'll get 4999 different answers and two people that give the same answer. I personally use v27 because I have ran benchmark tests and v27 is faster - "mileage may vary" and you should really run your own benchmark tests.
  18. I will not. I do not follow "their" build, I follow your build.
  19. ALL settings in about:permissions is broken. "Most" of them were fixed in NM27 but they still remain broken in ArcticFox.
  20. Agreed! I, for one, do NOT want BLOAT added. I want to go the OTHER WAY and REMOVE (what I feel) is BLOAT already added. I want FAST and EFFICIENT at its CORE. "You guys" can slow your browser down all you want with addon after addon and extension after extension. "To each their own", as the saying goes.
  21. 300+ MB RAM with only the "Tableau" open ??? HECK NO, that's not for me! (you asked my opinion, lol) Plus I don't want my browser to use my OS's proxy settings - I know there's probably an extension for that but the 300+ MB RAM with nothing open is a showstopper for me.
  22. I can direct SOME (not "most") to web devs. I whitelist JS and only allow a portion of them to work on a very small number of web sites. I have high hopes for BNavigator but it can't dethrone Mypal / New Moon / Pale Moon just yet. Pale Moon (at the upstream level) has become BLOATED and there is no such thing as a current fork that attempt to remove any of the BLOAT. "Most" can be directed to "web standards" and that browser developers FALSELY think they need to attempt to adhere to them. The "web standards" are GIGANTIC and we CAN browse the web WITHOUT a very VERY large portion of them. Read some of our "patch" descriptions on a weekly basis then try to track down WHY that patch was implemented. You are kidding yourself if you think MOST of them have anything to do with "security" as opposed to 'striving to achieve 100% web-standards-compliance'. (Granted, I can only find a WHY for a very small number of these "patches"). But it's also not my "line of work". But I digress. There WILL be a day where I will have to switch to Win 7 or 10 or run a Server version (I ran Server 2003 for several years and trial-ran 2008 and 2012). But that day is FAR away so long as I don't fool myself into thinking I need to achieve a 555 score for HTML5 -- I don't!
  23. I've personally become INCREASINGLY displeased with "new" web browsers. I want FAST and EFFICIENT. What good does it do to boast "works on XP" if it takes 10 seconds to load or 5 seconds to render (exaggerating, 'slightly') ??? FAST and EFFICIENT is WHY I run XP - boot time from full power down is UNDER 20 seconds compared to OVER A FULL MINUTE for Win 10 -- "mileage may vary". My default-for-everything is currently Mypal 27.9.4 dated July 19, 2018. PassMark AppTimer == https://www.passmark.com/products/apptimer/ Kraken 1.1 == https://krakenbenchmark.mozilla.org/ Basemark Web 3.0 == https://web.basemark.com/ Speedometer 1.0 == https://browserbench.org/Speedometer/ Speedometer 2.0 == https://browserbench.org/Speedometer2.0/
×
×
  • Create New...