🚀 go-pugleaf

I got the impression (correct me if I'm wrong) that many of java's cross JVM
problems (write once- debug everywhere) were due to differences in services
implementations. Counting AWT as a service then the fact that it requires
hooking into the underlying OS's presentation capabilities it would seem
that AWT would be much more prone to implementation deficiencies. and
therefre cross-platform vulnerabilities, than swing.
Is this the case? Are my swing projects going to have fewer problems on
other platforms?

I've also heard that swing does actually use something of the AWT underneath
itself. If that's the case then it would seem to undermine any possible
portability advantage that swing might have. Have I picked up a butt end?

Thanks

    Greg