

But actual results and bugs have very little to do with corporate firings or open positions, as 30 years of history show us.
If corporations “think” they can fire people, with AI as an excuse, and put that cost in their pockets, they will do it. We are already seeing it in the US tech-bro sphere.
Companies will tank themselves in the medium-long term to make short term profits. Which I think is the “dev market” that OP is talking about. It shouldn’t affect the market, but it will because you have MBAs making technical decisions. I could be wrong, but the tech market is very predictable as far as behavior. They will hire a skeleton crew and work them to burnout to fix the AI slop. (Tech industry needs unions now)







Hey, something I can maybe help with.
Flatpak IDEs on the main system are not very useful for development. I got rid of mine entirely. I am developing firmware so it might be a bit different from your case, but what I did in have a single arch distrobox where I could install everything embedded-dev-related that had to work together (JLink, nordic tools, code-oss, etc…) on that. Then a few standalone debugging tools like STLink and Saelae logic2 could be installed to the home folder by default and Code could still find them from the distrobox (but they could be installed in the distrobox also). It doesn’t even need to have an init system, but I ran into a few problems like having to manually chmod usb devices to give STLink access. Udev rules are also hit or miss in /etc/udev/rules.d, e.g. the STM udev rules just don’t work, but nordic does.
High storage consumption is likely negligible (or at least nitpicky) since storage is so cheap nowadays. Your SSD doesn’t care if it has 15GB or 20GB of system programs, especially when development codebases and SDKs, games, and media will likely make up 90% of space and almost never share libraries even on traditional systems.