Like others have said, the grey is too pale.
EDIT: It would be nice if the layout made use of columns .. this could provide innovative use of wide-screen resolutions.
i'll uninstall it now. looking forward to try a corrected version.
I try not to down-vote just for differing opinions from my own, although my emotions do get the better of me occasionally. However, if I see bad grammar it's just automatic.
The parent post is being shown as a reply to a peer and not the post it actually replied to. Seemed like normal threading until I noticed the reply was older than the grandparent.
Any suggestions as to what could be causing this?
This is my beef with the new Sparrow Gmail client on OS X as well. When I open up Gmail in Chrome I can see 33 messages at once (40 once I scroll). By contrast Sparrow shows me 13 (always utilizing the full vertical of the screen). Now arguably it presents them in a better fashion (although the label display is lacking, but I digress), but is it worth sacrificing 2/3rds the visibility? Not with my email volume.
Granted, information density is less important for HN, but then so is aesthetic appeal (the last thing I want is more people joining HN because it has an elegant appearance).
I'd do just two small changes:
First, the comment's points are important and right now are hard to read/notice.
Second, I'm not a designer, but I've always heard you shouldn't use black typo on white background as it's a little bit to hard contrast, it's better to use a (very) dark grey on the type.
I'm using Chrome 10.0.6.648.204 on OS X.
Will see if using pseudo class for first element helps me out.
Also I normally avoid looking at Comment points to avoid any bias and bring neutrality in my reaction to a comment. Again this maybe different for you guys.
Also as a golden rule the popular comments (unless threaded) are on the top so not really that important for me.
Second: In design specifically the rules are not hardwired like physics. You can break them but you must know that you are breaking a rule when you do. Normally I use #333333 in all my works but somehow missed it here. Will correct and put up an updated version tonight.
1.) There's a lack of contrast in the page. A visited link is the same color as a comment that is rated < 0.
2.) The up/down vote arrows are visually far away from the name of the user. Knowing the context of who's saying something can mean the difference between a troll post and an insightful one.
3.) The page is no longer fluid. While this is more preference than an actual issue, I think that a fixed width format is detrimental for those of us who have widescreen monitors (or for those of us who like to tile our windows in small patches).
4.) Whitespace. There's a lot of it. Without your plugin, I can see all of the articles on the front page in ~1400px. With the stylesheet patch, it's about 3x that. I visit HN a lot, and will click on just about every story. As such, when I'm done reading HN all of the links have changed color. When I visit it later in the day, I can at a glance see every story that's new. Sometimes I have it autorefresh every few minutes on a separate monitor, and keeping everything concise allows me to do that.
Those are my thoughts. At this stage I'd say that it's pretty, but not yet functional. Work on the functional portion and I'll keep this plugin installed. Great work, keep it up!
(3) Fluid has a deterimental effect at lengthier line span (when it exceeds 50-60 chars). Hence limited at 700 px.
(1)On HN visited links are read emails for me. Hence they are of not much use and thus same treatment as the dead link.
Also it is funny since the reason most people gave for requesting flushing commenter's name to left was that they upvote or downvote with help of points/commenter's name! Atleast that was my interpretation. I had thought of the exact opposite reason and hence put it in right earlier. Upvote should have nothing to do with who said it or how many points it has already received.
Not necessarily. While I'll agree with that the current score of the comment should have little to do with your vote, who said it is necessary for context. Consider this hypothetical comment:
"The backend code behind the current search functionality at google is absolutely horrible. The search ranking algorithm is pathetic to say the least."
Had this been said by an SEO guy or an employee of yahoo/bing, I'd have downvoted the comment. However, if it were a comment by Matt Cutts (http://news.ycombinator.com/user?id=Matt_Cutts), it presents itself in a whole different context. It's no longer a flamewar comment, but rather an admittance of areas where someone/something needs to improve.
So be sure to submit it there too, I will definitely try it.
The thing is, if it is just style changes, it is better to be done via Stylish. Extensions, for most of them in chrom(e|ium), would would absolve resources in the system via a separate process. For computers with less memory, running multiple chrome extensions would not be a good idea. Better to run extensions that benefit all sites than just one.
Also as a side note for using that in Firefox 3.6 , it seems that submit button's orange background is not applied like in chrome, so it would be harder to read the text on the button. Someone with Firefox 4 on hand may to see check on that as well.
Please note this has a fixed width issue in Chrome. Works fine in Firefox. So I would recommend Chrome extension for chrome users and Stylish for FF
edit: Also, the extra space in comment-headers is wonky. And even with my nitpicking, great job!
Also that makes the URLs work as an Inbox/Unread badge for me. With what I can see as the unread ones I need to read before the end of day.
Will tweak it a bit though. Also different screens with different color gamut make it troublesome in corner cases.
edit: The comments whitespace treatment is next in line on by issue list.
If marketers starting picking up the idea, I see "shoot here to win the prize", phone number, email address collecting type of ads promising to "bring facebook back the way it was", "just enter your email address and we'll send you the link!" If you don't think this could work, just remember that a few years back people were installing emoticon packs and CometCursor just so they could have a customized, albeit terrible, experience.
The people who would install a Chrome extension to improve the design of facebook aren't going to be the kind of people who blindly say "ugh, Facebook looks differen, wtf!", and those kinds of people are especially not going to be the kind of people who would write up lots of complicated CSS and JS (both, not just CSS, would be necessary to roll back Facebook's upgrades) to redesign facebook. But this raises a good point: when Facebook rolls out a redesign, do they change the backend enough that an extension that overrode the CSS and JS with the previous design's CSS and JS would break?
(Not passing judgement on this theme, which seems quite nice; just thought I'd throw in a recommendation for a theme I've been using on HN since it was originally posted.)
A couple of points for me are that:
1. While it is easier to read, the combination of the larger size of the text and the vertical spacing makes it harder to scan all the topics quickly, as was possible without this style.
2. as already mentioned, the info sub-text is a bit soft in contrast and hard to read quickly, even though it looks nice. Suggestion: make the important info such as the numbers and username a bit more darker, but leave the repeated info such as 'points by' and 'comments' as they are.
Non AJAX version: http://www.skillendar.com/hackernews/noajax.aspx
AJAX version: http://www.skillendar.com/hackernews/
Golden rule of 40-60 chars each line.
That is the reason readability and Safari Reader are designed the way they are. Use em/% to go screen size free.
It's still a good move from the Author. I was thinking of something similar, but time was a constraint. I might look to help improving that one. Any Github?
Just reducing the font sizes a little would help - having the default font so large kind of apes apps like readability, it's much bigger than is necessary.
(Just zooming out on my browser isn't enough, since it also reduces the width of the lines.)
That's the reason i don't maximize windows. Sites like HN let lines of text go way too far for a window that's 1000+ px wide.