Comment by dataflow

Back to stories Open in a window
Comment

Comment by dataflow

Thanks for asking. Depends what time period you're asking about. My memory's faded so there may be inaccuracies here or things may be out of order, but this is what I remember.

There was a long era (years) when I loved Mozilla and used Firefox -- and then even Waterfox, IIRC because it was 64-bit -- exclusively. (As well as Thunderbird.) I did not like Chrome. IIRC at some point they started feeling like every update made them more bloated, broken, and unbearable in various ways. I forget all the exact issues but I distinctly remember rendering was a big one for all of them (I think it happened around the obsession with GPU rendering), my extensions constantly breaking or getting disabled because of "compatibility" issues forcing me to keep toggling flags in about:config being another, my toolbar styling/customizations getting constantly messed on every damn update up being another, the tab bar getting moved up like in Chrome when that was very much one of the reasons I liked Firefox being another, and slowness/bloat being another. I wasted too much of my time into finding workarounds, but eventually I couldn't take it anymore. Giving up everything including extensions like Greasemonkey and Stylebot and having the ability to customize everything just so I could have a better experience was painful, but I bit the bullet and switched to (I think Chromium first? and then) Chrome.

After that I basically stuck with them though I kept a Firefox around and updated it once in a while to see if maybe they would come to their senses and start improving the UX. They removed support for old-style extensions which immediately was like a punch in the gut. Regardless, a few years ago I figured maybe times have changed so I spent probably weeks on it (if not longer) and even sank quite a bit of time into manually porting porting my custom local Chrome extensions to it just to make sure I was giving it a fair shot. The snappiness was maybe better than before but overall I just felt like they didn't give a damn about longstanding UX issues people have been complaining about for years, and were too focused on other priorities. So I've stopped wasting more of my time on it until it passes a couple litmus tests, which it failed again today.

And don't get me wrong, Chrome has had its own issues and frustrated me too (MV3 being the most recent and frustrating), but at least it's not completely defeating the very reasons that drew me to it in the first place.

But the point being: I believe I've given it a fair shot enough times in the past, but I also have better things to do than fight with a browser vendor over the very things that drew me to their browser. For Chrome the speed was probably the biggest factor, and for Firefox it used to be UX/customizability. One of those companies understood that and never compromised on their core strengths, but the other never seemed to get the memo.

Replies dataflow · 6d
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.