3 ms·

All css frameworks really should prefix their classes so you can mix them. And I hope that Google keeps showing them in search results, because while MDN is gr

All css frameworks really should prefix their classes so you can mix them. And I hope that Google keeps showing them in search results, because while MDN is great for in-depth information, most of the time I just need a quick reference of common attributes, and no I don't want it cluttered with a bunch of in-depth information when I am just trying to see what the correct word for something is and how to spell it. Both W3 and MDN are valuable resources for different use cases.

zichy 4y ago
>All css frameworks really should prefix their classes so you can mix them. I don't believe that would work out.
- klibertp 4y ago
  That's a standard practice in languages that don't have namespaces. C and Emacs Lisp have both proven to be "working out" for decades despite using prefixes instead of namespace support.
- jaywalk 4y ago
  Why not? Using prefixes to create a "namespace" is a well-established practice in CSS. I'm not sure there's much of a point in doing it to use multiple frameworks, but there's really no reason it wouldn't work.
skilled 4y ago
I mean, you are more than welcome to share a subjective opinion. "In-depth" in this context means actual relevant content and not a few lines of text. Yeah, sure, one-liners are great and I myself have to Google them all the time because I forget the different variables that shorthand's can take, but W3Schools is on another level when it comes to this. They inherited their authority from a time when content on the web was sparse and thin as a rail. The argument here is not that they don't provide _any_ useful information, the argument is that the inherited authority is making them first results for queries were they obviously should not be first.
- chillfox 4y ago
  I don't believe there is anything obvious about it. I think the way W3 lays out information is likely better for beginners. And MDN is likely better for the average professional developer. So the question is who makes the most searches for those subjects. That said, I do actually see MDN as the first result for some searches.

zichy 4y ago

>All css frameworks really should prefix their classes so you can mix them. I don't believe that would work out.

klibertp 4y ago
That's a standard practice in languages that don't have namespaces. C and Emacs Lisp have both proven to be "working out" for decades despite using prefixes instead of namespace support.
jaywalk 4y ago
Why not? Using prefixes to create a "namespace" is a well-established practice in CSS. I'm not sure there's much of a point in doing it to use multiple frameworks, but there's really no reason it wouldn't work.

skilled 4y ago

I mean, you are more than welcome to share a subjective opinion. "In-depth" in this context means actual relevant content and not a few lines of text. Yeah, sure, one-liners are great and I myself have to Google them all the time because I forget the different variables that shorthand's can take, but W3Schools is on another level when it comes to this. They inherited their authority from a time when content on the web was sparse and thin as a rail. The argument here is not that they don't provide _any_ useful information, the argument is that the inherited authority is making them first results for queries were they obviously should not be first.

chillfox 4y ago
I don't believe there is anything obvious about it. I think the way W3 lays out information is likely better for beginners. And MDN is likely better for the average professional developer. So the question is who makes the most searches for those subjects. That said, I do actually see MDN as the first result for some searches.