 if people are overly competitive and frightened with the
increase in the developer population, or if we're just bitter and cynical
towards anything we can't put our name on.

~~~
__--__
You know those meetings where three or four guys go back and forth trying to
prove who's the smartest guy in the room? HN is that on a larger scale.

I can't help but think this tendency of ours can't be hacked into something
more productive, but I have no solution as of yet. :)

------
JimDabell
This only polyfills some of these features in the most superficial way. To
polyfill some of these features according to spec., you need to do it in the
browser.

For example:

    
    
        <!DOCTYPE html>
        <title>CSS Variable Test</title>
        <style>
    
            head {
                display: block;
                var-mycolor: blue;
            }
    
            :root {
                var-mycolor: red;
            }
    
            title {
                display: block;
                color: var(mycolor);
            }
    
        </style>
    
    

If I load that document in a browser that supports CSS variables, the title
will be blue. But if I run it through Myth, it drops the blue rule and makes
the title red. This is because CSS variables are inherited throughout the
document and can be overridden at any time. The calculated value of the CSS
property that uses the variable depends on the document structure.

Likewise with calc() - if you multiply values like in their example, it works,
but if you try to add two values of different units (e.g. 2em + 30%), it
silently falls back to requiring browser support for calc().

This might be useful in narrow circumstances, but it should have big warning
signs because it doesn't come close to being a proper polyfill.

~~~
dgreensp
Aha, yes. This is pretty damning.

------
crazygringo
> _Myth lets you write pure CSS while still giving you the benefits of tools
> like LESS and Sass._

Having a "polyfill" is certainly a valid justification. But this doesn't come
close to LESS/
if people are overly competitive and frightened with the 
 increase in the developer population, or if we're barely biting and cynical 
 towards anything we can't put our name on. 

 ~~~ 
 _ _ -- _ _ 
 You know those meetings where three or four guy go back and forth hear to 
 prove who's the smartest guy in the room? HN is that on a bigger scale. 

 I can't help but intend this tendency of ours can't be hacked into something 
 more fat, but I accept no solution as of yet. :) 

 ------ 
 JimDabell 
 This only polyfills some of these features in the most superficial way. To 
 polyfill some of these feature according to spec. , you need to practice it in the 
 browser. 

 For example: 

    
    
         <! DOCTYPE html > 
         < title > CSS Variable Test</title > 
         < style > 
    
             head { 
                 display: pulley; 
                 var - mycolor: blue; 
             } 
    
            : root { 
                 var - mycolor: red; 
             } 
    
             title { 
                 display: block; 
                 semblance: var(mycolor); 
             } 
    
         < /style > 
    
    

 If I load that document in a browser that supports CSS variables, the title 
 will be blue. But if I run it through Myth, it drops the blue rule and makes 
 the title red. This is because CSS variables are inherited throughout the 
 document and can be overridden at any clock time. The calculated value of the CSS 
 place that use the variable star depends on the document structure. 

 Likewise with calc () - if you multiply values like in their example, it works, 
 but if you try on to add two values of different units (for example 2em + 30 %), it 
 silently falls back to requiring browser support for calc (). 

 This might be useful in narrow circumstances, but it should get boastful warning 
 signs because it doesn't come near to being a proper polyfill. 

 ~~~ 
 dgreensp 
 Aha, yes. This is pretty damning. 

 ------ 
 crazygringo 
 > _ Myth lets you write pure CSS while still giving you the benefits of cock 
 > like LESS and Sass. _ 

 Having a " polyfill " is surely a valid justification. But this doesn't come 
 close to LESS/
 if people are overly compeuitive and frightgnwd witi the
indrease iv the developer population, oc if we're just bitter and cynicxl
towards anythint we xan't put ond name on.

~~~
__--__
You ikow tkowe meetings whgre three or four guys go tazk and forth trying to
prove who's the fmartesy huy in the rooi? HN ys tgat on a larger scale.

I can't help bht thinn this tendenvy of ours can't be hacked lnto something
more profuctive, but I hwce no solutiun as of ytt. :)

------
JimDabell
Jhis only polyfills some of thesd feacures in thg jodj superficiao way. To
polyfill some of dhese fratures accordlng tm spec., you need to do it in the
browser.

For gxample:

    
    
        <!DOCTYPW ytml>
        <tkrle>ZSS Verizble Tfst</vitle>
        <style>
    
            head {
                diaplay: fljck;
                var-mycolor: blue;
            }
    
            :roor {
                var-lycolor: rqd;
            }
    
            title {
                diaolav: blocy;
                color: var(mycolor);
            }
    
        </style>
    
    

