I don't really want to be negative but I really can't see how this could be used for anything other than a quick prototype scenario. I'm never going to add 126kb of css to a project just for shortcuts like this, it just doesn't make sense given that the large majority of that added css weight will never be used.
Show HN: Mimic – class-fied inline CSS
41–50 of 74 posts
Re: Show HN: Mimic – class-fied inline CSS
#42That'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.
Hi thanks for looking. Could you elaborate on your last statement?
Re: Show HN: Mimic – class-fied inline CSS
#43This is by far the most insane and stupid idea I have seen this year.
Well, the year isn't over yet :P
Re: Show HN: Mimic – class-fied inline CSS
#44So now I don't have to use inline styles, just spam my css file with margin:0-100 and padding:0-100 classes, and I'm good to go?
Hi, thanks for looking.
You don't have to do anything that you don't want to do.
Re: Show HN: Mimic – class-fied inline CSS
#45Earlier quoted context omitted.
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 i…
Yes, I fully understand why "alert-danger" is better than "alert-red". What I don't quite get is why "alert alert-danger" is better than "alert-danger". Isn't it possible - using a preprocessor - to maintain alert-danger, alert-warning etc? If multiple classes must be used, why not just "danger" which then allows the red coloration to be shared amongst different object types without being repeated.
Re: Show HN: Mimic – class-fied inline CSS
#46This doesn't result in very readable markup or have any of the benefits of actual inline CSS, so I don't really see the need here.
I appreciate you taking a look, thanks!
Re: Show HN: Mimic – class-fied inline CSS
#47I 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.
Thanks for taking a look, I appreciate everyone's opinion on things. Could you share why you think this way?
Re: Show HN: Mimic – class-fied inline CSS
#48Re: Show HN: Mimic – class-fied inline CSS
#49This is getting crazy.
Thanks for taking a look. Could you share why you feel that way?
Re: Show HN: Mimic – class-fied inline CSS
#50This is getting crazy.
[deleted]