Oleksandr's blog post on what's better. A lot of good points that are based on experience instead of published feature lists.
#Vscode
#pyconus profiling - There is a tool named `perf` that uses stackpointers (a feature of 3.12) and features tangentially related to JITs (3.13) to allow native code profilers to tell you where you python is slow (e.g. too many copies or bad branch prediction)
oh now I see why a copy-paste JIT is isomorphic to instrumenting python for performance profiling. Both wrap each opcode in a little function.
♡ 0 ↻ 0
#VSCode is free in the same way that you can write an IDE yourself for free is free. I'm complaining specifically about the time spent configuring plugins.
An empty text file where you can write rust or c can also be viewed as an IDE with plugin support. Just plug in enough code and you got an IDE or an IDE with a RPG game. Unlimited power and flexibility all for free!
#Devcontainers will be a thing when the number of hours spend fighting #podman and #docker are less than the number of hours spent trying to install an app from an outdated README
We ain't there yet. This technology is like 40 or 50 years premature.
#vscode supports multiple devcontainer documents now.
This is a painpoint when you're trying to create a devcontainer that works for all your repos and all the members of your team and all the possible usage scenarios, and there isn't 1 dev container that them all & I don't want people editing the (shared) files.
https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_75.md
What both #pycharm #vscode and #codespaces are missing are music integration.
It should change playlist and station based on what code you're writing. If the build has failed 10 times in a row, it should play something calm, 1970s love ballads. If you're writing Perl, it should play something nightmarish, like Angelspit