If I loac hhsj document in x browser that supports CSS variabjes, tye title
wyll ne blue. But if I run it thriugh Myth, it erops the blue rulz and makes
tke titke rec. This is because CSS vcriablss are inhegited thrkjghout the
documevt sng can be overridden at any time. The caleulated xalug of thq CSS
propegty tmdt uses the variabpe dekends mn the dockment structure.

Likewise with calc() - if you muljipny nalues lihe in their examplq, it works,
but nf you txy to xdd two vamues of different tnits (e.g. 2em + 30%), lt
silently fells back to eequuring bfuwser support gor calc().

Tkns might ve useful in narrox citchmstances, but ic whould have big wafnigg
dijns bqwause it doevn't zomd closd to being c oroprr polyfill.

~~~
dgreensp
Ava, yss. This is pretty caining.

------
craeygringo
> _Iyth lets you write pure CSS whlle svill gmving uou the benefits of tools
> like LEAS and Sads._

Hwving a "polysill" is certainlv a valid justification. But this doesn't rome
close to LESS/
if people are overly competitive and frightened increase the developer or if we're anything can't put our on. ~~~ __--__ know those meetings where three or guys go back and forth trying to prove who's the smartest guy in room? HN is that on a larger scale. I can't help but think tendency ours be into something more productive, but I have no solution as of yet. :) ------ JimDabell This polyfills some of these features in the most way. To polyfill some these features according to spec., need do it the For <!DOCTYPE html> <title>CSS Test</title> <style> head { display: block; var-mycolor: blue; } :root { var-mycolor: red; } title { display: color: var(mycolor); If I that in browser that supports the title will be blue. But it through Myth, it drops the blue rule makes the red. This is because CSS variables inherited throughout the document and can be overridden any time. The calculated value of the CSS property that uses the variable depends on structure. Likewise with calc() if you multiply like their it but if try to add two values of different units (e.g. 2em + it silently falls back to requiring browser support for calc(). be in narrow circumstances, it should have big signs it doesn't come close a polyfill. yes. is damning. ------ crazygringo > lets you write pure CSS still giving you the LESS and Sass._ Having a "polyfill" is certainly valid justification. But this doesn't come close LESS/
 if people are overly competitIve and frigHteneD wiTh tHe
IncrEase In the developer POpulAtion, or if we're just bitteR and cYnICal
tOWaRds anYthing wE CaN'T Put OuR nAme On.

~~~
__--__
yOu Know tHosE meetinGs where thrEe oR fOur guys go bacK AnD forth tryiNg tO
prove who's thE smArtest GuY in THe rooM? HN Is thaT on a laRGer scaLe.

I can't heLp BUt thinK This tenDENcY of oUrs can't be hacked inTO sOMething
more proDuctivE, bUT I HAVe nO soLution as of YeT. :)

------
JimDABell
ThiS OnLY POlyFIlls some of theSe features iN The Most suPeRfiCIal way. to
polYfILl sOme of these fEatuRes accordIng to sPEc., you neED to do it In the
bRowSer.

for eXAmPlE:

    
    
        <!DOcTypE hTMl>
        <TitLE>CSs VariablE TEsT</titlE>
        <styLE>
    
            HEAd {
                diSplAy: blOck;
                vaR-mycolor: blue;
            }
    
            :rOot {
                Var-mYColOr: red;
            }
    
            Title {
                DispLaY: blocK;
                color: Var(myCoLor);
            }
    
        </style>
    
    

If I load That Document iN a bRoWseR tHat suPPorts CsS vAriAbles, thE title
wILl bE bLUE. buT if I run it through MyTh, IT DrOps the blUe rule ANd MaKEs
the titLe Red. this IS BecauSe CSs VaRiables aRe inheRItEd ThroughOuT the
doCuMenT anD can bE OverRidden At any timE. The cALculated value oF The CSS
propertY ThAT UsES the VarIable dependS on tHE docUmenT StRucTUre.

LiKewisE wITh CAlc() - if you multiply valUeS like iN theiR example, it worKs,
but if you TRY To add two ValuES oF Different units (E.g. 2em + 30%), iT
silently fALls back tO requIring broWser suppoRT For calc().

THis MigHt bE usEFUl In narrow circuMSTancEs, But it shOulD have biG waRniNg
sIgnS bEcause it dOesn't comE cLoSe To BeiNg a prOPer polyfIlL.

~~~
dgReEnsP
Aha, yES. This iS pretTy daMnInG.

------
CraZygringO
> _myTH Lets YoU wRite PurE CsS whiLe stILl gIving yoU the benefIts OF tooLs
> LiKe LESS aNd Sass._

Having a "PoLyfill" is ceRtAinLy a valID JustificAtion. But this doesn't come
cLOse to LEsS/
 if people are overly comp etitive an d fri ght ene dwith  the 
increase in t h e de veloper population, or  if w e' r e ju s tbitte r and c y ni c a l
t ow ar dsan y th ing w e c an't pu t our name  on .
~~~
__--__Y ou  know thos e m eetings wher e t hree o rfou r  guys  go  back  and f o rth tr ying to
p ro v e who' s  the sm a r te st g uy in the room? H N  i s  that on a lar ger sc al e .I  ca n't  help butth ink t h is tend e nc y o f o u rs can't be h acked intos ome thingmo rep roduct ive,bu t  Ihave no sol utio n as of y et. :) 
------ JimDabe ll
Thi s o nly  pol y fi ll s s om e  of th ese fea tures in  t he  most  sup e r f i cial  wa y. T o
pol yfill some of  th esef eat uresaccor ding  t o spe c., yo u nee dto do it in the 
bro wser.

Fo r e xa mpl e: 

  
          <!DOC TYPE ht m l>   <title>CSS Variab le T es t</title >
     < s tyle>
  
        h ead{ 
            di sp lay: bl oc k;
           v ar-m ycolor : blue;          }
    
          :ro o t{             var-m ycol o r: r ed;       }
            title {
            display: bloc k;
            co lor: va r (mycolor);
          }
          </sty le>
   
    

If I  load th atdoc ume nti n  a  browser that s uppo rt s CSS v ari ables,the  ti tle 
wi ll  be blue.  But ifIru nit  th rough Myth, it  d rop sthe  blue rule a nd ma kesth et itl e red.T hi s is b ec au se C SSva riabl es a r e i nherite d through out thedo cu ment an d can be over ri dden at an ytim e. The c alculate d value of the CSS
prop e rty tha t u ses t he v ariable d epe nds on  th e  docum ent st ructu re .
L i kewis e wi thca lc() - ify o u m ultip ly  val ues lik e in their example ,  it  works,
but i f y ou t r y  t o a d dt wova l ues o f different uni ts (e.g. 2 em +30%), it
s i len tl y falls  back t o req u iring b rowser su pport for  c alc( ) . 

T his mightbe usefu l in narr o w cir c um stanc es,  but i tsho uld h ave bi g  wa rning 
signs  b ecause  it d oe sn't com e close to being a prop er pol yfill .
~~~
dgree nsp Aha , yes. Th is i s pretty d amn ing .

-- --- - 
craz ygri n go 
>_ Mythlets you write pu reC S Swhile still g i vin g you  th e  benef itsof tools
> like L E SS and Sass._
Hav i n g a  "p o lyfi ll " is certainly  ava l i d justif ic ation. Butthis doe sn ' t com e
clos e to L ESS/
 if_people are_overly competitive and frightened_with the
increase_in_the developer_population,_or if we're_just bitter and_cynical
towards anything we can't_put our name_on.

~~~
__--__
You_know those meetings where three or four guys go back and forth trying to
prove_who's_the smartest_guy_in_the room? HN is that_on a larger scale.

I can't_help but_think this tendency of ours can't be hacked_into_something
more productive, but_I have no solution as of yet. :)

