I don't think it's a joke. It contains some useful stuff like row and col which you can't do with inline CSS.
Show HN: Mimic – class-fied inline CSS
21–30 of 74 posts
Re: Show HN: Mimic – class-fied inline CSS
#22I don't think it's a joke. It contains some useful stuff like row and col which you can't do with inline CSS.
Sure, the row and col stuff makes sense ... which makes it all the more bizarre that the terrible inline-as-classname stuff is included. I fear it might be more a 'troll' than a joke; either that or this person has really got the wrong end of the stick.
Re: Show HN: Mimic – class-fied inline CSS
#23How do you handle advanced selectors? Or hover states? Or priority? Or inheritance? There is a lot of reasons why separating content and styling is benefitial to both the designer and the developer. And why semantic classes, especially with tools like Sass where abstraction and reusability are key, allow to describe the content, not define its looks. That's why we went from color="red" to style="color:red;" to class=…
Although bear in mind that bootstrap still does class="alert alert-danger" so they disagree slightly on that point.
Re: Show HN: Mimic – class-fied inline CSS
#24Re: Show HN: Mimic – class-fied inline CSS
#25Hey, this is a very radical approach. I have great respect for people who ship something (anything!), because they have the vision to see things differently and actually execute this vision.
This may take some getting used to, and a lot of debate if using this is really worth it, but it's something. Nice job! :)
Re: Show HN: Mimic – class-fied inline CSS
#26irony has reached the front end.
Re: Show HN: Mimic – class-fied inline CSS
#27Perfect, now we just need an equally redundant pseudo syntax template system that produces html on top of this.
Re: Show HN: Mimic – class-fied inline CSS
#28That's the equivalent of a front-end developper going into back-end, saying "screw this!" and hardcoding everything.
Urgh.
Also, you cannot use numbers as classes. That's not allowed and may mess up some browsers / devices.
Re: Show HN: Mimic – class-fied inline CSS
#29How do you handle advanced selectors? Or hover states? Or priority? Or inheritance? There is a lot of reasons why separating content and styling is benefitial to both the designer and the developer. And why semantic classes, especially with tools like Sass where abstraction and reusability are key, allow to describe the content, not define its looks. That's why we went from color="red" to style="color:red;" to class=…
Although bear in mind that bootstrap still does class="alert alert-danger" so they disagree slightly on that point.
If you're using sass you just extend alert inside alert-danger. No need for two classes.
Re: Show HN: Mimic – class-fied inline CSS
#30How do you handle advanced selectors? Or hover states? Or priority? Or inheritance? There is a lot of reasons why separating content and styling is benefitial to both the designer and the developer. And why semantic classes, especially with tools like Sass where abstraction and reusability are key, allow to describe the content, not define its looks. That's why we went from color="red" to style="color:red;" to class=…
Although bear in mind that bootstrap still does class="alert alert-danger" so they disagree slightly on that point.
Yes, but "alert" simply means "this is an alert" (so, it may be a box or a popup, depending on where it is on the app/website). "alert alert-danger" means that this alert, whatever shape it is in, is also the alert for danger. It may be red, yellow, blink, have javascript attached to it, etc.
However, it is not "alert alert-red"... What if your client wanted to never use the colour red again because his competition is branded red? You need to go through all the CSS (a few lines of :red needs to be changed to :yellow). You however also need to go through all your view, templates, possibly some hardcoded parts of the code, to change "alert-red" to "alert-yellow"... simply have it "alert-danger".