pos VS bloop

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.

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