is this module better worse than the other alternative (unlimited css loader)?

I would also like an answer to that question.

If you care about the performance issues related to using @import (which is what unlimited_css uses), this is the better module.

IE Unlimited CSS Loader is wildly buggy. Don't use it.

I've updated this module's project page with a comparison. http://drupal.org/project/ie_css_optimizer

There has been a new release on ie_css_optimizer recently, that can be expected to fix a lot of the bugs.
You can check out the other comparison thread here, #698488: How is this module different from ie_css_optimizer ?.

The two modules do a few things differently, and I'm not sure which one has the better strategy. More on this in the other issue. IE CSS Optimizer definitely has more options, but not everyone needs them.

Hi,
the statements are no longer accurate, I would say.

I have kind of "taken over" that other module, mostly because at this time I did have a bit of a misconception about IE CSS Optimizer, making me believe that only the other module can solve my problems. Since then the code has been very much rewritten, and I have not seen any serious bug reports for a very long time, despite an increase in popularity. The old bug reports are still around, since people are too lazy to report back. But I strongly believe they no longer apply.

Maybe there are still some edge cases where it would break, but it doesn't seem serious enough for people to report it.

The "unlimited css" module is still quite minimal, and it's meant to stay this way. It does what is promised, not more.
It lacks the feature of disabling theme- or module-specific CSS, and I'm not going to add it.

The technical approach of Unlimited CSS is a bit different than that of CSS Optimizer. Both use @import when necessary (please don't say you don't!), and avoid it when possible. But, while CSS Optimizer will produce a mix of link and import, Unlimited CSS will either do everything with @import, or nothing. It would be interesting to find out what is the better strategy. The linked article says it's actually bad to mix both, but I think some more research would be appropriate if we really want to know.

Actually there are still some css files that will still be served with link, namely all those that are already processed, at the time that the module kicks in. But so far there has not been much activity in the issue queue that would indicate this being a problem.

The module page of Unlimited CSS contains a matrix with the differences that I identified.
Maybe that matrix is a bit of overkill, so if you find a shorter way to explain the difference, go ahead.

-----

PS:
The theme and module specific css aggregation is actually quite sexy, and I started to switch to CSS Optimizer for my own projects. It did not always work for some reason, but I think I should rather discuss that in another issue. Atm my information is not solid enough for a bug report.