4 ms·
Question: If we want to write an gui app and have the binary continue to work on anything linux just about forever, how far does static linking get you? In mos
by harry8 5y ago
Question: If we want to write an gui app and have the binary continue to work on anything linux just about forever, how far does static linking get you?
In most cases disk is not the resources most needed to optimize. Granted you don't get bugfixes in your libraries but you made the call that they were working well enough, and if security is at issue old binaries probably aren't a good answer ever?
Statically linked to everything including libc should be forwards compatible with any kernel upgrade - "don't break userspace"
Your app isn't the xserver. Do X upgrades break it? I imagine a distro switch to Wayland would? Or do they reverse compatible an X abi? Anything else that could change under you? Other servers than X? Anything else I'm missing?
Anyone else remember being told that the answer was Java? What happened to that?
- kodah 5y agoI can't speak to the long-term limitations of static linking. I will say that the JVM is a user-side hurdle which is undesirable. I usually use Rust or Go for cross compilation.