News for hackers. Stuff that matters.
Re:The case for memory-mapped GPU assets by throw7 on Monday June 13, 2016 @09:04AM (#11893424)
Totally aside and ranty: facebook has started (recently?) greeting/forcing outsiders with a login dialog that covers the whole page. You can click "not now", but that just permanently lowers the login dialog box to about the bottom 1/3 of the page.

If you want to publicly make your content available in a free and seamless way stop using facebook. Please.

Re:The case for memory-mapped GPU assets by cageface on Monday June 13, 2016 @11:04AM (#11894404)
Your rant may be justified but I'm getting really tired of clicking on HN threads I'm interested in and finding the top comment plus a screenful or two of replies addressing some nit somebody wants to pick with the implementation of the site in the article instead of addressing the content of the article.

Leave the asides aside please.

Re:The case for memory-mapped GPU assets by wmccullough on Monday June 13, 2016 @12:23PM (#11895094)
I'm at that point too. I know if I click a link, I'm not going to get to read intelligent discussion until much deeper in the page. Take for example the article about the LinkedIn acquisition, top comment has people arguing over the origin of the word secular...
Re:The case for memory-mapped GPU assets by kibwen on Monday June 13, 2016 @12:59PM (#11895388)
How about we solve this problem once and for all by turning this thread into a two-page series of complaints about how HN doesn't allow you to collapse comment threads. :P
Re:The case for memory-mapped GPU assets by andrepd on Monday June 13, 2016 @01:09PM (#11895461)
And now this article's top level comments are a discussion about how another thread's top level comments are out of topic...
Re:The case for memory-mapped GPU assets by geofft on Monday June 13, 2016 @01:27PM (#11895581)
I look at the comments to determine whether the article is worth reading. "The article is unreadable" is as useful for me to know as something like "Hm, everyone seems to be talking about a programming language I don't use". So I appreciate complaints about popups and the like being at the top.

(The other very useful comment at the top is "Warning, it autoplays a video")

Re:The case for memory-mapped GPU assets by skybrian on Monday June 13, 2016 @01:10PM (#11895466)
I think Hacker News should allow tangents, but make them easier to hide. Maybe have a button to collapse everything under the top-level comment somehow. This would also be good data to collect as input into ranking.
Re:The case for memory-mapped GPU assets by Bjartr on Monday June 13, 2016 @11:44AM (#11894777)
I disagree that we should discourage engaging discussion just because it happens to be meta or only tangentially related. This is a user experience problem, not a content problem. More specifically, this is a use case for comment-thread collapsing where when, as a user, you come across a long thread that doesn't interest you, you can collapse it and immediately be at more content, rather than needing to manually find the end of the uninteresting thread.

This allows both for the community to drive the discussion to what most interests the community, and to allow those with different tastes than the majority to still participate without alienating or frustrating them or those involved in said discussion.

Re:The case for memory-mapped GPU assets by kbenson on Monday June 13, 2016 @12:46PM (#11895300)
There are many browser extensions for HN, and thread collapse is possibly the most common feature in them.

I'm of the opinion that HN doesn't implement features like this on purpose, because they expect you to find a way to work around the limitations that works best for you, and that will likely result in a more customized and comfortable experience than them forcing their opinion of how the content should be presented on you. HN is somewhat notorious for having these soft limitations (such as not showing reply on very active threads for a few minutes, which also has an easy workaround for those that know).

Re:The case for memory-mapped GPU assets by cageface on Monday June 13, 2016 @08:49PM (#11899002)
I completely agree that I should be able to easily collapse any sub thread and also see only the comments that have been made since the last time I viewed comments on an article.
Re:The case for memory-mapped GPU assets by zepto on Monday June 13, 2016 @11:41AM (#11894741)
Flag?
Re:The case for memory-mapped GPU assets by draw_down on Monday June 13, 2016 @12:43PM (#11895281)
Same here! This is now just a place where people gripe about whatever they don't like about web pages.
Re:The case for memory-mapped GPU assets by anamoulous on Monday June 13, 2016 @11:16AM (#11894530)
And I wish there was some filter in HN that let us ignore upvoted posts that complain about gated sites, design, javascript requirements or how slow Atom is. It's an unfair world.
Re:The case for memory-mapped GPU assets by izacus on Monday June 13, 2016 @11:56AM (#11894885)
Or, you know, don't link to content that's actively hostile to the reader.
Re:The case for memory-mapped GPU assets by nwah1 on Monday June 13, 2016 @12:35PM (#11895215)
Exactly. It is usually possible to find other links with the same content, and on a site like HN we ought to be able to expect better.

Perhaps there ought to be some feature on the part of HN itself, to automatically recommend the better links, when possible.

Re:The case for memory-mapped GPU assets by adrianratnapala on Monday June 13, 2016 @09:08AM (#11893467)
Yes, it was annoying enough to make me give up on trying to read the article.
Re:The case for memory-mapped GPU assets by coldpie on Monday June 13, 2016 @09:32AM (#11893676)
NoScript prevents this dialog box from loading and you're allowed to read the article full-screen.
Re:The case for memory-mapped GPU assets by distances on Monday June 13, 2016 @10:02AM (#11893924)
Another great option is the "Block Element" feature of uBlock Origin which lets you easily create a blocking rule for any element on the page. In Firefox it's found in the right click menu, and you can then visually choose the element to be blocked.

I regularly use it e.g. for the cookie acceptance boxes. They are a major annoyance -- as I don't save cookies, the setting for accepting cookies isn't preserved either and I have to approve them again and again. If I visit any such page for a second time it's easier to just hide the whole question with uBlock.

Re:The case for memory-mapped GPU assets by mdpopescu on Monday June 13, 2016 @10:35AM (#11894174)
Thank you, I wasn't aware of Block Element (it works in Chrome too). Great feature.
Re:The case for memory-mapped GPU assets by mikerichards on Monday June 13, 2016 @09:39AM (#11893737)
Yes, annoying. Ended up right-clicking, inspect, and delete element.
Re:The case for memory-mapped GPU assets by ebbv on Monday June 13, 2016 @09:48AM (#11893812)
Unfortunately he's now a high profile Facebook employee so I'm sure he has strict orders about where his content is to be posted.
Re:The case for memory-mapped GPU assets by brudgers on Monday June 13, 2016 @01:40PM (#11895672)
Firefox Reader Mode resolves the issue for me. I use it on both Desktop and Android. My only beef with it is that there is no keyboard shortcut.
Re:The case for memory-mapped GPU assets by GFK_of_xmaspast on Monday June 13, 2016 @01:35PM (#11895630)
On the other hand, making a fake facebook account is pretty easy.