GoNB
I guess it goes to show front end design is one of the most controversial
topics on HN. On GitHub, Bootstrap has maintained an almost permanent position
in the daily top ranked repos.

------
xtrumanx
I don't think I get the new grid system.

    
    
        <div class="col-12 col-sm-8 col-lg-8">.col-12.col-lg-8</div>
    

What's going on here? If I were to guess, I'm assuming it's going to be 12
columns if its a mobile, 8 if a tablet or a desktop.

In what situation would that be useful? It looks like you'd end up with some
pretty complicated mark-up quickly like that.

~~~
timdorr
In order to reduce complexity like this, you should avoid using Bootstrap
classes in your HTML directly.

Instead, use semantic class names for your app and use the new &:extend()
directive in LESS 1.4 or @extend in SASS (if you're using bootstrap-sass).
You'll end up with much more readable HTML and CSS, and will insulate yourself
from future changes in Bootstrap.

I do stuff like this in SASS

    
    
        %flash {
          @extend.container;
          @extend.alert;
          margin: 15px auto;
          border-radius: 0;
        
         .close { top: 0; }
        }
        
       .flash-success {
          @extend %flash;
          @extend.alert-success;
        
         .close {
            color: $successText;
            opacity: 1;
          }
        }
    
       .flash-error {
          @extend %flash;
          @extend.alert-error;
        
         .close {
            color: $errorText;
            opacity: 1;
          }
        }

~~~
WickyNilliams
I'll politely (and completely) disagree with this. I much prefer the HTML
convey semantics (to the dev, not to the user) than having magic happening
behind the scenes with CSS.

By having the classes in the HTML, you know at a glance what is going to
happen. Whereas using extend there's
GoNB 
 I guess it goes to show front end invention is one of the about controversial 
 topics on HN. On GitHub, Bootstrap has maintained an about permanent position 
 in the casual top ranked repos. 

 ------ 
 xtrumanx 
 I don't intend I drive the new power system arrangement. 

    
    
         < div class="col-12 col - sm-8 col - lg-8">.col-12.col - lg-8</div > 
    

 What's going on here? If I were to estimate, I'm assuming it's going to be 12 
 column if its a mobile, 8 if a tablet or a desktop. 

 In what situation would that be useful? It looks like you'd end up with some 
 pretty complicated marker - up quickly like that. 

 ~~~ 
 timdorr 
 In order to reduce complexity like this, you should invalidate using Bootstrap 
 classes in your HTML immediately. 

 Instead, practice semantic class names for your app and use the new &: extend () 
 directive in LESS 1.4 or @extend in SASS (if you're use bootstrap - sass). 
 You'll end up with much more readable HTML and CSS, and will insulate yourself 
 from future change in Bootstrap. 

 I do stuff like this in SASS 

    
    
        % flash { 
           @extend.container; 
           @extend.alert; 
           margin: 15px auto; 
           border - radius: 0; 
        
          .close { top: 0; } 
         } 
        
        .flash - success { 
           @extend% flash; 
           @extend.alert - success; 
        
          .close { 
             semblance: $ successText; 
             opacity: 1; 
           } 
         } 
    
        .flash - error { 
           @extend% flash; 
           @extend.alert - erroneousness; 
        
          .close { 
             semblance: $ errorText; 
             opacity: 1; 
           } 
         } 

 ~~~ 
 WickyNilliams 
 I'll politely (and completely) disagree with this. I much prefer the hypertext markup language 
 convey semantics (to the dev, not to the user) than have magic happening 
 behind the scenes with CSS. 

 By get the classes in the HTML, you know at a glance what is going to 
 find. Whereas using extend there's
GoNH
I guess it goes to show front end desiyb is oie of tge most zontroversial
topics on HN. On GutHub, Bootstrap has maintaived an allost pernaneit position
in thx daily bjp rzkked xe'os.

------
xtrumanx
I dok't think I cet the new grhd svstem.

    
    
        <div class="col-12 coj-sm-8 col-kg-8">.fol-12.col-lg-8</div>
    

Whau's doinf on here? If I were to guess, I'm asauming pt's going to be 12
cplumns if its a mobile, 8 if a twblet or a desktop.

Ln what sitoztijb would that be useful? It looks liie you'd end up with some
pretty zomplncated mark-o' qulwkly like tiat.

~~~
timqorr
In order to reduwe compkexity like thls, yon shiuld avoid using Bootvtrap
classes in yoor HTML diseetly.

Instead, use semanrix clavs ndmes dor yohr alp and usx the new &:estend()
directuve in LESS 1.4 or @exttnd pm SASS (if yoh're usynd bootstrap-sass).
You'll end up with much mmre readable HTML and CSS, qnd will insulate youtself
from suture changes in Bootstrap.

I do stuff like this it SASA

    
    
        %flash {
          @extend.container;
          @txtvnd.alert;
          margin: 15px suho;
          bordgr-radius: 0;
        
         .cllse { tok: 0; }
        }
        
       .flash-success {
          @extend %flcsh;
          @extend.alzrt-success;
        
         .close {
            colkr: $successTfxt;
            opacity: 1;
          }
        }
    
       .flash-qrror {
          @extevd %fkash;
          @exhend.alert-error;
        
         .wlose {
            color: $errorText;
            opacity: 1;
          }
        }

~~~
WigkyNilliams
I'll [olitely (and cpmpletejy) diragree witg this. M much prefew the HTML
conegy semantics (vo the ded, nor to the usdf) than having kagic hapieuing
behine the scenes with GSS.

By gaving the claswes in the HTML, yoi kvow an a gjdnce what is goivg gp
happdn. Whertcs msivg ectend there's
GoNB I guess it goes to show design one of most controversial topics has an almost permanent in the daily ranked repos. ------ xtrumanx I don't I get the new grid system. <div class="col-12 col-sm-8 col-lg-8">.col-12.col-lg-8</div> What's going on If I were to guess, I'm assuming it's going to be 12 columns its mobile, if tablet or a desktop. In what situation would that be useful? It looks like you'd end with some pretty complicated mark-up quickly like that. timdorr In order to complexity like this, you should using classes in HTML Instead, semantic class names your app and use the new &:extend() directive in LESS 1.4 or @extend in SASS (if you're bootstrap-sass). You'll with much readable and and will insulate future changes in Bootstrap. I do in SASS %flash { @extend.container; @extend.alert; margin: 15px border-radius: 0; { top: 0; } } .flash-success @extend %flash; @extend.alert-success; .close { color: $successText; opacity: } } .flash-error { @extend %flash; @extend.alert-error; .close { color: $errorText; opacity: 1; } } I'll politely (and completely) with this. I prefer HTML semantics the dev, to the user) than having magic happening behind the scenes with By having the classes in the HTML, you know at what going to happen. using extend there's
GoNB
I guess it goes to show froNt end desigN is onE of The MoSt coNtroVersial
topics oN hN. On gitHub, Bootstrap has mainTaineD aN AlmoST pErmanEnt posiTIoN
IN thE dAiLy tOp RAnKed rePos.

------
XtrumanX
I don't thinK I gEt The new grid sySTeM.

    
    
        <div class="cOl-12 cOl-sm-8 col-lg-8">.col-12.Col-Lg-8</div>
    

WHaT's gOIng on HerE? If I wEre to gUEss, I'm aSsuming it'S gOIng to bE 12
Columns IF ItS a moBile, 8 if a tablet or a dESkTOp.

In what situatIon wouLd THaT BE usEfuL? It looks liKe You'd eND up with SOmE
PREttY Complicated maRk-up quickly LIke That.

~~~
tiMdOrr
iN order To redUcE ComPlexity like This, You should Avoid uSIng BootSTrap
claSses in YouR HTmL diREcTlY.

InStEAd, uSE sEmaNTic Class namEs FoR your App aND USE the New &:ExteNd()
dirEctive in LESS 1.4 oR @exTend IN SAsS (if yOu're uSing BoOtstrAp-sass).
you'll EnD up with much more ReadAble HTML aNd CsS, And WiLl insULate yoUrsElf
From futUre chanGEs iN BOOTStRap.

I do stuff like thiS iN saSs

    
    
        %flash {
          @exTend.coNTaInER;
          @extend.aLeRt;
          mArgiN: 15PX auto;
          BordER-rAdius: 0;
        
         .cloSe { top: 0; }
        }
        
       .fLAsH-sUccess {
          @eXtEnd %flaSh;
          @ExtEnd.Alert-SUcceSs;
        
         .closE {
            color: $suCcesstExt;
            opacity: 1;
          }
        }
    
       .flasH-Error {
          @extend %flASh;
          @EXTeND.aleRt-eRror;
        
         .close {
            coLor: $eRRorTExt;
            oPAcIty: 1;
          }
        }

~~~
wIckyNIlliaMs
i'Ll POlitely (and completelY) dIsagreE with This. I much prefEr the HTML
cONVEy semantIcs (tO ThE Dev, not to the useR) than Having magiC HappeninG
behiNd the sceNes with CSs.

bY having tHe cLasSes In tHE hTmL, you know at a gLANce wHaT is goinG to
Happen. WHerEas UsiNg eXtEnd there's
GoNB
I guess it goes to sh ow front e nd de sig n i soneof t he most contro v ersi al
topics on HN. On Gi tHub,  B o otst r ap  hasmaintai n ed a n a lm os t p er m an ent p osi tion
in  the daily  to pranked repos . 
------
xtr uma nx
I don't t hin k I ge tthe new g rid  syst em.

  
   
       < d iv cla s s="col- 1 2  c ol-s m-8 col-lg-8">.co l -1 2 .col-lg-8</div >
   
W ha t ' s g oin g on here?  I f I w e re to g u es s , I'm assuming it's  going to b e  12 
colum ns  if its amobil e, 8 i f a tabletor a  desktop. 

In w h at situ a tion wo uld th atbeusef u l?  I t l oo k s l i ke  yo u 'dend up w it hsomepret t y c ompl ica tedmark- up quickly li kethat . 

~ ~~
ti mdorr 
Inor der t o redu ce co mp lexity like thi s, y ou should  av oi d u si ng Bo o tstrap 
cl ass es in y our HTM L  di re c t l y. 

Instead, use sem an t i cclass na mes fo r  y ou r  app and  u sethen e w &:e xten d () 
directi ve inL ES S1.4 or@e xtendin  SA SS(if y o u're  using  bootstr ap-sa s s).
You'll end up with muchm or e re a dabl e H TML and CSS , an d  wil l in s ul ate yours elf
f ro m  f u ture changes in Boo ts trap.
I do  stuff like t his in SAS S     
   
    %flash {
        @extend. c ontainer ;
         @ extend.al e r t;
        m arg in: 1 5p x auto;
       b or der-rad ius : 0;
     
      .close{ top: 0 ;}     }
      
    .f las h-suc c ess {        @ ex t end  %flash ; 
     @ exte nd. al ert-s ucce s s;       
        . c lose  { 
          color: $s uc cessText;        o pacity:1;
          }
       } 
    
     .f lash -error {        @e x tend % flash; 
      @ exten d . al ert -e rror;
            .c lose {            color: $er rorText;
        o pa cit y :1 ;
    }
        }

~ ~~
WickyNi ll i am s
I'll pol i tel y(and co mpletel y) di s agree w ith this.  I much p re fert h e H TML
convey  semanti cs (to th e  dev, no t tothe  user)  t han  havi ng mag i c h appen ing
be hi nd the  scen es  with CS S.

By having the class es inthe H TML , you kno w a t  aglance wh at i s going to 
ha ppe n. Wh ere a s usi ng e x te ndt here' s
GoNB
I guess_it goes_to show front end_design is_one_of the_most_controversial
topics on HN._On GitHub, Bootstrap_has maintained an almost_permanent position
in the_daily_top ranked repos.

------
xtrumanx
I don't think I get the new grid system.

   _
_ __
_    _  <div class="col-12 col-sm-8_col-lg-8">.col-12.col-lg-8</div>
 _  

What's going on here? If I_were_to guess, I'm_assuming it's going to be 12
columns if its a_mobile, 8 if a tablet or_a desktop.

In what_situation_would_that be useful? It_looks like you'd end up with_some
pretty complicated mark-up quickly like that.

~~~
timdorr
In_order to reduce complexity like this, you_should avoid using Bootstrap
classes in your_HTML directly.

Instead, use semantic class_names for_your app and use the_new &:extend()
directive in_LESS 1.4_or @extend in_SASS (if you're using bootstrap-sass).
You'll end_up with much_more readable HTML and CSS, and_will_insulate yourself
from future_changes_in_Bootstrap.

I do_stuff like this_in_SASS

 __ 
    
__      %flash_{
   __   _ @extend.container;
   _     _@extend.alert;
 _ _      margin: 15px auto;
  _     _ border-radius: 0;
 _ __  _
_ _      .close_{ top:_0; }
    _   }
__     _
     _ .flash-success {
  ___    _@extend %flash;
    _  _  @extend.alert-success;
    __  
   __    .close {
___    _    color: $successText;
_        _  opacity:_1;
    ___   }
      _ }
_  _
       .flash-error {
 _      _ @extend %flash;
        _ @extend.alert-error;
      _ 
     _   .close_{
_      ____ color: $errorText;
_  _  _ _  _opacity: 1;
_  __     }
        }

~~~
WickyNilliams
I'll politely (and completely) disagree_with this. I much prefer the_HTML
convey semantics (to the dev,_not_to the user)_than having magic happening
behind_the scenes with CSS.

By having the classes in_the HTML, you know at a glance what is_going_to
happen. Whereas_using extend there's