I want hacker news UX to stay as it is, mostly, but these are features I'd welcome.
What features would you welcome?
Show HN: Orange Juice – Small UX improvements that make HN easier to read
51–60 of 165 posts
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#52Latchkey, would you be comfortable with HN adopting your dark mode styling as a user choice someday, if they came around to liking it? I really like it and I think it’s in the spirit of the site.
I'm pretty sure that will never happen, as it would've happened already by now. People can and do already use custom CSS or Dark Reader for dark mode.
Some things have taken us 15 years and then pow they happened
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#53Earlier quoted context omitted.
How is it over-engineered slop? Happy to improve things, but I thought it was pretty clean.
You claim to have 30+ years of webdev experience and yet 2 MEGABYTES of javascript only for those features doesn't feel/look wrong to you?
Hey please don't cross into personal attack. You can make your substantive points without that.
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#54Earlier quoted context omitted.
Of course I don't, but if it helps me do trivial tasks so that I can focus on other things, I might as well use it.
I think it's fine if you find the design of the site a trivial thing that others shouldn't focus on, but it kinda begs the question why you didn't just have the ai generate a much simpler page. Why have the ai generate all this fluff when you just want to show of what you've made? You (rightfully!) care about not wasting your own time, why waste ours?
Sorry for wasting your time.
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#55I want hacker news UX to stay as it is, mostly, but these are features I'd welcome.
What features would you welcome?
All the features I've added to this extension.
But if you want to pick one: Inline replies.
Right now, I have to do a ton of magic to make that happen in order to work around your auth flow. Namely, pulling the auth token out of the other page and then having to keep track of it in session storage.
I could delete a whole lot of code if that was just built in.
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#56Earlier quoted context omitted.
You claim to have 30+ years of webdev experience and yet 2 MEGABYTES of javascript only for those features doesn't feel/look wrong to you?
You're not really answering the question. That's the bundle size, not the amount of code in the project. I've done nothing to try to optimize the bundle size, but I suspect that a lot of it has to do with some of the third party dependencies like mermaid.
Well, i downloaded firefox extension and checked the size of only *.js files without any additional assests - and it's 2 megabytes. Mermaid is around 800kb, so it still leaves over 1 megabyte of javascript.
The amount of abstraction alone for the project of this scope makes me cringe. You introduce unnecessary complexity.
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#57Earlier quoted context omitted.
Sounds good. Another bug or quirk, with Refined, I was able to reply and then tab once to the reply button and hit enter. Now with the "HN's approach to comments and site guidelines." text I can't do that, "comments" and "guidelines" are links so I have to tab three times to get to the reply button which is annoying. Omit that text or change the tab order (this is possible in HTML with the tabindex attribute, just ma…
The orange box is to mark where you are currently focused. If you use the keyboard navigation (keys: j/k), it really helps.
It's distracting for those who don't use hjkl so might be good to have it as an option.
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#58Earlier quoted context omitted.
You're not really answering the question. That's the bundle size, not the amount of code in the project. I've done nothing to try to optimize the bundle size, but I suspect that a lot of it has to do with some of the third party dependencies like mermaid.
Well, i downloaded firefox extension and checked the size of only *.js files without any additional assests - and it's 2 megabytes. Mermaid is around 800kb, so it still leaves over 1 megabyte of javascript. The amount of abstraction alone for the project of this scope makes me cringe. You introduce unnecessary complexity.
Thanks for the feedback!
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#59Earlier quoted context omitted.
What features would you welcome?
All the features I've added to this extension. But if you want to pick one: Inline replies. Right now, I have to do a ton of magic to make that happen in order to work around your auth flow. Namely, pulling the auth token out of the other page and then having to keep track of it in session storage. I could delete a whole lot of code if that was just built in.
By inline replies do you mean you click 'reply' and then a textbox opens in place?
The browser extension I wrote years ago, and which tomhow and I use for moderation, does this. I feel guilty about not having shared it a long time ago, but there just has never been time. Now that LLMs are starting to let me do things I've wanted to do for years, there's a chance I'll actually get to it before the sun dies.
Re: Show HN: Orange Juice – Small UX improvements that make HN easier to read
#60How about a Safari/Mobile Safari extension so iPhone users can use it?
Agreed. Unfortunately, the browser extension tool that I use, wxt [0], doesn't support Safari yet. It seems there are some work arounds, but I haven't gotten to it yet. PR's welcome, of course. =) [0] https://wxt.dev/guide/essentials/publishing.html#safari
Is it just:
pnpm wxt build -b safari xcrun safari-web-extension-converter .output/safari-mv2
And that’s it? Or is there some hidden extra work involved.