On Thu, 18 Jul 2019, 02:19 Tim Boudreau, <[email protected]> wrote:
> Calling out to node from gradle/java/whatever as an external process to > generate some CSS from sass is pretty trivial and I don't see why it would > be an ordeal to integrate into the existing website build. It's also trivial to call libsass directly via Gradle as the build already does. Adding node adds complexity without improving anything (right now) > Java-based tooling for generating web-sites is not likely to pull ahead of > what's available for node ... ever, as long as Javascript is the primary > language web developers use. So sooner or later, taking advantage of > what's out there is going to be necessary. > I don't think anyone is disagreeing with that point. But a replacement also has to not fail at the first requirement. I expressed concerns over using a Java-based SSG at the time, although there were good reasons for that choice. Yes, the Java options are likely to be behind the Javascript options, for now at least. Neither does Javascript dominate the SSG world in the same way. Best wishes, Neil >
