Max Rydahl Andersen

What would be the advantage ? Each file isn't a module on its own.

Not sure if jbang should do this as it requires root access and root wouldn't have jbang installed to run using curl.

I used ALL-SYSTEM in early days to make it as easy as possible to use any java code - if we do "all-default" you won't get access to the incubating...

the code is here: https://github.com/openjdk/jdk/blob/c88e081a6a0a00d7e7e5f2337f942a1d6c3b5110/src/java.base/share/classes/jdk/internal/module/ModuleBootstrap.java#L1019 and it just prints directly to System.err.println() ...and it happens before any code is granted access to setup/rewire stderr so can't even do some trickeries.

fyi https://github.com/jbangdev/jbang/issues/992 explains why we added that flag, basically without it you have to get really verbose if you use modules.

I reckon we could add that --enable-preview adds system instead of default? As inthink you need preview anyway to actually use it ( at least in java)

> The issue is that the extension includes Otel Tracing which is supported... It is the logging and metrics part that is tech preview... We chose to have them off...

as others said this doesn't feel right to have on frontpage. we have quarkus.io/developer-joy that talks about devui - maybe there ? or on a dedicated quarkus.io/developer-joy/devui page?

Also, would be good to have the "core" features separate from "you need to add extension"-features or at least call it out somewhere. Also just as another sugggestion - make...

Standalone jars are not dependencies but class path entries. '--classpath %{url}' should work. Not at laptop atm so can't verify if we ever got around to implement //CLASPATH in source...