Probably only minor ones; three come to mind:

- The web app has to be loaded every time (~700K total right now), whereas the native app works offline. This could be mitigated with a progressive web app, though.

- Fullscreen mode is usually blocked by mobile devices for websites, so you always see e.g. the address bar. That’s just a visual thing, though.

- I’d assume that native audio APIs would allow for more control (and are likely easier to work with too).

I consider the [x]it! file format mostly complete, so in a way there isn’t much for me to do anymore. But I guess that’s also a good thing about such standards – that there is little to no maintenance burden compared to “actual” software.

(Links for reference: https://xit.jotaen.net and https://klog.jotaen.net)

Two things (I suppose) are special about it:

- The timers are “programmable”, so you can freely express your own routines and procedures in a declarative notation.

- The app is all static (no backend): the entire program is encoded in the URL and can be bookmarked or shared/transferred via QR-code.

You can check it out at https://timer.jotaen.net, optionally with a demo program pre-loaded: https://timer.jotaen.net/#demo.

Source code is at https://github.com/jotaen/timer. I’ve also written up a small behind-the-scenes on my blog: https://www.jotaen.net/SAKxq

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

Points: 30

# Comments: 14

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

Points: 1

# Comments: 0

What would you answer if grandma asked you what happens if she loses her physical key?

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.