Design proof that being "unique" doesn't mean "good".
I'm certainly glad they like what they've built. But it breaks a lot of design concepts that help with UX (some in micro ways that aren't really noticeable without the aggregate effect). The "max character width" is a really valuable thing for "readability". But why bother with learning design when you're using all of the TECHNICAL specs 'exactly as specified'. Why bother with design responsibility when you're already absolving yourself of technical responsibility ('it should not be our job to work around bad tech...').
Of course, the most galling thing is that they're not actually using the spec, as it is specified. Using `section` tags everywhere is inappropriate. They are meant to break up content in the `article` tag.
But, okay, whatever; you're going to cling to the spec but still ignore the parts of it you don't like. Fine. Like they said, it's not causing screen-reader issues, so who cares, right? Except that they ALSO don't use the `header` tag within those sections to denote what is clearly a header. Not a "heading" (h1-6, used for breaking up paragraphs in articles), maybe, since it's not in an article and that can cause funky screen-reader performance, but there's no reason to NOT use a `header` tag. This use case is literally what it was made for; giving a generic header that you can style and make accessible on your own. So why use a `section` tag erroneously, but then eschew using the `header` tag for the exact purpose you need? (why use it? screen readers/accessibility)
Nothing in this seems like "well-considered design". Rather it seems like "good enough, and how I like it." Which is a perfectly wonderful way to design and run a website! It's just kind of shitty to then go write an entire article telling anyone who misunderstands your uniqueness for a different flavor of uniqueness that you are actually doing everything exactly right and that anyone who dislikes your site should take their "problems" elsewhere. A fine enough attitude, if you're in to that kind of gatekeeping, but I've never found it compelling or endearing.
> It's just kind of shitty to then go write an entire article telling anyone who misunderstands your uniqueness for a different flavor of uniqueness that you are actually doing everything exactly right and that anyone who dislikes your site should take their "problems" elsewhere.
I'm certainly glad they like what they've built. But it breaks a lot of design concepts that help with UX (some in micro ways that aren't really noticeable without the aggregate effect). The "max character width" is a really valuable thing for "readability". But why bother with learning design when you're using all of the TECHNICAL specs 'exactly as specified'. Why bother with design responsibility when you're already absolving yourself of technical responsibility ('it should not be our job to work around bad tech...').
Of course, the most galling thing is that they're not actually using the spec, as it is specified. Using `section` tags everywhere is inappropriate. They are meant to break up content in the `article` tag.
But, okay, whatever; you're going to cling to the spec but still ignore the parts of it you don't like. Fine. Like they said, it's not causing screen-reader issues, so who cares, right? Except that they ALSO don't use the `header` tag within those sections to denote what is clearly a header. Not a "heading" (h1-6, used for breaking up paragraphs in articles), maybe, since it's not in an article and that can cause funky screen-reader performance, but there's no reason to NOT use a `header` tag. This use case is literally what it was made for; giving a generic header that you can style and make accessible on your own. So why use a `section` tag erroneously, but then eschew using the `header` tag for the exact purpose you need? (why use it? screen readers/accessibility)
Nothing in this seems like "well-considered design". Rather it seems like "good enough, and how I like it." Which is a perfectly wonderful way to design and run a website! It's just kind of shitty to then go write an entire article telling anyone who misunderstands your uniqueness for a different flavor of uniqueness that you are actually doing everything exactly right and that anyone who dislikes your site should take their "problems" elsewhere. A fine enough attitude, if you're in to that kind of gatekeeping, but I've never found it compelling or endearing.