I'm a bit confused, because I don't see the commonality between Go and Project Loom other than lightweight threading. Go's whole concurrency model is still fun

I'm a bit confused, because I don't see the commonality between Go and Project Loom other than lightweight threading. Go's whole concurrency model is still fundamentally different from Java as it went all in on CSP, and Project Loom isn't. Beyond that, nothing about Project Loom fundamentally changes the design of all but the most performance sensitive concurrent programs in Java. For most of us plain programmers that Go was targeted at anyways, a bucket of OS threads is just fine. Now they will be a bucket of virtual threads, which will be nicer, but not exactly game changing.