Re: [css-d] Ready for Pre-processors?

[MiB]

apr 26 2014 00:36 Reese :

> 
> CSS pre-processors do not write optimized code by default, it is very
> easy to write code that will result in bloat and reduced performance.
> It didn't take much Googling to find this article:
> 
> 
> 
> If that isn't reason enough to shun them…

Irrelevant to the subject here, which is about the discussion of preprocessors 
on this list.

__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Ready for Pre-processors?

[Reese]

At 06:53 AM 4/25/2014, Tom Livingston wrote:


Possible Holy War as well...



CSS pre-processors do not write optimized code by default, it is very
easy to write code that will result in bloat and reduced performance.
It didn't take much Googling to find this article:



If that isn't reason enough to shun them...

Reese


__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Ready for Pre-processors?

[MiB]

25 apr MiB :

> I didn’t get the original for this. Eric?

Andrews original was found in the spam folder for unknown reasons.
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Ready for Pre-processors?

[Tom Livingston]

> On Apr 25, 2014, at 1:43 AM, Philip Taylor  wrote:
> 
> 
> 
> Eric wrote:
> 
>> I'll raise my hand and say I'm against it. Not because I have a problem with 
>> CSS
>> pre-processors rather because this is a CSS list. Pre-processors are simply a
>> tool used to write CSS in a more programmatic way and then 'compile' it
> 
> I agree, and each is presumably different; a separate list for such
> things (or no list at all) would allow this list to retain its focus.
> 
> 

Possible Holy War as well...
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Re: [css-d] Ready for Pre-processors?

[MiB]

I didn’t get the original for this. Eric?


apr 25 2014 03:21 John Johnson :

> certainly seems appropriate to me…I’d vote “yes” for the powers that be to 
> consider.

I’m for it as long as there is a clear connection to CSS, which there typically 
is. 


__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/