marcomezzavilla

Yes, but coverage outside the US is surprisingly sparse. Many European countries (Italy, Spain, France, Germany, Greece…) have fewer than 20 points of interest each.

Message received loud and clear.

Just to clarify why there aren’t any demos right now: I originally built the site mostly for myself, as a quick reminder for simple things whose syntax is easy to forget.

The use case was simple: I have my editor open, quickly check the site, copy those 2 or 3 lines, and get back to work, already knowing exactly what they do.

Sharing it publicly came later, so demos/screenshots weren’t really part of the original idea.

That said, I’m happy to take the criticism on board, even if I don’t always agree with the delivery :)

It wasn’t, but I’d be curious to know what specifically gave you that impression.

You’re right: it doesn’t identify the device type, so the title is misleading.

The intended point is that device type is often the wrong thing to detect: a touchscreen laptop may expose both coarse and fine pointers, while a tablet may be connected to a mouse or trackpad. The snippet detects available input capabilities instead, which is usually what the interface should respond to.

I wasn’t particularly careful with the titles, but this one should be "Detect input capabilities". Thanks for the heads-up!

Features built directly into the browser, without requiring a framework or third-party library.

If the term is confusing, I’m open to better wording.

Agree to disagree. I don’t think preferring an in-place reveal makes navigation to a dedicated page a cheap UI/UX decision, it was a deliberate choice.

Each note has a stable URL that can be shared or bookmarked and can be indexed independently. A dedicated page also leaves room for longer content or links to related notes.

Flip interactions also behave differently on touch devices and require more care around keyboard accessibility. It’s a valid alternative, but I don’t see navigation to a standalone document as something inherently undesirable on the web.

Yeah, it makes perfect sense. It’s definitely on my "I really should do this, but…" list.

Not AI, just not a native speaker.

I often end up there by accident and have a laugh every time.

Sure. I was thinking of fairly narrow cases, not ordinary page scrolling:

- A swipe/drag carousel with visible arrows or dots, especially a looping carousel where the native scrollbar does not represent a meaningful start and end

- An accordion or expanding panel that animates to reveal all of its content. During the transition, its intermediate height may briefly produce a scrollbar (and a visual flash), even though the fully expanded state does not need one

- Highly visual or experimental interfaces where scrolling is communicated through another control, or where the scrollable area is decorative and scrolling is not required to access the content

If you mean the "Hide scrollbars" note, I agree 100% (:

There are a few specific situations where it can be useful, but I added the caveat precisely because it’s generally not a good practice.

You’re absolutely right, thanks for the feedback. I initially included live examples (mostly through CodePen), but they were taking too much time to maintain, so I stopped.

The Bash entry was really just a half-finished personal note that I never properly edited. It’s probably out of scope too.

That’s fair, "tricks" may be overselling it. The website is meant to be a small, opinionated collection of features I want to remember, not a replacement for an authoritative reference like MDN. I can probably make that positioning clearer.