bloop VS advisoryboard

Here's the links: * bloop: https://scalacenter.github.io/bloop/ * terminal to IDE (iTerm only): https://alexn.org/blog/2021/07/18/iterm-open-file-cmd-click-ide-semantic-history.html * Switching between JetBrains' and standard typechecker in IDEA: Options -> Languages and Frameworks -> Scala -> Editor tab -> Error highlighting

If you look at the Build Tools section of the Metals documentation, you'll see how Metals supports sbt. It is admittedly a bit of a roundabout process: Metals first imports the sbt build definition into a tool called bloop that implements the Build Server Protocol that Metals relies on for metadata, compilation, etc. for the project.

Jorge Vican had finished some work on this in the past, but this feature was abandoned (for now). As u/tgodzik has pointed out, there is not enough interest for this in the community (thanks for replying btw.).

Bloop -- https://github.com/scalacenter/bloop

From what I can tell looking back, it seems the Scala Center made a conscious decision to back BSP in sbt here. This makes absolutely no sense to me seeing that the people in that conversation seemed to advise against it. Since then Bloop seems outdated in terms of Scala version, dependencies, etc. There is a bit of activity but no active development. With other tools relying on it and it providing an easy way for new tools to come about, it seems totally irrational that the Center wouldn't continue development of Bloop and instead back sbt when Bloop is their own project.

This blog post on the accessibility of Scala is interesting, along with the associated proposal. Dunno if it went anywhere though. It might also be useful to consider the accessibility of compiler diagnostics too.