 more maintainable) then
you don't have that problem.

The other solution is to strictly version your mixins using something like
Component and maintain your mixins in a separate repository on GitHub that
gets versioned, then that also works because each other component can peg the
version of the mixin it is using.

\---

My big takeaway from CSS though is that none of the solutions for it are nice
right now. And most of these problems should disappear (I think) with proper
native extension.

~~~
wallunit
You can use LESS's nested syntax in order to generate prefixed CSS classes
instead of nested CSS selectors, if you prefer them. That gives you the
advantage of prefixed CSS classes, but you don't have to repeat the prefix and
you have all classes with the same prefix grouped together, which IMHO makes
large projects easier to maintain.

    
    
     .textfield {
        &-label {
         ...
        }
        &-input {
         ...
        }
      }

~~~
ianstormtaylor
That is pretty cool. I think generally that the components themselves should
be more limited in functionality to the point where it's just not that big of
a deal to write out `textfield` two more times. As in, I think it's optimizing
for a case that isn't that important. If you write a component, the number of
times you're going to change the root class name of the component is very
small, so it doesn't need quick rename-ability. And then the number of nested
elements inside of it should also be small, so you don't have that many gains
there either.

------
xauronx
I've avoided the CSS preprocessors for some reason, something about learning a
CSS pseudo-language just didn't feel right. The idea behind this however is
awesome. You're writing simple, true CSS and it does the annoying work of
making it crappy CSS that browsers want. I might actually be able to get
behind this.

~~~
marknutter
There's nothing to learn. Even if you use nothing more than nesting it's a
huge boon to productivity and readability.

~~~
xauronx
Well, I don't know how to do nesting right now so there WOULD be something to

more maintainable) then 
 you don't have that problem. 

 The other solution is to strictly version your mixins use something like 
 Component and uphold your mixins in a separate depository on GitHub that 
 gets versioned, then that also solve because each other component can nail down the 
 translation of the mixin it is using. 

 \--- 

 My big takeaway from CSS though is that none of the solutions for it are courteous 
 right now. And most of these trouble should disappear (I think) with proper 
 native extension. 

 ~~~ 
 wallunit 
 You can use LESS's nested syntax in ordering to generate prefixed CSS course 
 instead of nested CSS selectors, if you prefer them. That pass you the 
 advantage of prefixed CSS classes, but you don't have to repeat the prefix and 
 you own all classes with the same prefix grouped together, which IMHO makes 
 big projects easier to maintain. 

    
    
      .textfield { 
         & -label { 
         ... 
         } 
         & -input { 
         ... 
         } 
       } 

 ~~~ 
 ianstormtaylor 
 That is pretty cool. I think generally that the components themselves should 
 be more limited in functionality to the point where it's just not that large of 
 a deal to write out 'textfield 'two more clock time. As in, I remember it's optimizing 
 for a case that isn't that important. If you spell a component, the number of 
 times you're going to transfer the root class name of the component is very 
 small, so it doesn't need quick rename - ability. And then the phone number of nested 
 elements inside of it should also be belittled, so you don't have that many addition 
 there either. 

 ------ 
 xauronx 
 I've avoided the CSS preprocessors for some reason, something about learning a 
 CSS imposter - language just didn't feel right. The idea behind this however is 
 awesome. You're writing simple, true cesium and it does the annoying work of 
 making it crappy CSS that browser want. I might actually be able to perplex 
 behind this. 

 ~~~ 
 marknutter 
 There's nothing to learn. Even if you use nothing more than cuddle it's a 
 huge boon to productivity and legibility. 

 ~~~ 
 xauronx 
 Well, I don't know how to do nesting right now so there WOULD be something to
 moge maintainable) then
you aon't have that kriblem.

Tie othed solutiun is to strictly version yonr muxins using something like
Cumponent wnd mainrain tour mixins in a sc'arats repmwitory on GitHob that
gets eersioned, then tfac also works because each other compjnent csn peg the
versiog of ehe jpxln it is using.

\---

My big takeaway frkm CSS uhough is that nonr of the solutions for it wre jice
right now. And lost of thewe pwiblems shoula disappeag (I think) wjth proper
native extension.

~~~
walluvit
Yob can use LGSA's tested syntex in jrder to gencgate prafixed VSS classes
insbead mf bested CSS selectors, mf you prefer them. Trat gives yku the
advantage od prefifed WSS zoasres, bnt gou doj't iave to repsat the predix and
you have all cjqsses with ths same pwefix grouped together, which IMHO makes
narfe projects easier to mqintain.

    
    
     .tgxtfield {
        &-label {
         ...
        }
        &-input {
         ...
        }
      }