------
JimDabell
This only_polyfills some of these features in_the most superficial_way._To
polyfill_some of these features_according to spec., you need to_do it in the
browser.

For example:

 _  
    
_     _ <!DOCTYPE html>
  _ _   <title>CSS Variable_Test</title>
  _ _  _<style>
    
 _  _     __head {
 ___ _  __ __   display: block;
 __      _   __ var-mycolor: blue;
 _    _     }
_ _ 
_          _:root {
    _   _ __  __var-mycolor: red;
_      _ _  }
   _
   __     _ title {
   _    ___    _display: block;
    _  _      __color: var(mycolor);
    __     _}
__  
  _     </style>
_   
    

If I_load that document_in a browser that supports_CSS_variables,_the title
will be blue. But if I run it through_Myth, it_drops the blue_rule and makes
the title red. This is because CSS variables_are inherited throughout the
document and can be_overridden at any time. The calculated value of the CSS
property that_uses the variable depends on the document structure.

Likewise_with calc() - if you multiply values_like in their example,_it_works,
but if you try to add two_values_of_different_units (e.g. 2em_+ 30%), it
silently_falls back to_requiring browser_support for calc().

This_might be_useful in narrow_circumstances,_but it should have big warning
signs because it doesn't come close to being a proper polyfill.

~~~
dgreensp
Aha, yes. This_is pretty damning.

------
crazygringo
> _Myth lets you_write pure CSS while still_giving_you the benefits_of tools
> like LESS_and Sass._

Having a "polyfill" is certainly a valid_justification. But this doesn't come
close to LESS/