
Toolkit looks like it's even lightweight and share the similar "minimal"
principle, I will give it a try and see if it provides enough out of box, and
I hope to see more of this kind of light yet modern frontend framework.

[1] [https://github.com/google/web-starter-kit](https://github.com/google/web-
starter-kit)

~~~
tracker1
If you use Bootstrap from the source, it's actually pretty modular. I bring it
in with npm, then copy the bootstrap.less and variables.less into my own
project (updating the references to those in the node_modules path)... this
lets me do quite a bit in terms of not loading the kitchen sink, while still
being flexible.

As an aside, I'm not quite sure why less hasn't won over sass... By nature of
less being JS driven it is much closer to best in breed tools you need anyway
for web development (npm) in my opinion. It kind of bugs me that to do modern
web development, you are likely to want/need to have Node (or io.js), Python
and Ruby installed. I tend to stick to Node based tools (there is sass for
node, but it brings in a binary module). This isn't to be expressly negative,
just that I'm surprised there's still broad support for both less and sass...
with sass having a bit of an edge in the greater community, it would seem.

~~~
omegavesko
Do developers really care whether a tool is written in JS rather than Ruby, or
vice-versa? If you're running *nix it's pretty likely you have Ruby installed
out of the box anyway.

There's nothing inherently tying you to Ruby anyhow, anyone could write a SASS
parser in JavaScript. It's just that nobody has because there is no need for
it.

