4 ms·
Ok, so usually I'm not a fan of the sarcastic "Hey, you just reinvented X! We've been doing that since the 90s!" But in this case: <h2 class=“f2 helvetica
by habitue 8y ago
Ok, so usually I'm not a fan of the sarcastic "Hey, you just reinvented X! We've been doing that since the 90s!"
But in this case:
<h2 class=“f2 helvetica strike”>Fancy title <strong>with some bold</strong></h2>
Tachyons really seems to have reinvented the <font> tag. Like, exactly. Come on guys.
Edit: Apparently I'm out of the loop, and this style (atomic css) is now good. I'll take this as an opportunity to learn to refrain from making snide comments about fields I am not deeply involved in
- abraham 8y agoThe font tag is considered obsolete by MDN. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fo...
- nocman 8y agoI'm trying to understand your point. Are you saying that in support of habitue's comment, or as a counter-argument?
- habitue 8y agoI interpreted abraham's comment as "Right, it's just like the font tag, but the font tag is deprecated, so we use this instead". Implicit in my original comment was that "everybody knows the font tag is a bad idea so this is a bad idea too", which I think abraham missed. That being said, apparently I'm wrong and this style is back in vogue. CSS Zen garden style design has just failed hard apparently, so this is how things are done.
- atombender 8y agoYou missed the point here. This is a marriage of two existing formats: Markdown, which you probably know, and HAML, a templating language that was popular with Rails and Sinatra for a while (less so these days, I think). HAML uses CSS-like syntax to allow you to write HTML more succinctly: %div.foo.bar means <div class="foo bar">, for example. It has tons of short of concise syntax to make it a more pleasant alternative to HTML. It uses whitespace-sensitive indentation, like Python, so no end tags. This isn't reinventing the font tag. It's an alternative to putting HTML in Markdown, which many people do because Markdown is very limited. Sometimes you need to insert something that isn't supported. Not saying this is good, just explaining how your criticism doesn't apply.
- habitue 8y agoSorry for the confusion, I'm not criticizing hamdown, I'm commenting on the tachyon project that is linked to from the hamdown documents
- jasim 8y agoThat's not what Tachyons is. The people who made it and those who advocate Functional CSS (Tachyons, Tailwind, Atomic CSS etc.) have a clear idea what HTML < 5 used to be, what inline css is, why BEM and SMACSS exist, what js-in-css is, and in general know what they're doing. I'm saying that to help apply a principle of charity when evaluating this idea that on first blush looks like insanity. But there is something in there. Readings to get started: https://johnpolacek.github.io/the-case-for-atomic-css/ https://johnpolacek.github.io/the-case-for-atomic-css/
- deltron3030 8y agoWhy not go one step further (like Style Elements in Elm), and reduce CSS & HTML to layout and style? https://mdgriffith.gitbooks.io/style-elements/content/ https://mdgriffith.gitbooks.io/style-elements/content/ Accessibility is often mentioned when it comes to the separation of concerns between HTML layout and CSS layout, but why would somebody try to adress blind people differently when it comes to semantics and hierachy? Wouldn't you want the same experience as seeing people?
- habitue 8y agoOk, that's interesting. I guess I am out of the loop on this one