Forgot your password?
typodupeerror
User Journal

snowgirl's Journal: Why do you need so much CPU to collect a comment Slashdot? 13

Journal by snowgirl

I'm using OpenBSD, and as a result, my webbrowser options are somewhat limited. I love XFCE, so I'm using that, so naturally, I chose to use Midori to do my webbrowsing.

Frustratingly though, anytime I want to type out a response or comment, or even in this field here, Midori's usage spikes up to some 60~78%! So, my typing ends up looking all 300 baud modem like (yeah, I read that story, too.) So, like what is it Slashdot? Why do you need to sit there and cycle through a bunch of javascript while I'm typing things out?! I don't see any cool nifty text editing options, I don't see anything in fact to justify you jumping on a spinlock and taking it for a joy ride.

Does anyone have any clues as to what slashdot is supposed to be doing with all this CPU time?

This discussion has been archived. No new comments can be posted.

Why do you need so much CPU to collect a comment Slashdot?

Comments Filter:
  • Does Midori have NoScript or an equivalent? Glancing at the source code of the page, there is a bunch of JS crap. Everything from JQuery to Google Analytics to a Double-Click bit of code and then some.

    I don't see anything that cycles on mouse presses, so I'm not sure what would be going on there.

    Last I remember, there was a Firefox package for OpenBSD, though it looks to be quite a bit behind the current. Still, NoScript (and AdBlock Plus) should work on it. You might just break down and install FF.

    • by snowgirl (978879)

      Does Midori have NoScript or an equivalent? Glancing at the source code of the page, there is a bunch of JS crap. Everything from JQuery to Google Analytics to a Double-Click bit of code and then some.

      I don't see anything that cycles on mouse presses, so I'm not sure what would be going on there.

      Last I remember, there was a Firefox package for OpenBSD, though it looks to be quite a bit behind the current. Still, NoScript (and AdBlock Plus) should work on it. You might just break down and install FF.

      I am a firm believer that I shouldn't have to use noscript to post comments. I generally like the rest of the UI, and I like the Web 2.0 interface (to within a moderate tolerance). So why would I want to abandon all javascript?

      I just don't want the javascript running some tight-loop RSA decryption while I'm trying to leave a comment.

      • by chill (34294)

        Yes, but are you 100% sure that a script is the problem? I was proposing using NoScript to verify that at first.

        I agree that you shouldn't have to use it to make things workable, and Web 2.0 can have some nice benefits.

        • by snowgirl (978879)

          Giving it a shot... with noscript on, it still seems to jump to 60~80% as well... good call, here I get all caught up in "I know what's wrong" and forget to check if it actually is!

          • by snowgirl (978879)

            It doesn't ramp up and sit and spin using a different CMS... it just seems to happen with Slashdot. What could possibly be doing all this? Like it also only starts hemorrhaging CPU time if the input field actually has focus, if I move focus away (even to the Subject input line) the CPU leaking goes away. So, this is purely having to do with the slashdot comment box. :(

            • by chill (34294)

              Which theme/scheme are you viewing Slashdot in? Going into "Options", I have "low bandwidth" and "simple design" checked so things load faster and look semi-decent when checking from my phone.

              I also have Slashboxes and a few other items like icons disabled to make things quicker.

              Maybe it is a CSS bug of some sort?

              • by snowgirl (978879)

                Well, let's see... no, it's still projectile vomiting CPU time all over the place... even with low bandiwdth and simple design.

                • by Bill Dog (726542)

                  If you're definitely denying all js (including from alternate domains like fsdn.com), well, the styles look like they're the same for the subject field as the comment field. I guess it could be a CSS focus bug that affects text areas but not input text fields.

                  The problem may be that Slashdot decided to violate/disregard web standards in their site redo, and maybe your browser is not quite expecting such craptastic deviations. One thing the comment field has that the subject field doesn't is a (non-standard)

  • by Bill Dog (726542)

    I'd say your browser is getting, ahem, Web2.0verwhelmed!

    • by snowgirl (978879)

      I'd say your browser is getting, ahem, Web2.0verwhelmed!

      I hate you so much right now, because I have a horribly sadistic sense of humor for bad puns.

  • It maybe in the ports in 4.9 and that should have the fastest javascript.

    I used FreeBSD so you can disregard my comments as I am sure OpenBSD is different.

"I have just one word for you, my boy...plastics." - from "The Graduate"

Working...