CSS Import Resolver resolves the @import url(...); statements in input CSS files (by replacing the @import statement with the actual content of the linked CSS) and creates a huge CSS output (written to STDOUT by default). Including the combined CSS in your Web pages will improve the performance of a site by avoiding additional HTTP roundtrips.
> I don't consider it 'costly' when
> developers have to figure out something
> new, I tend to consider it as an
> investment for the future.
It definitely is an investment for the programmer. The average time a programmer in India stays in a job should be around 2 years (statistics from my contacts and experience). Now consider someone coming into your organization, and doing everything in some new language and then decides to leave for a better offer. if your organization's primary developer skillset is Java, how long will it take an average Java programmer to learn the new language and be productive (of course, we also have this trend in India where the Java developers will not do anything other than Java--they consider it lowly!!)? Or will you recruit a new person with that skillset just to maintain this application?
My opinion on people knowing multiple-programming-languages: it is a must. It makes them take better decisions when facing programming challenges. My argument is not against learning new languages (unfortunately, I believe the article's tone seems to suggest this--which was completely unintended). It is about the advantage of using Java expertise in your scripting environment; and about the ability to use scripting language (when running in JVM) to access Java specific services like content repositories (JSR 170) which traditionally cannot be accessed by non-Java languages; and an implicit argument against making your organizational investment going in to figure "how to do this in this language?"--I am advocating consistency, but not promoting redundancy.
> The use of ScriptEngine as a plugin
> architecture looks like an okay thing to
> do. But mixing Java and various random
> scripting languages together just
> because developers are too lazy or
> because it's too 'costly' to make them
> learn a new language seems like a
> blatant abuse of the technology. In
> fact, to me it's even worse than a shell
> script parsing XML with sed and then
> making calls to Java programs for more
> advanced XML scripting. (xml-starlet
> might have helped here).
I again disagree with your opinion on ScriptEngine. Any good technology can be abused when used irrationally. I am in no way advocating mixing some random scripting language with Java. My point is: ScriptEngine architecture allows one to gracefully support plugins in multiple languages if there be a need.
BTW, xml-starlet seems to be interesting!
Request To Upload This To Maven Repository
This seems to be a great software which will help write editors easy. I will be using this to revive one of my dream projects--now long dead. Details on uploading is available here:
Please do this, it will help people who use this library.