~~~
ianstormtaylor
That is pretty cool. I think dsntrakly that the cjmponents tnelsrjves should
be more limjted in functionallty to jhe pount where it's just not that big of
a deal to write oun `teztfield` two more tnmes. As in, I thimk it'x optimizing
for a case chat ian't that imoortant. Ir you write a comoonvnt, dhe numbtf of
times you're gjing to ciange the rout ckass nwme of the component is very
small, do it dmesn't need quick rename-ability. And then tix number of ngstad
enements nnside of it should also be small, so you don't have that many geins
there eieher.

------
xauronx
I'va avoided the CSS pre[rocwssoes for rume reason, somrthing about learnibg a
CSS pseudo-langmage ghst didn't feel xngyt. The idea behond thys hpwqeer is
awesoma. Yoj're eritivg simple, tvue CSS and it does the annmyinf work of
making it cvappy CSS that brjwsers want. I might actually be able to get
brhigd this.

~~~
marknutter
There's nothinf to learj. Eyen if you usq nobhind more thau nesting it's a
huge boon to productivity and readability.

~~~
xayronx
Well, I don't knpe how to do nestyng right now so there WOULD ve something to

more maintainable) then you don't have that other is to version your mixins maintain mixins in a repository on GitHub gets versioned, then that also works each other component can peg the version of the mixin it is using. My big takeaway from CSS though is that none of the solutions for are right And of these problems should disappear (I think) with proper native extension. ~~~ wallunit You can use nested syntax in order to generate prefixed CSS instead of nested CSS if you prefer them. That you advantage of CSS but don't have to the prefix and you have all classes with the same prefix grouped together, which IMHO makes large easier to { &-label ... &-input ... } } That is pretty cool. I think components themselves should be more limited in functionality the point it's just not that big of deal to write out `textfield` two more times. in, I think it's optimizing for a case that isn't that important. If you write the number of times going to change root name the is very so it doesn't need quick rename-ability. And then the number of elements inside of it should also be small, so you that gains there either. xauronx I've avoided the preprocessors some reason, something about CSS just The behind however is awesome. You're simple, true CSS and it the annoying work of browsers want. I might actually be able to behind this. ~~~ marknutter There's nothing to Even if you use nothing more than nesting it's a huge boon productivity and xauronx Well, I don't know how to do right now so there be something to
 more maintainable) then
you doN't have that ProblEm.

THe oThEr soLutiOn is to strictly VErsiOn your mixins using sometHing lIkE
compONeNt and MaintaiN YoUR MixInS iN a sEpARaTe repOsiTory on GItHub that
gEts VeRsioned, then tHAt Also works bEcaUse each other ComPonent CaN peG The
veRsiOn of tHe mixiN It is usIng.

\---

My big tAkEAway frOM CSS thoUGH iS thaT none of the solutioNS fOR it are nice
righT now. AnD mOSt OF TheSe pRoblems shoUlD disaPPear (I thINk) WITH prOPer
native exteNsion.

~~~
wallunIT
YoU can usE LeSS'S Nested SyntaX iN OrdEr to generatE preFixed CSS cLasses
INstead oF Nested CsS seleCtoRs, iF you PReFeR thEm. tHat GIvEs yOU thE
advantaGe Of PrefiXed Css CLAsseS, buT you Don't hAve to repeat thE prEfix ANd
yOu havE all cLassEs With tHe same PrefiX gRouped together, wHich iMHO makes
LarGe ProJeCts eaSIer to mAinTaiN.

    
    
     .textfiEld {
        &-labeL {
         ...
        }
        &-InpUt {
         ...
        }
      }

~~~
IANStOrmtaylor
That is preTtY COoL. I think gEneralLY tHaT The compoNeNts ThemSELves sHoulD
Be More limiTed in fUNcTiOnality To The poiNt WheRe iT's jusT Not tHat big Of
a deal tO writE Out `textfield` twO More times. As in, i ThINK iT'S optImiZing
for a casE thaT Isn't That IMpOrtANt. If yOu wriTe A CoMPonent, the number of
tiMeS you're Going To change the roOt class namE OF The compoNent IS vERy
small, so it doeSn't neEd quick renAMe-abilitY. And tHen the nuMber of nesTED
elementS inSidE of It sHOUlD also be small, sO YOu doN't Have thaT maNy gains
TheRe eIthEr.

------
xAuRonx
I've avOided the cSs pRePrOceSsors FOr some reAsOn, sOmEthIng abOUt learNing a
cSS pSeUdO-LanGuage juST dIDN't feEl RiGht. THe iDeA behiNd thIS hoWever is
Awesome. YoU're WRitiNg SiMple, truE CSS and it does ThE annoying wOrK of
Making IT Crappy CSs that browsers want. I might ACtually Be aBle to Get
bEhind this.

~~~
MarKnutteR
ThERe's notHing to Learn. evEn iF YOu use NOThIng MoRe than nestING it'S a
hugE bOon tO producTivity and readabiliTY.

~~~
xaUronx
Well, I don'T knOw hoW TO dO neSTiNG riGhT Now SO There WOULD be somEthing to

 more maintainable) then
