We need to try harder to find opportunities to go outside of our Java bubble and show young devs what modern Java is like. The few times where I did this and showed them some basic Quarkus demos (especially with Dev Mode) they were speechless

files-to-prompt datasette -e py -c | \
llm -m o3-mini -s \
'write extensive documentation for how the permissions system works, as markdown'

Gave me this: gist.github.com/simonw/4a13c...

Ok cheers, i'll look into that

People have different workflows, i almost exclusively do clean builds. Development is with IDE. Then clean builds before pushing big changes, and CI does clean builds

the compilation is just the target, this is the fastest it can be, lets compare to that

they seem to do a clean build for all, so there are no stale classes to check, just first time project build with external caches filled (dependencies downloaded), there might be faster ways to run gradle in incremental mode

i don't think you read the article, its literally all about the overhead the build tools add

Now that @Deprecated has tiers with forRemoval, might be possible to deprecate them, think i saw some discussion in that direction on the mailing list this year

Check github.com/policeman-to... not sure if its included in the signatures by default, but they are easy to add