The almost-lost art of rosin potatoes - https://news.ycombinator.com/item?id=41991352 - Oct 2024 (168 comments)
15,025 karma · joined April 6, 2011
The almost-lost art of rosin potatoes - https://news.ycombinator.com/item?id=41991352 - Oct 2024 (168 comments)
This is a more detailed, informative critique of the Tahoe change than is in the post, where all that's specifically written as evaluation is,
>Seriously, why??? I thought Liquid Glass was supposed to “bring greater focus to content”? Darkening videos brings less focus to content!
So in terms of volume, this isn't much. In terms of potential effects, it becomes a question of how well players utilize their teams' two challenges (teams retain challenges if they correctly use them, but only the batter, the catcher, and the pitcher can request a challenge).
It all becomes an interesting question in terms of strategies. A catcher when he's batting? Does he want to risk one of his team's challenges as a batter that he might want for his pitcher? A mediocre hitter in a low-stakes situation? Does he want to risk one of his team's challenges? What about a really good hitter in a low-stakes situation? Lots here for teams to consider, and since it's up to the players to decide on a challenge (not managers or coaches), teams will have to determine their approaches such that players can make decisions without assistance.
Most beneficial for me is its customizations that can be applied to all shows or configured for individual shows. For example, all episodes for all shows can be set to play at 1¼x speed, but one show could be set to play at 1x speed. For me, the interview format can be at the faster speed, but the music podcast is better at regular speed. Similarly, users could set all shows' episodes to start at the 30-second mark because of, say, opening ads, but a specific show could be set to start at a different time because its opening is unlike the others.
I listen to enough shows that these configuration options make the app great for me. It's been a long time since I tried alternatives, but none of them ever stuck for more than (at most) a few days because the presentation or lack of customizations were less satisfying or convenient.
Truthfully, just writing this has compelled me to give the developer another in-app tip. It's been years since I did that and I must average at least 20 hours of use a week.
I think your immediately following phrase captures the idea well: "Curiosity withers under repetition," and that's compounded by topical subjects inherently being ephemeral.
I said nothing of how I regard the regulatory process. Don't be presumptuous; doing so disregards the site guidelines.
>Converse curiously
>And the inspector and everyone his organization works for say this is all great, and of course they've got self-serving metrics to prove it, because those organizations naturally fill up with people who don't question the premises of what they're doing.
I've been through dozens of FDA facility inspections (and dozens more from non-governmental inspection agencies that are regularly used in the food industry, some of which I might say are more strict than the FDA). Nothing you've said matches my experience in any way.
https://news.ycombinator.com/item?id=45236479
Copying their comment to here:
I have redone the classical exercise of writing a tiny OS kernel with time sharing, which manages a couple of user threads. My goal was to experiment specifically on RISC-V + OpenSBI. Additionally, I wanted to explore Zig a little bit, so that was the language used instead of the traditional C, but it should be straightforward how to do the same experiment in either C or Rust.
It's definitely very rough around the edges, and it's more of an experiment and an intro for people who want to go through step 0 of learning OS kernel development and computer architecture. Nevertheless, I hope it is still a fun experimental thing to play with over the weekend!
The full walkthrough and the GitHub link are available at the link posted!
World's Oldest joke traced back to 1900 BC (2008) - https://news.ycombinator.com/item?id=27374675 - June 2021 (87 comments)
>This is the previous thread from then:
I didn't pick those; they're the ones I saw. I missed the one you added. Thanks.
Did Siri spy on you? You could receive part of a $95M settlement - https://news.ycombinator.com/item?id=44004682 - May 2025 (2 comments)
Siri listened in on private conversations, Apple pays out $95M in lawsuit - https://news.ycombinator.com/item?id=43928424 - May 2025 (4 comments)
Note the article linked here from May indicates the deadline for filing a claim passed months ago.
https://www.theparisreview.org/podcast/6075/the-smoker-by-ot...
Honesty Boxes in Scotland (2024) - https://news.ycombinator.com/item?id=44824684 - Aug 2025 (59 comments)
Privately-Owned Rail Cars - https://news.ycombinator.com/item?id=33460052 - Nov 2022 (244 comments)
Ride in your privately-owned rail car to see North America - https://news.ycombinator.com/item?id=10324823 - Oct 2015 (2 comments)
https://www.macrumors.com/2025/06/17/ios-26-use-as-ringtone-...
The Value of Hitting the HN Front Page - https://news.ycombinator.com/item?id=44584461 - July 2025 (6 comments)
This is what tptacek was noting in the search results he posted: Dang has made clear that HN is okay with having its readers "work a little."
>Edit out swipes.
>Thoughtful criticism is fine, but please don't be rigidly or generically negative.
>Please don't fulminate. Please don't sneer...
>Eschew flamebait. Avoid generic tangents. Omit internet tropes.
Even so, I haven't seen any basis for thinking article summaries would change those community behaviors.
Here's the line in the guidelines that seems to be eluding you in this whole discussion:
>It's implicit in submitting something that you think it's important.
The fact that an article has been submitted is the "better guide" the site uses to indicate "whether the article is worth reading." Tomhow's comment says why HN has not seen this to be something that should change.
This reads as if you're confusing HN the site (and its goals) with HN the community (and the behaviors of those people). The ideal is that the site goals and the community behavior would be identical. We know that's not how things unfold in practice.