Comments URL: https://news.ycombinator.com/item?id=47625099

Points: 4

# Comments: 0

To me, your response would have been just fine with only the last sentence.

That I understand, I’m mainly wondering why all that would have to happen automatically by merely opening a folder.

My personal preference may differ here, but for things like running a build or starting a dev server, I usually prefer to trigger them manually, and not have them silently executed only by me browsing through the sources.

Therefore I’m trying to understand whether there are legitimate use-cases for this “auto-run on open folder” feature besides the obvious convenience aspect of saving one or two extra clicks.

Is it only for convenience so it already `npm i` or `npm start` without you having to do anything, or are there any other legitimate purposes beyond that?

s/east/west/

(I.e., the area left of the power station.)

It also would be interesting to learn how many rides had been excluded altogether, just to put things into perspective.

Maybe I’m misunderstanding something here, but I find that nowadays the process of buying high-quality, DRM-free MP3 music is as simple and straightforward as it can be: you purchase the files (on Bandcamp, Amazon, Apple Music, etc.), download them legally, and then physically own them forever.

By the way, when purchasing through Bandcamp, 80+% goes to the artist (https://bandcamp.com/fair_trade_music_policy). So not only do you own the music, but you also make sure the artist is properly paid for their work.

- Clicking “Demo” (for macOS) points to the 3.2.0 ARM version

- Clicking “Intel Mac” points to the 3.1.0 (!) Intel version

The Github release page appears to list all available versions: https://github.com/whyboris/Video-Hub-App/releases

To me, it would have been clearer to avoid the “Demo” button label altogether and be explicit about the different versions and OS targets. Also, I think the visual hierarchy of the two respective buttons is too subtle.

I think the main selling point of passkeys is their ability to prevent phishing.

A 32-character password + TOTP can still be entered on a phishing website, e.g. if you happen to follow a fabricated link. With passkeys, this is not possible by design.

> I find that the drag and drop experience can quickly become a nightmare, especially on mobile.

To me, drag and drop is only a nightmare on mobile. On desktop (using a mouse or trackpad), drag and drop actually works quite well.

Your design experiment reminds me of a recent talk of Scott Jenson, where he talked about how we just took over established UX patterns from desktop to mobile as is, and how that created all sorts of nuisances. (https://youtu.be/1fZTOjd_bOQ?t=1565)

If mobile drag&drop was implemented like you are suggesting from the very start, I actually might have preferred that over the situation we now ended up with.

One technical note on your implementation: on certain mobile browsers, there is a glitch where the UI can jump around as the browser dynamically slides top or bottom menu bars in and out.

I wouldn’t say so. The “Increase Contrast” and “Show Borders” accessibility options make liquid glass just bearable to me, but the new UI design is still ungracefully buggy and unnecessarily hard(er) to use. (See e.g. https://www.nngroup.com/articles/liquid-glass/ for a detailed discussion.)

Sure, life goes on. However, considering the price tag of an iPhone/iPad, I understand how iOS 26 is off-putting to so many people – despite all the other new features.