Metals VS scala-trace-debug

Links: - https://dotty.epfl.ch/ - https://scala-native.org/en/stable/ - https://www.scala-js.org/ - https://typelevel.org/ - https://zio.dev/ - https://github.com/scala-native/scala-native/pull/3120 - https://github.com/lampepfl/dotty/pull/16517 - https://dotty.epfl.ch/docs/reference/experimental/index.html - https://scala-cli.virtuslab.org/ - https://scalameta.org/metals/ - https://docs.scala-lang.org/scala3/guides/migration/compatibility-intro.html - https://www.scala-lang.org/blog/2023/04/18/faster-scalajs-development-with-frontend-tooling.html - https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

You might want to look at Scala, they have proper LSP support with metals which means you can write your code in vscode, neovim, emacs, or even fleet (the new jetbrains text editor).

Please write in the comments if you know of any language servers I should test it with. Currently I tested only metals and rust-analyzer.

If you are using nvim-lspconfig you can pass the settings as a Lua table to the setup function. For example, here are may metals settings:

Bazel support in Metals. I didn't spend all that time figuring out and adjusting Emacs/Spacemacs and making my workflow (almost) mouse-free just to scrap my config and switch to IDEA's rodent infested ways.

There is one small issue involving code completion returning inappropriate completions in some cases; https://github.com/scalameta/metals/pull/4414 will fix it, once it's included in a release. Perhaps that's the PR you saw?

It is, by quite a bit.

While the "Scala IDE" project is dead for all practical purposes, IntelliJ IDEA's Scala plugin is actually pretty amazing. There's also a VisualStudio plugin that does pretty much the same and is advancing by leaps and bounds. There are also interconnecting projects that provide i.e. language server or build server that are reused by other projects. It's pretty modular. Metals (https://scalameta.org/metals/) is amazing.

In general the language has become a wee bit faster to build, there was good progress with build times during the 2.12/2.13 cycles.

With Scala3 the language got a bit simpler; concepts that were implemented explicitly using (hehe) implicits got their own keywords and a lot of the opinionated boilercode that cause a lot of debates is now generated during complication and hidden. A lot of "standardization" has occurred.

IntelliJ has its own BSP. The other one is Metals. You can use it with many IDEs (vim, emacs, vscode, atom,...). Use it with emacs if you're comfortable with it.

If you're not sure what you want to do maybe build your own sample site from a "starter" like https://github.com/microsoft/TypeScript-Node-Starter (this one uses TypeScript which is JavaScript with types added) or https://github.com/sahat/hackathon-starter (this one uses plain old JavaScript without types). I personally deploy to https://www.heroku.com/ because it's less complicated than deploying to AWS or Google Cloud but more businesses deploy to AWS than Heroku so learning AWS and having the AWS services you use to build and deploy your app as skills on your resume would probably make your resume look better to companies than just saying you know Heroku. If you want to copy off me (don't make and use an exact copy) my sample app deployed to Heroku has its code at https://github.com/JohnReedLOL/TypeScript-Node-Starter and the site is at https://sea-air-towers.herokuapp.com/ (I pay Heroku $7 a month for hosting). It's good to have a link to a sample app and link to the code for your sample app on your resume, just make the README.md file on GitHub look good so people can look at it and know what your app does. I have a software library with a much better looking README.md file at https://github.com/JohnReedLOL/pos