FWIW...

1. 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.  There *are* a
lot of toolchains for building static websites with node that aim for world
domination, but as long as it's calling a simple tool on the command-line
that does exactly one thing - take sass and generate css - that shouldn't
be that disruptive.  And nvm is handy for managing multiple installed
versions of Node.  So there's no reason you couldn't have repeatable builds
and an easily replicated environment that plays nicely with any CI system.
It's not the wild west it once was.

2.  Locking down the version of node and/or node project dependencies is
pretty easy - it's what package-lock.json is for in any node project
managed by npm (and even uses hashes, not version numbers to make sure
you're building with *exactly *the same bits).

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.  But that doesn't mean tossing
everything and starting over (no matter what all the cool kids do these
days), just integrating bits as needed into the build when there's an
advantage to.

-Tim

On Tue, Jul 16, 2019 at 4:44 AM Neil C Smith <[email protected]> wrote:

> On Tue, 16 Jul 2019 at 09:01, Christian Lenz <[email protected]>
> wrote:
> > Open your eyes, there is more than only Java .
>
> Maybe open your eyes and realise you're not the only person with a
> decade plus of frontend work involved in this discussion, and that
> this has nothing to do with whether it's Java or not, and everything
> to do with actually understanding why we have what we have and what
> the *full* requirements are.
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

-- 
http://timboudreau.com

Reply via email to