5 ms·

Unfortunately, even proficient developers are having trouble due to some misguided technical choices those websites are making: https://twitter.com/sindresorhus

by dictum 9y ago

Unfortunately, even proficient developers are having trouble due to some misguided technical choices those websites are making: https://twitter.com/sindresorhus/status/900005504931438593 https://twitter.com/sindresorhus/status/900005504931438593

JosephRedfern 9y ago
If those websites don't wish to support skinning, I don't see how the technical choices are misguided.
- Cyph0n 9y ago
  True, but that still doesn't contradict the point made above regarding how the skinning community is a dying breed. Edit: I now realize that, taken out of context, my comment sounds pretty twisted.
- smadge 9y ago
  Originally stylesheets were meant to be recommendations. It was envisioned that user agents, users, and web pages would have their own, separate stylesheets, and the user agent would negotiate between the different stylesheets to determine the final style. I would argue that Twitter is going against the original spirit and best practices of the web with their technical decision to use css-in-js.
  - dictum 9y ago
    Exactly. The Web is a medium with built-in customizability. This "our product is perfect and must be used as is" attitude reminds me of a relatively recent example that seems to be dying down: mobile websites that used the `maximum-scale=1 ` value in `<meta name="viewport"`. This disabled zooming in mobile devices. This was an accessibility issue that affected people who otherwise don't encounter other accessibility issues. If it were simply a matter of providing the smallest payload to clients, these sites could provide some sort of external manifest/source map mapping human-readable class names to hashes.
  - zimablue 9y ago
    Meanwhile most people who have to use the web as a platform to build things view it as an incredibly painful mash of half implemented ideas and couldn't care less what the founders intended. Let's stop using divs for presentation whilst we're at it and spend man-years on picking the right semantically named elements with no benefit to anyone anywhere ever. No ajax or js either, I'm pretty sure they didn't envisage that.
    - smadge 9y ago
      To be honest, yes. The web was designed for hyperlinked documents. 90% of what I use the web for is still following links to pages with text and images. It is an unfortunate historical accident that people are trying to build thick client interactive applications using a technology envisioned and designed for sharing documents.
TomMarius 9y ago
Why exactly misguided? Because it doesn't allow you to hack their site? Uh... Edit: read the FAQ, downvotes are not for disagreement.
- dang 9y ago
  That's not in the HN FAQ. Downvoting for disagreement has always been allowed here. Some historical links at https://news.ycombinator.com/item?id=16131314 https://news.ycombinator.com/item?id=16131314. Commenting about downvotes in arguments isn't ok, though: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html.
RobertRoberts 9y ago
react/boostrap

by dictum 9y ago

JosephRedfern 9y ago

If those websites don't wish to support skinning, I don't see how the technical choices are misguided.

Cyph0n 9y ago
True, but that still doesn't contradict the point made above regarding how the skinning community is a dying breed. Edit: I now realize that, taken out of context, my comment sounds pretty twisted.
smadge 9y ago
Originally stylesheets were meant to be recommendations. It was envisioned that user agents, users, and web pages would have their own, separate stylesheets, and the user agent would negotiate between the different stylesheets to determine the final style. I would argue that Twitter is going against the original spirit and best practices of the web with their technical decision to use css-in-js.
- dictum 9y ago
  Exactly. The Web is a medium with built-in customizability. This "our product is perfect and must be used as is" attitude reminds me of a relatively recent example that seems to be dying down: mobile websites that used the `maximum-scale=1 ` value in `<meta name="viewport"`. This disabled zooming in mobile devices. This was an accessibility issue that affected people who otherwise don't encounter other accessibility issues. If it were simply a matter of providing the smallest payload to clients, these sites could provide some sort of external manifest/source map mapping human-readable class names to hashes.
- zimablue 9y ago
  Meanwhile most people who have to use the web as a platform to build things view it as an incredibly painful mash of half implemented ideas and couldn't care less what the founders intended. Let's stop using divs for presentation whilst we're at it and spend man-years on picking the right semantically named elements with no benefit to anyone anywhere ever. No ajax or js either, I'm pretty sure they didn't envisage that.
  - smadge 9y ago
    To be honest, yes. The web was designed for hyperlinked documents. 90% of what I use the web for is still following links to pages with text and images. It is an unfortunate historical accident that people are trying to build thick client interactive applications using a technology envisioned and designed for sharing documents.

TomMarius 9y ago

Why exactly misguided? Because it doesn't allow you to hack their site? Uh... Edit: read the FAQ, downvotes are not for disagreement.

dang 9y ago
That's not in the HN FAQ. Downvoting for disagreement has always been allowed here. Some historical links at https://news.ycombinator.com/item?id=16131314 https://news.ycombinator.com/item?id=16131314. Commenting about downvotes in arguments isn't ok, though: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html.

RobertRoberts 9y ago

react/boostrap