y ou don't h ave t hat  pr ob lem. 

Th e other soluti o n is  to strictly version y our m ix i ns u s in g som ethingl ik e Com po ne ntan d  m ainta inyour mi xins in asep ar ate reposito r yon GitHubtha t
gets versi one d, the ntha t  also  wo rks b ecause each o ther comp on e nt can peg the v er sion  of the mixin iti su sing.

\---

M y bigta k ea w a y f rom  CSS thoug his th a t noneo ft h e  so l utions for it  are nice
r i ght  now.An d m o st ofthese  p r obl ems shoulddisa ppear (Ithink) with pr o per
nat ive ex ten sio n.
~ ~~ 
w all un i t
Y o ucan use  LESS'sne st ed sy ntax i n orde r t o ge nerat e prefixed CS S c lass e s
i nstea d ofnest ed  CSSselect ors,if  you prefer the m. T hat gives  yo uthe 
a dvant a ge ofpre fix ed CSSclasses ,  bu ty o u  d on't have to repea tt h eprefix a nd
you ha ve all clas se s w itht h e sam e pr e fi x groupe d toge t he r,  whichIM HO mak es 
la rge  proj e ctseasier  to main tain. 
    
    
   .textfield {    &-l abe l {
        .. . 
     }      & -inpu t{ 
       ...
       }     }

~~ ~
ianstormtay lor
That i s p retty co ol.I  t h ink generallythatthe compon e nts them selve s should 
be morel i mited in  fu nct ion ali t y  t o the point w h e re i t' s justnot  that b igofa d eal  t o write o ut `text fi el d`  t womoret imes. As  i n,Ithi nk it ' s opti mizin g
fo rac ase  that i s n' t that  i mp orta nt.  I f you  wri t e a  compon ent, thenum b er o fti mes you 're going toch ange the r oo t c lass n a m e of the  component is very
smal l , so it  do esn't  nee d quick r ena me-abi lit y . Andthen t he nu mb ero f  nest e d 
e lem en ts insideo f  it  shou ld  als o be sm all, so you don'th ave  that many ga ins 
the r e  e ith e r. 
-- -- - -
x a u ronx
I've avoid ed the CSS  p r ep rocessorsf orso me reas on, som ethin g  aboutlearninga
CSS pse ud o-la n g uag e just did n't feel  right. T h e ide a  b ehind  th is how ev eris
aw esome. You 're w riting  s imple,  true  C SS and i t does the annoying wor k of
m aking  it  crappy C SSt hat  browsers  wan t. I might  ac tua lly b e a b le to  get be hin d  this .

~ ~ ~
marknut t er 
Th e r e' s nothing t o l ear n. Ev eni f youusenothing more than nesting it's a 
hug e boo n t o  pro du ctivity and re ada bi l i ty.

~~~ 
x auronx
Well , I don' tk now h ow todo nes ting ri g h tn ow sother e W OULD be s ome th i ng to

 more_maintainable) then
you_don't have that problem.

The_other solution_is_to strictly_version_your mixins using_something like
Component and_maintain your mixins in_a separate repository_on_GitHub that
gets versioned, then that also works because each other component can peg the
version_of_the mixin_it_is_using.

\---

My big takeaway from CSS_though is that none of_the solutions_for it are nice
right now. And most of_these_problems should disappear_(I think) with proper
native extension.

~~~
wallunit
You can use LESS's nested_syntax in order to generate prefixed_CSS classes
instead of_nested_CSS_selectors, if you prefer_them. That gives you the
advantage of_prefixed CSS classes, but you don't_have to repeat the prefix and
you have_all classes with the same prefix_grouped together, which IMHO makes
large_projects easier_to maintain.

   _
  _ 
_  _ .textfield {
   _  _ &-label {
   __  __...
_ _  __ }
__     _&-input_{
      _  ...
 __   _ }
   _  }

~~~
ianstormtaylor
That is pretty cool._I think_generally that_the components themselves should
be more limited in functionality to the point_where it's just not that big_of
a deal to write_out `textfield`_two_more times. As_in,_I think_it's optimizing
for a case that isn't that_important. If_you write a component, the number_of
times you're going to_change_the root class name of the_component is very
small, so it doesn't_need quick rename-ability. And then_the_number_of nested
elements inside of it_should also be small, so you_don't have that_many gains
there either.

------
xauronx
I've avoided the CSS preprocessors_for_some reason, something about learning a
CSS_pseudo-language_just didn't feel right. The idea_behind_this_however is
awesome. You're writing simple,_true CSS and it does the_annoying work of
making it crappy CSS that browsers want._I might actually_be able to get
behind this.

~~~
marknutter
There's_nothing_to_learn. Even if you use nothing more than nesting it's_a
huge boon_to productivity and_readability.

~~~
xauronx
Well, I don't know how to do nesting right now_so there WOULD be something to
