Julien Tournay

Unless I am missing something, none of the cons of this article affect Scio since https://github.com/spotify/scio/pull/1404 was merged.

IIRC we removed those hooks in Scio `0.8.x` since all the `Future` were removed. Now you can just do: ```scala // ... sc.waitUntilDone() executePostProcessing() ``` Are you suggesting we reintroduce...

Should be possible to make that a compile time issue. Worth a try I guess even though it's a pretty minor issue imo.

Every coder depends on Beam directly or indirectly. The Scio `Coder` instances don't have any serialization logic in them and all of them defer to Beam eventually. The only thing...

Hi @skybox2 Thanks for reporting the issue. I'm not sure wether it's a problem in Scio or Beam, would you mind posting the full stack trace ? Thanks

Java annotations also hurts when you need the derived typeclass to be serializable. (Annotation are not serializable)

Thanks for your replies. Metals does support both languages out of the box but as far as I can tell, it does not support a single project having sources in...

Indeed I'm using `crossScalaVersions`. I would guess most cross-built projects out there do the same so it'd be great if it could "just work".

I did not know that. Although while it's correct it does not make it any less of an issue. You are less likely to run into the issue between Scala...

@martinbomio I'll need to test it on our dev cluster.