4 ms·
While we kind of like Less' approach to CSS, we were not thrilled with the performance and also found it not really enough for serious development. We opensour
by fforw 14y ago
While we kind of like Less' approach to CSS, we were not thrilled with the performance and also found it not really enough for serious development.
We opensourced our attempt at CSS generation in a java environment.
The website is a little outdated http://dynamic-style-sheets.org/dss-website/index.jsp http://dynamic-style-sheets.org/dss-website/index.jsp but might give a rough overview. The SVN is more up-to-date ( http://opensaga.org/svn/opensaga-dynamic-stylesheets/trunk/ http://opensaga.org/svn/opensaga-dynamic-stylesheets/trunk/ )
In addition to rule nesting and mixings, variables, expressions, etc, DSS allows user-defined functions to be written. Some come with it, including a system do imagemagick or so like processing of images in the CSS.
It's a funny little thing that kind of just wanted to be written that way.
- jameskilton 14y agoHave you checked out SASS and the new libsass library? If you want speed, you can't beat a 0-dependency c / c++ library. https://github.com/hcatlin/libsass https://github.com/hcatlin/libsass
- fforw 14y agoAs I said: in a Java environment, which rules out C/C++. 20 times the speed of JRuby based Less is not shabby though. edit: Performance was never the top motivation though. Architectural concerns and resilience were. Although based on a decent JavaCC grammar generated parser DSS should be able to eat any CSS and spit it out again as-is. While I certainly wouldn't want to write such dismal CSS, I also don't want to work on some richtext editor CSS just because I want to integrate that with our system.
- deleted 14y ago[deleted]
- lucian1900 14y agoYou could try the node.js version of less, I've found it to be much faster.