Visual Studio Code VS awesome-wayland

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

IDE: Many IDES can be used with Flutter but the two most common ones are; Android Studio and Visual Studio Code (VS code). We will work through the setup of VS Code in this article. To download VS Code, just click on Visual Studio Code if you are on Windows or Visual Studio Code for iOS

Yup. Here is an example list of things you can swap around. https://github.com/natpen/awesome-wayland

You didn't say whether your current config is based on X or Wayland therefore two links with Wayland applications. Are we Wsyland yet and awesome wayland

plenty others of all sorts.

> auto keyboard/mouse scripting with xdotool

There's a few tools for this: https://github.com/natpen/awesome-wayland#tools

> not have unnecessary mouse/keyboard to monitor delay

There's none that I can notice. Mice cursor are rendered with hardware support

Here's one of many forks of an awesome-wayland repository that lists what's going on: https://github.com/natpen/awesome-wayland

customization isn't killed, it just takes time to adapt to a new protocol. check out all the stuff you can do with wayland

More specifically, see: awesome-wayland and arewewaylandyet. Sway-addons also has interesting stuff in it, like wl-clipboard which is mostly compatible with Klipper.