Slashdot Mirror

← Back to Stories (view on slashdot.org)

Slashdot's 10 Most-Visited Stories of 2017 (slashdot.org)

Posted by EditorDavid on from the happy-New-Year dept.

Slashdot's most-visited story of 2017 was Google Has Demonstrated a Successful Practical Attack Against SHA-1, which was visited more than 212,000 times since it was published in Feburary.

And our second- and third-most popular stories also came in February -- both just one week before.

FCC Chairman Wants It To Be Easier To Listen To Free FM Radio On Your Smartphone and IT Decisions Makers and Executives Don't Agree On Cyber Security Responsibility.

Keep reading for a complete list of Slashdot's 10 most-visited stories of 2017.
Here's a quick reminder for 2018. You can always find a list of Slashdot's ten most-visited stories for the preceding year in the Slashdot "Hall of Fame." It will also tell you which stories got the most comments during the preceding year, and also reveals the most active submitters and most active poll topics.

Here's our most-visited stories for 2017.

16 of 35 comments (clear)

  1. Dumb metric by war4peace · · Score: 5, Insightful

    "Most visited" means shit. A crap older story might be visited more than a very interesting story from last month.
    Focus on "most commented" instead, because comments are disabled after a while.

    --
    ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
    1. Re: Dumb metric by alvinrod · · Score: 2

      Most commented would be even worse. It really just means the most controversial and Iâ(TM)d guess most of them have more to do with politics than tech.

    2. Re: Dumb metric by war4peace · · Score: 1

      At least you know they raised interest.

      --
      ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
    3. Re: Dumb metric by 93+Escort+Wagon · · Score: 1

      I would guess that the ten most-commented stories on Slashdot this year all involve Trump and/or members of his administration.

      --
      #DeleteChrome
    4. Re: Dumb metric by AmiMoJo · · Score: 1

      Anything about diversity or Trump brings the snowflakes out... So I'd guess the Damore debacle.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    5. Re:Dumb metric by Tenebrousedge · · Score: 1

      You anti-creimer trolls need to fuck off.

      --
      Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
  2. Trend line by cold+fjord · · Score: 1

    2016: Wow! That was kind of crazy, huh?
    2017: Hold my beer!
    2018: I see you have a line forming already, so where do you want me to offload the kegs?

    --
    much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
  3. Use both by cold+fjord · · Score: 2

    Different metrics measure things, and both are worth considering: most commented, and most visited.

    Some other possible metrics of potential interest: most unique commenters, most heavily moderated, most linked to, ....

    --
    much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    1. Re:Use both by war4peace · · Score: 1

      - Most unique commenters: I suppose it's somewhat doable but only if you log the IP addresses or eliminate all AC comments from the pool.
      - Most heavily moderated: directly related to amount of comments and views.
      - Most linked to: maybe - how do you reliably measure that?

      --
      ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
  4. News for Trump? by Xenographic · · Score: 1

    I'm surprised my submission on Donald Trump winning isn't higher on the list, honestly, given that it has the unfair advantage of somehow being a related story for damned near every story on here for the past year. Some of the stories it sorta makes sense, but I know there were more than a few stories where I wondered how it could possibly be related.

  5. Re:OT: Programming Question by jfdavis668 · · Score: 1

    COBOL is the up and coming cross platform language.

  6. sjames won't get this either by Hognoxious · · Score: 1

    10? I swear I can see 20.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    1. Re:sjames won't get this either by sjames · · Score: 1

      Well, it's true that I nearly didn't bother with this article. Ceretainly I didn't write it. Your beak is still over by that tree. Still smoking. Just clomp once if you understand.

  7. What? by DontBeAMoran · · Score: 1

    Nothing about Bitcoin, Arduino, Raspberry Pi or 3D printers?

    --
    #DeleteFacebook
    1. Re:What? by Hognoxious · · Score: 1

      Come on, the pi and 3d printers were last year. Actual last year, not soon-to-be last year.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  8. Use the language right and speed isn't a problem by raymorris · · Score: 1

    >. I'll also need it to run pretty fast due to my desired complexity for the game. Therefore, a scripting language like Python probably isn't the best choice

    The language has little impact on the speed. When using "a scripting language like Python", the few operations that take up most of the time should generally be done in the interpreter / library anyway. For example, sorting is a slow operation - a shell script can sort just about as fast as any language, because the actual sort is done by the "sort" program.

    Profile your program to find out the two or three functions that need to run faster. Refactor them to be just a few lines, then profile to see which *lines* of code are slow. If those lines are being called thousands or millions of times, fix the algorithm. Then figure out how to leverage a thorough understanding of the language to make the few problem bits much faster. That may well involve figuring out how to have that bit done by the interpreter / library, which is written in a fast language like C. As an example, though "write quicksort" is a common interview question, you should almost never write sorting code. Every high-level language already *has* a fast sort already provided. Use it.

    It's also not uncommon that the slow operations can be entirely removed by using a faster algorithm or pattern.

    Several things can make a big impact on execution speed. Language choice isn't near the top of that list.