Mono VS Pylint

In the video you basically install .NET 7.0 SDK with the deb packages from Microsoft repos AND mono deb packages from repos laid out in https://www.mono-project.com/ apart from Unity and VS Code. And then you configure VS Code so that it always uses Mono installed in the system (not Unity Editor's own instance???)

4- Any user-side telemetry would be in the MS .Net framework, which is not used when you selfhost as .net based stuff like Jellyfin use Mono, which is fully open-source and independent (https://www.mono-project.com/)

Did they intentionally name it after a widely used, well known programming framework[1], or did they want to guarantee, I dunno, that they will fly way, way under the radar? I thought it was bad form to name a new programming language 'Cedar', but at least the other Cedar isn't actively developed, unlike the other Mono.

[1] https://www.mono-project.com/ for the few of you who didn't know.

.NET 4.8.1 and earlier do not install on Linux. Unless you want to play around with Mono (your mileage may vary): https://www.mono-project.com/

They have deceived you. https://www.mono-project.com/ I seriously don't know how well wine can deal with newer .NET winforms

It also gained a lot of more popularity and success after the release of the open source implementation of it called Mono.

Hey, I'm working on a C++ game engine in VS Code and wanted to add C# scripting, so I'm trying to install Mono. I already got SDL2 working with CMake, but I'm having trouble setting up Mono because it doesn't seem to have any out of the box CMake support.

Microsoft already has universal cross flatform low level spyware as C# and .NET (which is used by tons of even native linux games, especially made with Unity), mono is sponsored by Microsoft and has telemetry. Wine also uses mono.

And then installs proprietary steam, spotify, vscode and develops on C# for linux with telemetry even in mono runtime...

A little introduction about pylint. Pylint is a static code analyzer, it analyses your code without actually running it. Pylint looks for potential errors, gives suggestions on coding standards that your code is not adhering to, potential places where refactoring might help, and also warnings about smelly code.

Pylint, on the other hand, focuses on code analysis and style checking. It offers extensive customization options and supports various coding standards. Pylint is known for its comprehensive reports and ability to detect a wide range of code issues.

In my opinion, the best way to expose configuration options is to read and parse them from the project's pyproject.toml file. Here's how Pylint handles it.

I even contributed to Pylint by submitting a new rule a few years ago : implicit-str-concat.

Implemented code formatting with Black and linting with Pylint in my CI pipeline. Here is my updated GitHub Actions Workflow file: ci.yml

One last thing to do before running the hooks is to create a config file, just like we did with flake8. For this you are going to create a pylintrc file at the roor of your project and copy the contents of the pylintrc file from the pylint repo (here is the link to it).