addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

CSS Pre-processor - Good or Bad?

From: Bryan
Sent on: Wednesday, August 11, 2010 11:19 AM
Hello all,

I recently stumbled upon using CSS Pre-processors, although nothing
new, they have certainly sparked my interest. I recently started
looking at Turbine­, and it does a few
"neat" things.  It essentially abstracts many of browser
incompatibilities away (plays friendly with more browsers then you can
shake a stick at). Its currently under development on Github.

My question to you (yes, this includes you), have you worked with this
or similar systems? What are some of the issues you've come across?

For the speed critic in me, the developers have created some caching,
which in theory should improve runtime, etc.  However, I haven't done
any type of analysis for actual speed changes.


Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy