pos VS Metals

Make the changes to the code you just cloned in your computer. If you already have changes, you can copy-paste them into this local project whose code is being tracked by git. Then, using the GitHub terminal for Windows or the Linux/Mac terminal with the git command line command installed, from the directory of the repository you cloned (so for this example it would be ~/Home/code/pos because the name of my project is "pos") run git status to see the list of files you modified in this project. Then run git add . (with a period in the command) to add all the modified files or git add file.py to add say a file named file.py that you modified. Then run the command git commit -m "I modified the file file.py" or whatever you want to be the message documenting what change you made to your project (the -m flag specifies the commit message). A git commit is like a save point in a videogame, if you mess up you can always go back to it, reverting all your code to that point. Finally, do git push origin master to push your changes from your local git repository to the one in GitHub (in this command master refers to the name of the branch in the git repository, the master branch, and origin refers to the origin of where you got the code from, in this example it is https://github.com/JohnReedLOL/pos . A branch in git is like a version of your code and the master branch is the main version. If someone is working on version 2.0 they might make a branch named "2.0" that is a clone of the master branch, add their commits to it, and when they're done merge those commits back into the master branch.

A portfolio of personal projects ceases to matter when you have years of relevant experience but it can help you get your first few jobs. The code for personal projects is usually hosted on GitHub with a README.md file in your project's repository for documentation. Here's a project I published because I found it useful for print debugging Scala code: https://github.com/JohnReedLOL/pos . Usually if prospective employers look at your personal project they will just briefly look at the README documentation without actually running it (I don't think any employer actually takes the time to run the code in your personal projects). I also have a website I built for my mom's condo at https://sea-air-towers.herokuapp.com/ with the source code at https://github.com/JohnReedLOL/TypeScript-Node-Starter , both of which I previously put on my resume. I like having links to websites I built on my resume because a potential employer can click the link and briefly take a look, which is much more convenient for them than having to execute the code you wrote on their machine, which they don't have the time or interest in doing. For hosting I used Heroku because it's more convenient than AWS and they used to be 100% free for personal projects, but recently Salesforce bought Heroku and ended that policy so the app hosting has been costing $7 per month. You might incur less cost if you take out AWS free tier or free credits although those run out after some number of months.

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.