DietPi VS Visual Studio Code

DietPi is a lightweight Debian based Linux distribution for SBCs and server systems, with the option to install desktop environments, too. It ships as minimal image but allows to install complete and ready-to-use software stacks with a set of console based shell dialogs and scripts.

The source code is hosted on GitHub: https://github.com/MichaIng/DietPi

That's a good point, but the array of devices supported by the DietPi team is extensive: https://dietpi.com/

Before someone starts the usual yadda yadda about the RPi biger community, the OS not having long time support etc. I would repeat one more time: do not rely on board vendor supplied images; this is valid for pretty much all boards. Just go to Armbian or DietPi pages and you'll almost certainly find one or more images that work on your board and forums to discuss about them with very knowledgeable people.

https://www.armbian.com/download/

https://dietpi.com/#download

Those projects are well worth a contribution, as they don't have a giant like Broadcom behind them.

> bananapi do a lot of boards but their software story has been a bit poor

This is quite common with other board manufacturers too. I'd rather suggest to ignore completely their cobbled together distros, often also tainted by proprietary modifications, that become unmaintained in a few years, and see if they're among the many supported by Armbian or DietPi.

https://www.armbian.com/download/

https://dietpi.com/#download

The full release notes can be found at: https://dietpi.com/docs/releases/v8_25/

RPi OS = diet pi https://dietpi.com/ - initial config via text file - SDcard burning out partially mitigated as writes log files to ram then flushes to SDcard reducing write cycles

You could also try very minimalistic distros like TwisterUI or DietPi which are most known for their use in the RasprebbyPi / SBC computers but which also have editions for desktop / laptop.

In VSCode for example this can be easily done by adding the following .vscode/launch.json file:

I had a near-identical experience. I looked into switching in 2019 and ran into this 2016 bug which was a showstopper for me. Fixed it myself, grand total 4 line diff. https://github.com/microsoft/vscode/issues/10643

When working in Visual Studio Code (VS Code), always create a new Python file for your project.

Code Editor: Choose a code editor like Visual Studio Code that offers good support for web technologies and extensions for PWA development.

When working in Visual Studio Code (VS Code), create a new Python file for our music player project. It's helpful to have separate files for different parts of your project.

https://github.com/microsoft/vscode/forks

27,000 people seem to have done so.

Choosing IDE: Selecting a suitable Integrated Development Environment (IDE) is crucial for efficient coding. Consider popular options such as PyCharm, Visual Studio Code, or Jupyter Notebook. Install your preferred IDE and ensure it's configured to work with Python.

I was doing it all wrong, designing and developing on the fly, using the same tool - VScode; Making one step forward and ten back when I mess up with good code while trying to get rid of the bad. I had gotten away with it for three pages, but it had finally caught up with me.

VSCode