@marius @posco @squarecog agree. Scala ABI compat seems like a total crapshoot, API is at least achievable
-
-
Replying to @slyphon
@slyphon@marius@squarecog but it's not a crapshoot. Look at the compiled code. Tools like mima and semver do this. Am I missing something?1 reply 0 retweets 0 likes -
Replying to @posco
@posco@slyphon@squarecog not a crapshoot, exactly, but It can be onerous.2 replies 0 retweets 0 likes -
Replying to @marius
@posco@slyphon@squarecog you can introduce lots of API compatible changes that aren’t ABI compat.2 replies 0 retweets 0 likes -
Replying to @marius
@marius@slyphon@squarecog yes, and this defeats the win of sharing jars. Not worth it.1 reply 1 retweet 1 like -
Replying to @posco
@posco@slyphon@squarecog so does constantly changing major versions... thus, either you need ABI stability, or else source compilation1 reply 0 retweets 0 likes -
Replying to @marius
@marius@slyphon@squarecog yes. ABI compat is a cost, but one that buys scalable collaboration inside and outside of a single enterprise.3 replies 0 retweets 1 like -
Replying to @posco
@posco@slyphon@squarecog (this is why I think we’d be better off, inside and out, to share source, not binaries.)7 replies 0 retweets 2 likes -
Replying to @marius
@marius@posco@slyphon@squarecog then we need build systems that are better at source dependencies, not binary.3 replies 0 retweets 2 likes -
Replying to @avibryant
@avibryant@marius@posco@slyphon@squarecog in theory you could do that from maven central as each artifact publishes its deps and source.1 reply 0 retweets 0 likes
-
-
Replying to @avibryant
@avibryant@marius@posco@slyphon@squarecog for projects on github and maven central the Pom contains the git URL. releases are tagged0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.