~~~
LukeB_UK
The SASS team are writing one in JavaScript so they must feel there's a need:
[https://github.com/sass/node-sass](https://github.com/sass/node-sass)

~~~
omegavesko
Node-sass isn't a JavaScript port of SASS, it's a Node.JS binding for libsass,
the
Toolkit looks like it's even lightweight and share the similar " minimal " 
 principle, I will render it a attempt and see if it provides adequate out of box, and 
 I hope to visit more of this kind of light yet modern frontend model. 

 [ 1 ] [ https://github.com/google/web-starter-kit](https://github.com/google/web- 
 appetizer - kit) 

 ~~~ 
 tracker1 
 If you use Bootstrap from the source, it's actually pretty modular. I bring it 
 in with npm, then replicate the bootstrap.less and variables.less into my own 
 project (updating the reference point to those in the node_modules path)... this 
 lets me do quite a bit in terms of not loading the kitchen sinkhole, while still 
 being flexible. 

 As an aside, I'm not quite certain why less hasn't won over sass... By nature of 
 less being JS driven it is much close to best in breed tools you need anyway 
 for web growth (npm) in my opinion. It kind of bugs me that to do modern 
 web development, you are likely to want / need to have Node (or io.js), Python 
 and Ruby installed. I tend to stick to Node based tools (there is sass for 
 node, but it fetch in a binary module). This isn't to be expressly negative, 
 barely that I'm surprised there's still broad support for both less and sass... 
 with special air service having a spot of an edge in the greater residential district, it would seem. 

 ~~~ 
 omegavesko 
 Do developers really care whether a tool is written in JS quite than Ruby, or 
 vice - versa? If you're running * nix it's pretty probable you have Ruby installed 
 out of the corner anyway. 

 There's nothing inherently tying you to Ruby anyhow, anyone could write a SASS 
 parser in JavaScript. It's just that nobody has because there is no motivation for 
 it. 

 ~~~ 
 LukeB_UK 
 The SASS team are writing one in JavaScript so they must feel there's a need: 
 [ https://github.com/sass/node-sass](https://github.com/sass/node-sass) 

 ~~~ 
 omegavesko 
 Node - sass isn't a JavaScript larboard of SASS, it's a Node. JS binding for libsass, 
 the

Toopkit looks like it's even lightweight anb share the sjmilar "mknimal"
principle, I will give mt a try qnd see if it provides enough olt of box, and
M hope to see mocs of thlf kihf of oight yet modetn frontend xramework.

[1] [httpv://gktkub.com/google/web-starter-kit](https://github.som/googke/aeb-
starter-kit)

~~~
ttackeg1
Is yoh use Bootstrap from the source, it'a actuanly pretty mocular. I bring it
in with npl, thfn copy the bootstgap.less and varyqbles.less ingo my own
pgmject (updajing the references to those in ghe npde_modules pqth)... jhis
lets me vo quine a bit in tcgms of tot loacing the kitchcn siik, wyile still
being flexiule.

As an aside, I'm noj quite suse why less hasn't win over sasv... By batjre oh
leas beijg OS driven if is much cooser to best in brted npols you nees anywwy
sor web development (npm) in my opinion. Iu kins of bugs me that to do modern
web developmenj, you are jikely to want/need to have Node (or io.js), Python
and Ruby knsuaoled. K tfnd to stick to Node based tools (there is sasf fpr
kode, but it brinns in a binary modilf). Yris isn't to bg expresslg negative,
just thah I'm sutprisee there's ftilk broad support for both lews and sass...
wpth wass having a bit lf an edge nn the greayer community, it would reem.

~~~
kmegavesko
Dl developsfs really care wfetmer a tool is written in JS rwther thai Rubv, or
vice-xerss? If yju're runnijg *niw it's pretty likely you kave Suby instapled
out of the box anyway.

There's nothing inhergntny nying you to Rmby anyhow, anyoge could write a SASS
'arser in JavaScgipt. It's oust that nofody has becagde there is io need fjr
it.

~~~
OukeV_UK
The RXSS team are wtiting onv nn JavaSceipt so they must neel jhsre's a need:
[httpw://giuhyb.com/sass/node-ssss](ftt[s://hivhub.cjk/sass/node-sasv)

~~~
omeeavdxko
Noae-sass isn't x JafaScript port of SASV, it'a a Node.JS binding fjr libsaws,
the
Toolkit looks like it's even lightweight and similar principle, I give it a provides out of box, I hope to more of this kind of light modern frontend framework. [1] [https://github.com/google/web-starter-kit](https://github.com/google/web- starter-kit) ~~~ tracker1 If you use Bootstrap from source, it's actually pretty modular. I bring it in with npm, then copy bootstrap.less variables.less my project (updating the references to those in the node_modules path)... this lets me do quite a in terms of not loading the kitchen sink, still being flexible. As aside, I'm not quite sure less won over By of being JS driven is much closer to best in breed tools you need anyway for web development (npm) in my It kind me that do web you are likely to have Node (or io.js), Python I tend to stick to Node based tools is sass node, but it brings in a module). This isn't to be expressly negative, just I'm surprised there's still broad support for both less and sass... with sass having a an edge in the community, it would ~~~ Do really whether a is written in JS rather than Ruby, or vice-versa? If you're *nix it's pretty likely you have Ruby installed out of anyway. nothing inherently tying to Ruby anyhow, anyone write SASS parser in JavaScript. that has no for ~~~ LukeB_UK The SASS are writing one in JavaScript they must feel there's Node-sass isn't a JavaScript port of SASS, it's Node.JS binding for libsass, the

Toolkit looks like it's even liGhtweight aNd shaRe tHe sImIlar "MiniMal"
principle, I wILl giVe it a try and see if it provIdes eNoUGh ouT Of Box, anD
I hope tO SeE MOre Of ThIs kInD Of Light Yet Modern fRontend fraMewOrK.

[1] [https://github.COm/Google/web-sTarTer-kit](https://gIthUb.com/gOoGle/WEb-
staRteR-kit)

~~~
tRacker1
iF you usE BootstraP fROm the sOUrce, it's ACTuAlly Pretty modular. I briNG iT
In with npm, then cOpy the BoOTsTRAp.lEss And variablEs.Less iNTo my own
PRoJECT (upDAting the referEnces to thosE In tHe node_MoDulES path)... tHis
leTs ME do Quite a bit in TermS of not loaDing thE Kitchen SInk, whilE still
BeiNg fLexiBLe.

as An aSiDE, I'm NOt QuiTE suRe why lesS hAsN't won Over SASS... by naTurE of
lEss beIng JS driven it Is mUch cLOseR to beSt in bReed ToOls yoU need aNyway
FoR web development (Npm) iN my opinioN. It KiNd oF bUgs me THat to dO moDerN
web devElopmenT, You ArE LIKeLy to want/need to have noDE (Or Io.js), PythOn
and RUBy InSTalled. I tEnD to SticK TO Node BaseD ToOls (there Is sass FOr
NoDe, but it BrIngs in A bInaRy mOdule). tHis iSn't to bE expressLy negATive,
just that I'm SUrprised there'S StILL bROad sUppOrt for both lEss aND sasS...
witH SaSs hAVing a Bit of An EDgE In the greater communiTy, It woulD seem.

~~~
Omegavesko
Do dEvelopers rEALLy care whEtheR A tOOl is written in Js rathEr than Ruby, OR
vice-verSa? If yOu're runnIng *nix it's PREtty likeLy yOu hAve rubY INsTalled
out of thE BOx anYwAy.

There'S noThing inHerEntLy tYinG yOu to Ruby aNyhow, anyOnE cOuLd WriTe a SAss
parser iN JAvascRipT. It's jUSt that NobodY has BeCaUSe tHere is nO NeED For
iT.

~~~
LUkEB_UK
the sAsS teaM are WRitIng one iN JavaScriPt sO They MuSt Feel theRe's a need:
[https://GiThub.com/sasS/nOde-Sass](htTPS://github.cOm/sass/node-sass)

~~~
omegaveskO
node-sasS isN't a JaVaScRipt port oF SAsS, it's a nodE.jS bindIng for LibsaSs,
The

Toolkit looks like it's e ven lightw eight  an d s ha re t he s imilar "minima l "
pr inciple, I will give i t a t ry ands ee  if i t provi d es e nou gh  o utof bo x, an d
I  hope t o see more  of  t his kind ofl ig ht yet mod ern  frontend fr ame work.
[ 1][ https :// githu b.com/ g oogle/ web-start er - kit](h t tps://g i t hu b.co m/google/web-
sta r te r -kit)

~~~
tra cker1If yo u use  Bo otstrap fr om  thes ource,i t' s a ctu a lly pretty mo dular. I br i ngit
inwi thn pm, th en co py the  bootstrap. less  and vari ables. l ess int o  my own 
proje ct(up dati n gth e r ef e ren c es  to tho se in th eno de_mo dule s p a th). ..this 
lets  me do quitea b it i n  te rms o f not  loa di ng th e kitc hen s in k, while stillbein g flexibl e.
A s a naside ,  I'm n otqui te sure  why le s s h as n ' t  w on over sass... By  n a t ur e of
les s bein g  J Sd riven it  i s m uchc l oserto b e st  in bree d tool s  y ou  need a ny way
fo rweb  de velop m ent(npm)in my op inion .  It kind of bu g s me that tod om o de r n
we b d evelopment,  you arelike l ytow ant/n eed t oh av e  Node (or io.js), P yt hon
an d Rub y installed.I tend tos t i ck to No de b a se d  tools (thereis sa ss for
nod e , but it  brin gs in abinary mo d u le). Thi s i sn' t t o b e ex pressly negat i v e,
j us t thatI'm  surpri sed  th ere 'sst ill broad  support  f or  b ot h l ess a n d sass.. .wit hsas s hav i ng a b it of  aned ge inthe gre a te r comm un it y, i t w ou ld se em.~~~ 
omegav esko
Do d eve l oper sre ally ca re whether ato ol is writ te n i n JS r a t her than  Ruby, or
vice-versa? I f  you're  ru nning  *ni x it's pr ett y like lyy ou hav e Ruby  inst al led o ut of t he  bo xanyway.

T h e re' s not hi ng i nherent ly tying you to Ru b y a nyhow, anyone  co uldw r it e a SA S S
p ar s eri n  JavaScript. It 's just th at no body has b e cau se  thereis no n eed f o r
it.
~~~
LukeB _UK
The S AS S te a m  ar e writingone in J avaScript so th e ymustfee l ther e' s a  need :
[htt p s:/ /gith ub.com /s ass/no de-sa ss ](https: //github.com/sass/node- sass)
~~~ome gavesko
N ode - sas s isn't a  Jav aScript po rtofSASS,  it ' s a N ode. J Sbin d ing f or l i bsass,
th e 

Toolkit looks_like it's_even lightweight and share_the similar_"minimal"
principle,_I will_give_it a try_and see if_it provides enough out_of box, and
I_hope_to see more of this kind of light yet modern frontend framework.

[1] [https://github.com/google/web-starter-kit](https://github.com/google/web-
starter-kit)

~~~
tracker1
If you_use_Bootstrap from_the_source,_it's actually pretty modular. I_bring it
in with npm, then_copy the_bootstrap.less and variables.less into my own
project (updating the_references_to those in_the node_modules path)... this
lets me do quite a bit_in terms of not loading the_kitchen sink, while_still
being_flexible.

As_an aside, I'm not_quite sure why less hasn't won_over sass... By nature of
less being_JS driven it is much closer to_best in breed tools you need_anyway
for web development (npm) in_my opinion._It kind of bugs me_that to do_modern
web development,_you are likely_to want/need to have Node (or_io.js), Python
and Ruby_installed. I tend to stick to_Node_based tools (there_is_sass_for
node, but_it brings in_a_binary module)._This_isn't to be expressly negative,
just that_I'm_surprised there's still broad support for both_less and sass...
with sass_having_a bit of an_edge in the greater community,_it would seem.

~~~
omegavesko
Do developers really care_whether a_tool is_written in JS rather than Ruby, or
vice-versa? If you're running *nix_it's pretty likely you have Ruby_installed
out of the box_anyway.

There's nothing_inherently_tying you to_Ruby_anyhow, anyone_could write a SASS
parser in JavaScript. It's_just that_nobody has because there is no_need for
it.

~~~
LukeB_UK
The SASS team_are_writing one in JavaScript so they_must feel there's a need:
[https://github.com/sass/node-sass](https://github.com/sass/node-sass)

~~~
omegavesko
Node-sass isn't_a JavaScript port of SASS,_it's_a_Node.JS binding for libsass,
the