What does native mean in this context?
Small, native web tricks worth remembering
41–50 of 73 posts
Re: Small, native web tricks worth remembering
#42[flagged]
Re: Small, native web tricks worth remembering
#43Best resource for proper HTML+CSS development is Jason Knight AKA deathshadow's CUTCODEDOWN (cutcodedown.com at Web archive) and his articles at Medium and CodePen (user Jason Knight).
How is an archived web site supposed to be a good resource on modern html and css development exactly?
We plateaued about 10 years ago right?
Re: Small, native web tricks worth remembering
#44I'm not sure where the design for this site came from, but I hate that it brings you to a new page to show you something that could have probably fit in the big ass buttons on the first page lol. It took my by surprise the the card didn't flip over to show you the details and instead just navigated to a new page. I'm not a design guy- more of a backend, do everything in a TUI kind of guy- so if I'm caught off guard by a cheap UI/UX decision, then that's a serious problem.
Re: Small, native web tricks worth remembering
#45I'm not sure where the design for this site came from, but I hate that it brings you to a new page to show you something that could have probably fit in the big ass buttons on the first page lol. It took my by surprise the the card didn't flip over to show you the details and instead just navigated to a new page. I'm not a design guy- more of a backend, do everything in a TUI kind of guy- so if I'm caught off guard b…
Wait... there's no demonstrations of any of these "tricks" on the site? Am I looking at a broken version of the site? This could have been a markdown file lol hos is this so high up in HN?
Re: Small, native web tricks worth remembering
#46Earlier quoted context omitted.
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.
Silly question, why not just render the html on the pages? e.g. the popover is something I wanted to see
Yeah, it makes perfect sense. It’s definitely on my "I really should do this, but…" list.
Re: Small, native web tricks worth remembering
#47And yet that site has horizontal scroll bars.
Re: Small, native web tricks worth remembering
#48I'm not sure where the design for this site came from, but I hate that it brings you to a new page to show you something that could have probably fit in the big ass buttons on the first page lol. It took my by surprise the the card didn't flip over to show you the details and instead just navigated to a new page. I'm not a design guy- more of a backend, do everything in a TUI kind of guy- so if I'm caught off guard b…
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.
Re: Small, native web tricks worth remembering
#49What does native mean in this context?
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.
Re: Small, native web tricks worth remembering
#50I'm not sure where the design for this site came from, but I hate that it brings you to a new page to show you something that could have probably fit in the big ass buttons on the first page lol. It took my by surprise the the card didn't flip over to show you the details and instead just navigated to a new page. I'm not a design guy- more of a backend, do everything in a TUI kind of guy- so if I'm caught off guard b…
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 keyboa…
Does it add time, or break eye-focus?