101–110 of 203 posts
One thing: it'd be nice to click the whole top header of the comments to collapse them, instead of clicking the far left toggle.
Edit: also not seeing my comment score inline on the page header makes it difficult to know if I should check my comments for activity. this one might be a deal breaker.
But this is really well designed and great to have the style customization available.
Are you a designer?
The upvote, bookmark buttons etc probably need a tooltip - not everyone might know what those icon buttons do. In fact I'd add a tooltip to all icons buttons.
Also, when the width is set to 100% - the menu that appears after clicking on the more button (3 dots) is cut off - as it appears to the right. You probably have to do some edge detection or always show it to the left.
And nice one for trying to earn a buck.
It is way less efficient to consume HN with this design, so I won't use it.
There's some overhead, but not much. It basically just parses the underlying HTML as soon as it's loaded, then redraws it with added features. Also no heavy frameworks used, just basic hand-coded JS + jquery + a few helper libraries (luxon for dates etc)
The following is not any sort of critique on the author’s work. The design looks quite fresh, in fact. This is merely a tangential observation. Anyone else see the mock-up and think “this looks slow”? Logically, it’s not a defensible inference in the slightest. There’s nothing about this design that would necessitate performance tradeoffs. But that’s the barely-conscious, emotional first impression I had. I wonder if…
It just looks clumsy and distracting compared to plain HN, IMHO. It highlights elements like usernames, the total amount of comments(!) or the upvote/favorite actions, that users will only rarely interact with or even want to look for. Meanwhile other actions have to be hidden beneath a "…" widget, lest the page become too cluttered. The factory HN look does a much better job of bringing the comment text into focus and reflects the threading hierarchy without needing a lot of padding to space things out.
The following is not any sort of critique on the author’s work. The design looks quite fresh, in fact. This is merely a tangential observation. Anyone else see the mock-up and think “this looks slow”? Logically, it’s not a defensible inference in the slightest. There’s nothing about this design that would necessitate performance tradeoffs. But that’s the barely-conscious, emotional first impression I had. I wonder if…
The design is clean, modern, minimalist -- and I associate sites that look like that with loading in a blink.
It's the sites where everything is crammed in and packed with ads that load slowly, like most news sites.
Everything about this style of design says "fast" to me.
The following is not any sort of critique on the author’s work. The design looks quite fresh, in fact. This is merely a tangential observation. Anyone else see the mock-up and think “this looks slow”? Logically, it’s not a defensible inference in the slightest. There’s nothing about this design that would necessitate performance tradeoffs. But that’s the barely-conscious, emotional first impression I had. I wonder if…
Related story: In my free time I am a coach for a competitive math team, I recently had to design an application to automate multiple choice problem submissions. Nothing stellar, your run-of-the-mill CRUD app. But it was under some interesting engineering constraints: users would have to log in from a variety of devices, phones, tablets, bad chromebooks, etc., possibly on slow cellular connections.
So naturally I went for a simple server-rendered design, with stock Bootstrap hosted on a CDN.
The overwhemling reaction was "this is so fast". Now, being server-rendered with absolutely no XHR, the app spends most of the time doing nothing, but it's interesting laymen think it's fast.
I think we came to associate "modern" designs with piles of javascript, requests everywhere, popups, ads, and the like.
Probably the correlation is indeed there, even if it's obviously not causation.
One deal-breaker for me, sadly -- having the collapse/expand and upvote/downvote buttons on opposite sides (left, right) of the page is way too annoying.
When I read comments, I'm constantly voting and collapsing. Using my trackpad to jump back and forth is just too much.
Current HN isn't great for that, but it's usually only traversing about a quarter of the page's distance.
The following is not any sort of critique on the author’s work. The design looks quite fresh, in fact. This is merely a tangential observation. Anyone else see the mock-up and think “this looks slow”? Logically, it’s not a defensible inference in the slightest. There’s nothing about this design that would necessitate performance tradeoffs. But that’s the barely-conscious, emotional first impression I had. I wonder if…
I had your exact same reaction. Related story: In my free time I am a coach for a competitive math team, I recently had to design an application to automate multiple choice problem submissions. Nothing stellar, your run-of-the-mill CRUD app. But it was under some interesting engineering constraints: users would have to log in from a variety of devices, phones, tablets, bad chromebooks, etc., possibly on slow cellular…
It is faster than basically any modern CRM in existence.
30+ companies use it daily. It runs in a namecheap shared hosting for $4 a month.