News for hackers. Stuff that matters.
Re:I Fixed Windows Native Development by tgtweak on Sunday February 15, 2026 @09:19AM (#47023865)
Toolchains on linux are not clear from dependency hell either - ever install an npm package that needs cmake underneath? glibc dependencies that can't be resolved because you need two different versions simultaneously in the same build somehow... python in another realm here as well. That shiny c++ project that needs a bleeding edge boost version that is about 6 months away from being included in your package manager. Remember patching openSSL when heartbleed came around (libssHELL).

Visual studio is a dog but at least it's one dog - the real hell on windows is .net framework. The sheer incongruency of what version of windows has which version of .net framework installed and which version of .net your app will run in when launched... the actual solution at scale for universal windows compatibility on your .net app is to build a c++ shim that checks for .net beforehand and executes it with the correct version in the event of multiple version conflict - you can literally have 5 fully unique runtimes sharing the same .net target.

Re:I Fixed Windows Native Development by nanoxide on Sunday February 15, 2026 @09:36AM (#47024015)
When was the last time you actually used. NET? Because that's absolutely not how it is. The. NET runtime is shipped by default with Windows and updated via WU. Let alone that you're talking about .NET Framework which has been outdated for years.
Re:I Fixed Windows Native Development by tgtweak on Sunday February 15, 2026 @12:01PM (#47025281)
The issue is in supporting older windows versions - which sadly is still a reality for most large-scale app developers.
Re:I Fixed Windows Native Development by p_ing on Sunday February 15, 2026 @12:12PM (#47025400)
https://github.com/dotnet/core/blob/main/release-notes/10.0/...

.NET 10 supports a Windows 10 build from 10 years ago.

Re:I Fixed Windows Native Development by tgtweak on Sunday February 15, 2026 @12:36PM (#47025618)
Yes and in the wild believe it or not you'll find windows 7 and windows 8.

We had just deprecated support for XP in 2020 - this was for a relatively large app publisher ~10M daily active users on windows. The installer was a c++ stub which checked the system's installed .NET versions and manually wrote the app.config before starting the .net wrapper (or tried to install portable .NET framework installer if it wasn't found at all).

The app supported .NET 3.5* (2.0 base) and 4 originally, and the issue was there was a ".NET Framework Client Profile" install on as surprising amount of windows PCs out there, and that version was incompatible with the app. If you just have a naked .NET exe, when you launch it (without an app.config in the current folder) the CLR will decide which version to run your app in - usually the "highest" version if several are detected... which in this case would start the app in the lightweight version and error out. Also, in the app.config file you can't tell it to avoid certain versions you basically just say "use 4 then 2" and you're up to the mercy of the CLR to decide which environment it starts you in.

This obviated overrides in a static/native c++ stub that did some more intelligent verifications first before creating a tailored app.config and starting the .net app.

Re:I Fixed Windows Native Development by p_ing on Sunday February 15, 2026 @01:57PM (#47026332)
Hey I have a PC running 98SE ;-)

I feel for those who have to support an OS no longer supported by the vendor. That's a tough position to be in, not only if a customer comes across a bug that is due to the OS, but it keeps you from advancing your desktop application forward.

Re:I Fixed Windows Native Development by ryandrake on Sunday February 15, 2026 @07:56PM (#47029568)
You can always have legacy builds for older systems and use shiny new features inside conditional compilation blocks. Or check at runtime and let newer operating systems use the new features. Yes it takes care and a little more testing to keep supporting older operating systems but your users will love you for it.

I’m always kind of sad when a developer says to a customer “your OS is too old. We are dropping you on the floor.”

Re:I Fixed Windows Native Development by p_ing on Monday February 16, 2026 @09:59AM (#47035830)
Sure, you can take on that technical debt! ;-)
Re:I Fixed Windows Native Development by p_ing on Sunday February 15, 2026 @10:45AM (#47024602)
.NET runtime is not shipped with Windows, but once installed can be updated by WU.

Only the latest .NET Framework 4.8 is shipped with Windows at this point.

Re:I Fixed Windows Native Development by croes on Sunday February 15, 2026 @10:15AM (#47024347)
.NET versions are faster outdated then .Net Framework 4.8
Re:I Fixed Windows Native Development by stackskipton on Sunday February 15, 2026 @11:06AM (#47024792)
Point? I’m SRE on .Net project, we have been through 6-8-10 and its cost us about 2ish hours of work each time. As long as you don’t get crazy, .Net upgrades is just matter of new SDK and runtime and away you go.
Re:I Fixed Windows Native Development by tgtweak on Sunday February 15, 2026 @12:41PM (#47025658)
You're talking about .net for server applications right? The discussion above is for client apps being distributed for windows endusers.
Re:I Fixed Windows Native Development by rblatz on Sunday February 15, 2026 @03:40PM (#47027319)
Just ship a self contained build?
Re:I Fixed Windows Native Development by tgtweak on Sunday February 15, 2026 @09:47PM (#47030323)
This was a sidecar application distributed by literally millions of installs per day - so having a 25MB "self contained" build was out of the question - we were targeting KB-sized distributables not 10's of MB.
Re:I Fixed Windows Native Development by stackskipton on Sunday February 15, 2026 @01:06PM (#47025872)
We have a small MAUI part of the application, it's not massive but it's working fine with .Net Upgrades.
Re:I Fixed Windows Native Development by croes on Sunday February 15, 2026 @01:43PM (#47026213)
A .net framework 4.8 app has zero hours of work.

Why is it ok that you have to invest 2 times number of apps hours just because MS has such a short life cycle for its .NET versions.

Re:I Fixed Windows Native Development by torginus on Monday February 16, 2026 @10:51AM (#47036545)
.NET Framework is a Windows system component, but it's been deprecated and Microsoft is moving away from it. The modern .NET ships as either a downloadable runtime/SDK, or can be bundled with your application, meaning your app has no dependencies.
Re:I Fixed Windows Native Development by pjmlp on Sunday February 15, 2026 @09:33AM (#47023996)
Which has been fixed on .NET 5 and later.

.NET Framework should only be used for legacy applications.

Unfortunately there are still many around that depend on .NET Framework.

Re:I Fixed Windows Native Development by foepys on Sunday February 15, 2026 @10:00AM (#47024230)
Since .NET 10 still doesn't support Type Libraries quite a few new Windows projects must be written in .NET Framework.

Microsoft sadly doesn't prioritize this so this might still be the case for a couple of years.

One thing I credit MS for is that they make it very easy to use modern C# features in .NET Framework. You can easily write new Framework assemblies with a lot of C# 14 features. You can also add a few interfaces and get most of it working (although not optimized by the CLR, e.g. Span). For an example see this project: https://www.nuget.org/packages/PolySharp/

It's also easy to target multiple framework with the same code, so you can write libraries that work in .NET programs and .NET Framework programs.

Re:I Fixed Windows Native Development by pjmlp on Sunday February 15, 2026 @10:32AM (#47024465)
Most likely never will, because WinRT is the future and WinRT has replaced type libraries with .NET metadata. At least from MS point of view.

The current solution is to use the CLI tools just like C++.

However have you looked into ComWrappers introduced in .NET 8, with later improvements?

I still see VB 6 and Delphi as the best development experience for COM, in .NET it wasn't never that great, there are full books about doing COM in .NET.

Re:I Fixed Windows Native Development by croes on Sunday February 15, 2026 @10:14AM (#47024343)
.Net Framework 4.8 has a longer life cycle as the current .NET version
Re:I Fixed Windows Native Development by 8cvor6j844qw_d6 on Sunday February 15, 2026 @10:56AM (#47024708)
When I first worked with dot NET I was confused with the naming and version numbers.
Re:I Fixed Windows Native Development by ozim on Sunday February 15, 2026 @11:08AM (#47024808)
This argument against .NET annoys me.

Because that’s pretty much any freaking thing - oh Python, oh PHP, oh driving a fork lift, oh driving a car.

Once you invest time in using and learning it is non issue.

I do get pissed off when I want to use some Python lib bit it just doesn’t work out of the box, but there is nothing that works out the box without investing some time.

Just like a car get a teenager into a car he will drive into first tree.

Posting BS on Facebook shouldn’t be benchmark for how easy things should be.

Re:I Fixed Windows Native Development by pjmlp on Sunday February 15, 2026 @10:33AM (#47024468)
It does, but current versions can be shipped with the application.

Thus this should be less of a problem.

Re:I Fixed Windows Native Development by sippeangelo on Sunday February 15, 2026 @11:01AM (#47024756)
.NET Framework 5 or .NET Core 5?
Re:I Fixed Windows Native Development by afdbcreid on Sunday February 15, 2026 @11:50AM (#47025182)
There is no .NET Framework 5. .NET Core 5 is just .NET 5.
Re:I Fixed Windows Native Development by tomkarho on Sunday February 15, 2026 @10:47AM (#47024619)
.NET does have flags to include the necessary dependencies with the executable these days so you can just run the .exe and don't need to install .net on the host machine. Granted that does increase the size of the app (not to mention adding shitton of dll's if you don't build as single executable) but this at least is a solved problem.
Re:I Fixed Windows Native Development by tgtweak on Sunday February 15, 2026 @12:42PM (#47025673)
They do now, after .net core and several other iterations. You'll also be shipping a huge executable compared to a clr linked .net app (which can be surprisingly small).
Re:I Fixed Windows Native Development by cmoski on Sunday February 15, 2026 @11:24PM (#47030872)
Mine is 33mb. Could be smaller, but it does the trick.
Re:I Fixed Windows Native Development by giancarlostoro on Sunday February 15, 2026 @09:26AM (#47023938)
I went from POP OS (Ubuntu) to EndeavourOS (Arch) Linux because some random software with an appimage or whatever refused to run with Ubuntus “latest” GLIBC and it ticked me off, I just want to run more modern tooling, havent had any software I couldnt just run on Arch, going on over a year now.
Re:I Fixed Windows Native Development by moogly on Sunday February 15, 2026 @12:27PM (#47025525)
Indeed. As late as 2 hours ago I had to change the way I build a private Tauri 2.0 app (bundled as .AppImage) because it wouldn't work on latest Kubuntu, but worked on Fedora and EndeavourOS. So now I have to build it on Ubuntu 22.04 via Docker. Fun fun.

Had fewer issues on EndeavourOS (Arch) compared to Fedora overall though... I will stay on Arch from now on.

Re:I Fixed Windows Native Development by TZubiri on Sunday February 15, 2026 @10:18AM (#47024368)
>Toolchains on linux are not clear from dependency hell either - ever install an npm package that needs cmake underneath?

That seems more a property of npm dependency management than linux dependency management.

To play devil's advocate, the reason npm dependency management is so much worse than kernel/os management, is because their scope is much bigger, 100x more package, each package smaller, super deep dependency chains. OS package managers like apt/yum prioritize stability more and have a different process.

Re:I Fixed Windows Native Development by the__alchemist on Sunday February 15, 2026 @09:59AM (#47024220)
This is one of the things that tilts me about C and C++ that has nothing to do with mem safety: The compile/build UX is high friction. It's a mess for embedded (No GPOS) too in comparison to rust + probe-rs.
Re:I Fixed Windows Native Development by Pay08 on Sunday February 15, 2026 @12:03PM (#47025303)
That hasn't been my experience at all. Cross-compiling anything on Rust was an unimaginable pain (3 years or so ago). While GCCs approach of having different binaries with different targets does have its issues, cross compiling just works.
Re:I Fixed Windows Native Development by the__alchemist on Sunday February 15, 2026 @12:35PM (#47025611)
Ah sorry. I should clarify. Not referring to specifically cross compiling; just general compiling. In rust weather PC or embedded, I run Cargo run. For C or C++, it's who knows. A provincial set of steps for each project, error messages, makes me get frustrated. I keep a set of notes for each one I touch to supplement the project's own docs. I am maybe too dumb or inexperienced in some cases, but I am having a hard time understanding why someone would design that as the UX.

I want to focus on the project itself; not jump through hoops in the build process. It feels hostile.

For cross compiling to ARM from a PC in rust in particular, you do one CLI cmd to add the target. Then cargo run, and it compiles, flashes, with debug output.

These are from anecdotes. I am probably doing something wrong, but it is my experience so far.

Re:I Fixed Windows Native Development by Pay08 on Sunday February 15, 2026 @12:40PM (#47025651)
That sounds like you don't have a build system for C/C++.
Re:I Fixed Windows Native Development by ryandrake on Sunday February 15, 2026 @08:01PM (#47029603)
I’m the opposite: I want my development tools to use my operating system’s package manager. Nothing enrages me quite like how, when I want to pull in a Python dependency, I have to reach for Python’s parallel package manager. Now I have to keep track of what apt installed and what pip installed. Then I move to do a rust project and there’s now another parallel package manager I need to use to install those dependencies! Yuck!

apt install build-essential or whatever the rpm equivalent is, gets you most of the way to building a C or C++ project.

Re:I Fixed Windows Native Development by the__alchemist on Sunday February 15, 2026 @09:43PM (#47030298)
If I understand correctly, this makes your program and/or its build system tied to an OS. Depending on the details (You mention interpreted and compiled languages), it's not clear if this would provincialize the build only, or running the application as well. (With complications beyond executable ABI compatibility)

My perspective: I want from the OS: An allocator, threading, filesystem support, dates/times, and in some cases hardware access like for GPUs, USB etc.

I do not want my software to be dependent on a specific OS's package manager. I don't want a headache when I change the PC I'm compiling on, and really don't want to deal with a separate package manager for each OS I distribute the application for. Especially so given that there are so many linux distros.

Re:I Fixed Windows Native Development by ryandrake on Tuesday February 17, 2026 @11:01AM (#47048954)
I don't care if my package manager is provided by my OS or by some third party--I only want to deal with one package manager. Currently we have these Matryoshka dolls where there are package managers inside package managers, and each of them manage their own distinct trees of dependencies.
Re:I Fixed Windows Native Development by calvinmorrison on Sunday February 15, 2026 @10:15AM (#47024351)
> Toolchains on linux are not clear from dependency hell either - ever install an npm package.

That's where I stopped.

Toolchains on linux distributions with adults running packaging are just fine.

Toolchains for $hotlanguage where the project leaders insist on reinventing the packaging game, are not fine.

I once again state these languages need to give up the NIH and pay someone mature and responsible to maintain packaging.

Re:I Fixed Windows Native Development by Pay08 on Sunday February 15, 2026 @12:10PM (#47025377)
The real kicker is when old languages also fall for this trap. The latest I'm aware of is GHC, which decided to invent it's own build system and install script. I don't begrudge them from moving away from Make, but they could have used something already established.
Re:I Fixed Windows Native Development by crote on Sunday February 15, 2026 @10:37AM (#47024511)
The counterpoint of this is Linux distros trying to resolve all global dependencies into a one-size-fits-nothing solution - with every package having several dozen patches trying to make a brand-new application release work with a decade-old release of libfoobar. They are trying to fit a square peg into a round hole and act surprised when it doesn't fit.

And when it inevitably leads to all kinds of weird issues the packagers of course can't be reached for support, so users end up harassing the upstream maintainer about their "shitty broken application" and demanding they fix it.

Sure, the various language toolchains suck, but so do those of Linux distros. There's a reason all-in-one packaging solutions like Docker, AppImage, Flatpak, and Snap have gotten so popular, you know?

Re:I Fixed Windows Native Development by fao_ on Sunday February 15, 2026 @10:42AM (#47024567)
> The counterpoint of this is Linux distros trying to resolve all global dependencies into a one-size-fits-nothing solution - with every package having several dozen patches trying to make a brand-new application release work with a decade-old release of libfoobar. They are trying to fit a square peg into a round hole and act surprised when it doesn't fit.

This is only the case for debian and derivatives, lol. Rolling-release distributions do not have this problem. This is why most of the new distributions coming out are arch linux based.

Re:I Fixed Windows Native Development by Pay08 on Sunday February 15, 2026 @12:04PM (#47025313)
I'm going to need a source for both of those claims.
Re:I Fixed Windows Native Development by jcgl on Sunday February 15, 2026 @12:46PM (#47025706)
It sure sounds very Debian-ish, at least. I’m a Fedora user, and Fedora stays veeeery close to upstream. It’s not rolling, but is very vanilla.
Re:I Fixed Windows Native Development by Pay08 on Sunday February 15, 2026 @01:19PM (#47025977)
Agreed, but I don't think that has to do with either it's "vanillaness" or the 6 month release schedule. Fedora does a lot of compatibility work behind the scenes that distros not backed by a large company more than likely couldn't afford.
Re:I Fixed Windows Native Development by jcgl on Monday February 16, 2026 @05:13AM (#47033222)
"Vanillaness" is exactly what's in-scope here:

> ...every package having several dozen patches trying to make a brand-new application release work with a decade-old release of libfoobar.

Applying non-vanilla flavor (patches) to libraries in able to make new packages work with old packages. (It's not just a library thing of course--I've run into packages on Debian where some component gets shimmed out by some script that calls out to some script to dynamically build or download a component. But I digress.)

Maybe I'm just out of the loop here, but I'm not aware of this being a general practice in Fedora. Yes, Fedora does a lot of compatibility work of course, but afaik the general practice isn't to add Fedora-flavored patches.

Re:I Fixed Windows Native Development by fao_ on Monday February 16, 2026 @12:42AM (#47031278)
`crote` claimed:

> with every package having several dozen patches trying to make a brand-new application release work with a decade-old release of libfoobar.

Quite frankly, as someone started distro-hopping around ~2009 & only stopped around 2020, I have experienced a lot of Linux distributions, as well as poked at a lot of maintainer pipelines — it is simply categorically untrue for the majority of non-Debian derived Linux distributions.

It used to be that a decent number of Linux distributions (Slackware, Debian, RedHat, whatever) put in a lot of work to ensure "stability", yes. However "stability" was, for the most part, simply backporting urgent security fixes to stable libraries and to their last three or so versions. The only system that is very well known for shipping "a decades old version" of a system library would be Debian (or its biggest derivative, Ubuntu), because it's release cycle is absolutely glacial, and most other Linux distributions do give somewhat of a shit about keeping relatively close to upstream. If only because maintaining a separate tree for a program just so you can use an ancient library is basically just soft-forking it, which incurs a metric shitton of effort and tech-debt that accrues over time.

One of the reasons I switched to and then ran at least one single Arch Linux installation for the back half of the 2010s (and used other computers or a dual boot for distrohopping) was partly for the challenge (I used to forget to read the NEWS before upgrading and got myself into at least one kernel panic that way lol), and partly because it was the only major rolling-release distribution at the time. In the last 6 years that's changed a lot, and now there's a whole slew of rolling-release distributions to choose from. The biggest is probably Steam's Holo distribution of Arch, but KDE's new distribution (replacing Kubuntu as the de-facto "KDE Distro") is based on Arch as well, along with I think Bazzite and CachyOS; Arch has always had a reputation (since before the 2010s) for keeping incredibly close to upstream in it's package distributions, and I think that ideology has mostly won-out now that a lot of Linux software is more generally stable and interacts reasonably well (Whereas, back when Pipewire was a thing... that was not the case).

Now, sure, I'm not going to the effort of compiling my decade+ experience of Linux into a spreadsheet of references of every major distribution I tried in the last ten years, just to prove all of this on an internet forum, but hopefully that write-up will suffice. Furthermore, as far as I can see, the burden of proof is not on me, but on `crote` to prove the claim they made.

Also, I get how if you've only ever used Debian-derivatives, all of this may appear to be incorrect. I would suggest, uh, not doing that — if only because it's a severely limiting view of what Linux systems are like. Personally, I've been a big fan of using Alpine's Edge release since before they had to drop linux-hardened and it's a really nice system to use as a daily driver.

Re:I Fixed Windows Native Development by IshKebab on Sunday February 15, 2026 @10:14AM (#47024344)
> python in another realm here as well

uv has more of less solved this (thank god). Night and day difference from Pip (or any of the other attempts to fix it honestly).

At this point they should just deprecate Pip.

Re:I Fixed Windows Native Development by LtWorf on Sunday February 15, 2026 @11:26AM (#47024956)
Ah yes let's all depend on some startup that will surely change the license at some point.
Re:I Fixed Windows Native Development by IshKebab on Sunday February 15, 2026 @12:38PM (#47025636)
Very clearly a better option than continuing to use Pip. Even if they do change the license in a few years I will definitely take several years of not being shat on by Pip over the comparatively minor inconvenience of having to switch to an open fork of uv when they rug-pull. If they ever do.

Continuing to use Pip because Astral might stop maintaining uv in future is stupidly masochistic.

Re:I Fixed Windows Native Development by kingstnap on Sunday February 15, 2026 @07:02PM (#47029164)
pip is really bad though so UV has a long ways to fall before you aren't still net better off :^)
Re:I Fixed Windows Native Development by rbanffy on Sunday February 15, 2026 @06:12PM (#47028732)
I have never experienced issues with pip, and I’m not sure it’s whether I’m doing something that pip directly supports and avoiding things it doesn’t help with.

I’d really love to understand why people get so mad about pip they end up writing a new tool to do more or less the same thing.

Re:I Fixed Windows Native Development by IshKebab on Monday February 16, 2026 @03:43AM (#47032525)
The problems with pip that uv fixes:

1. It's easy to install.

2. It's not dog slow.

3. It automatically sets up venvs.

4. It automatically activates the venv before running commands.

5. It supports a lock file out of the box.

6. It lets you specify the index for private packages. This fixes a major security issue with pip that they continue to ignore.

7. It installs your code in the venv in editable more by default.

8. It lets you install Python tools outside the venv (`uv tool install`).

9. It works reliably.

There's probably more that I've forgotten. If pip had all of that nobody would have felt the need for a rewrite. And if you've never run into any of those issues I guess you either haven't used Python much or didn't consider that there might be a less shitty way to do things.

Re:I Fixed Windows Native Development by rbanffy on Monday February 16, 2026 @05:51AM (#47033522)
> 2. It's not dog slow.

That’s very subjective. I have ADHD and I’m very sensitive to things that break my flow, but I don’t run pip frequently while I’m writing code, and the couple extra seconds it takes to do its job don’t bother me that much.

> 3. It automatically sets up venvs.

Remember: explicit is better than implicit.

> 4. It automatically activates the venv before running commands.

Again: explicit is better than implicit.

> 5. It supports a lock file out of the box.

Some (me included) would say it’s a bug, not a feature.

> 6. It lets you specify the index for private packages. This fixes a major security issue with pip that they continue to ignore.

This is good - a lot of organisations concerned with that will block access to PyPI altogether and offer a selected cache for approved dependencies. Alternatively you can declare private dependencies as Git URLs with tags, bypassing the need for a private index.

> 7. It installs your code in the venv in editable more by default.

That’s a nice touch, but goes against the explicit/implicit rule- a different behaviour automatically triggered by something environmental.

> 8. It lets you install Python tools outside the venv (`uv tool install`).

I always recommend not messing with the system’s Python.

> 9. It works reliably.

I’ll need you to elaborate on that. I might be used to the way pip works, but it’s been a while since I had it fail to do something I asked without there being a very good reason (an impossible conflicting requirement).

This brings me to another concern - I wouldn’t want Python development to become more like JavaScript post-npm. Every external dependency you bring in must be justified and understood. This goes for simple ones and especially for complex ones with lots of secondary dependencies. Any external dependency you bring is now your responsibility to manage forever. I’m fine not having to reimplement NumPy’s MSE function or Django’s ORM, but I’ve moved away from things like click because they save me just a little extra work at the cost of having to remember it’s there forever.

> And if you've never run into any of those issues I guess you either haven't used Python much or didn't consider that there might be a less shitty way to do things.

Or, perhaps, I’ve been using Python since 1.5 and have a deep understanding of why things are the way they are, having experimented with different ways, and just learned that new and convenient isn’t always the best in the long term.

Re:I Fixed Windows Native Development by IshKebab on Monday February 16, 2026 @07:44AM (#47034311)
> Remember: explicit is better than implicit.

It's not implicit. When you run `uv run ...` or `uv sync` you are explicitly asking it to automatically set up a venv.

> Some (me included) would say it’s a bug, not a feature.

Some (you included) would be wrong.

> This is good

What is good? That Pip doesn't have a way to avoid dependency confusion? What??

> but goes against the explicit/implicit rule

No it doesn't. It just does the right thing by default.

> I always recommend not messing with the system’s Python.

The reasons to avoid `pip install pre-commit` (outside a venv) are precisely because Pip can't do that in a sane way! `uv tool install pre-commit` suffers from none of the reasons to avoid `pip install pre-commit`.

You definitely have stockholm syndrome. Give uv a try.

Re:I Fixed Windows Native Development by arendtio on Sunday February 15, 2026 @02:14PM (#47026485)
Well, traditionally, there was no Python/pip, JS/npm in Linux development, and for C/C++ development, the package manager approach worked surprisingly well for a long time.

However, there were version problems: some Linux distributions had only stable packages and therefore lacked the latest updates, and some had problems with multiple versions of the same library. This gave rise to the language-specific package managers. It solved one problem but created a ton of new ones.

Sometimes I wish we could just go back to system package managers, because at times, language-specific package managers do not even solve the version problem, which is their raison d'être.

Re:I Fixed Windows Native Development by majoe on Sunday February 15, 2026 @03:33PM (#47027268)
Nix devShells works quite well for Python development (don't know about JS) Nixpkgs is also quite up to date. I haven't looked back, since adopting Nix for my dev environments.
Re:I Fixed Windows Native Development by vips7L on Sunday February 15, 2026 @04:10PM (#47027577)
.net has been able to ship the runtime with your app for years.
Re:I Fixed Windows Native Development by eqvinox on Sunday February 15, 2026 @04:40PM (#47027869)
> glibc dependencies that can't be resolved because you need two different versions simultaneously in the same build somehow...

If you somehow experience an actual dependency issue that involves glibc itself, I'd like to hear about it. Because I don't think you ever will. The glibc people are so serious about backward and forward compatibility, you can in fact easily look up the last time they broke it: https://lwn.net/Articles/605607/

Now, if you're saying it's a dependency issue resulting from people specifying wrong glibc version constraints in their build… yeah, sure. I'm gonna say that happens because people are getting used to pinning dependency versions, which is so much the wrong thing to do with glibc it's not even funny anymore. Just remove the glibc pins if there are any.

As far as the toolchain as a whole is concerned… GCC broke compatibility a few times, mostily in C++ due to having to rework things to support newer C++ standards, but I vaguely remember there was a C ABI break somewhere on some architecture too.

Re:I Fixed Windows Native Development by HexDecOctBin on Sunday February 15, 2026 @08:25PM (#47029789)
> The glibc people are so serious about backward and forward compatibility, you can in fact easily look up the last time they broke it

What? There was a huge breakage literally last year: https://sourceware.org/bugzilla/show_bug.cgi?id=32653

Glibc has been a source of breakage for proprietary software ever since I started using Linux. How many codebases had to add this line around 2014 (the year I brought my first laptop)?

    __asm__ (".symver memcpy, memcpy@GLIBC_2.2.5");
Re:I Fixed Windows Native Development by eqvinox on Sunday February 15, 2026 @10:54PM (#47030702)
> https://sourceware.org/bugzilla/show_bug.cgi?id=32653

dlopen and dlmopen no longer make the stack executable if a shared library requires it

I'm not counting intentional breakage to improve system security. I'm not even sure I'd call it an ABI breakage; by a wide definition I guess it is a "change in glibc that makes things not work anymore". You also can't execute a.out binaries anymore, eh. And I don't think I would call something that affects primarily closed source binaries (and mono on i386) a "huge" issue either.

The fix is trivial ("execstack -s <binary>") and doesn't involve any change to installed versions of anything.

> __asm__ (".symver memcpy, memcpy@GLIBC_2.2.5");

A 12 year old forward compatibility issue that is fixed by upgrading glibc, okay. (Note this is the same timeframe as the s390 thing I linked.) I guess people shipping binaries need to be aware of it if they want to support glibc pre-2.2.14. That said, the general rule of shipping binaries is that you need to assume whatever you build against becomes the minimum required version, anything else is a gift.

I think my point about never pinning glibc stands, and how many other things do you know where you need to go back 12 years to find an ABI break?

Re:I Fixed Windows Native Development by manwe150 on Sunday February 15, 2026 @11:21PM (#47030855)
A few recent examples: many distros changed the flag for emuTLS on Windows, which gcc implemented as a hard ABI break for no essential reason. If you compile for enough platforms, it will print various notes that various alignments have changed in the struct, which has caused grief numerous times in the past few years for people I work with (many of the changes don’t come with notes, they just change alignment since new hardware comes out that has new features which need more and/or there were bugs previously, so they silently change it). There’s also win32 or posix threading, and sjlj vs structured exceptions, all of which are mutually incompatible. Oh, and then don’t get me started on ARM v6 atomics, which is some weird decided-based-on-compiler-flags-to-record-heuristics-detected-during-configure-of-some-auxiliary-header time, instead of using the current target’s ABI

Sure, the ABI does not change at all, if you know in advance where the landmines are. Though it does have quite few, especially for a large project with a huge surface area

Re:I Fixed Windows Native Development by eqvinox on Monday February 16, 2026 @04:35AM (#47032906)
I was talking about glibc; none of the things you mention relate to that. (Note glibc is not used on Windows.) I'm painfully aware of some of the breakage GCC occasionally causes (the atomics fall into that — but to be fair ARMv6 is also >10 years ago at this point, unless you're doing embedded, in which case you generally build the whole system anyway and don't care about these breaks.)

Also, just in case it's not clear, glibc has nothing to do with GCC.

Re:I Fixed Windows Native Development by xg15 on Monday February 16, 2026 @04:45AM (#47032987)
You can have one of "they're so serious about forward and backward compat you should remove version pins because things won't ever break" and "well, I'm not counting intentional breaks" but not both.
Re:I Fixed Windows Native Development by eqvinox on Monday February 16, 2026 @02:03PM (#47038870)
Why? Is it not normal to have a first priority and a second priority? Does it not make sense for security to come before other things?
Re:I Fixed Windows Native Development by xg15 on Monday February 16, 2026 @05:18PM (#47041124)
I don't know much about glibc's specifics, but in general: Security comes before a lot of things but not before accidental breakage. If you say "our compat guarantees are so strong you shouldn't keep track of versions at all", I expect this to mean that APIs and ABIs will never change, or at least not without a massive awareness campaign and transition plan being announced before - because such a breakage would take out my project or might even introduce new vulnerabilities.

A security update that also does breaking changes is sort of the worst case, because dependents are essentially damned if they apply it and damned if they don't. They can't always be avoided if an API is so insecure it's beyond repair - but then dependents will have to update in their own time because they will also have to fix their own implementations. So this would be an argument for version pins in that case.

Re:I Fixed Windows Native Development by eqvinox on Monday February 16, 2026 @11:01PM (#47043563)
> Security comes before a lot of things but not before accidental breakage.

It didn't really sound accidental, though the bugzilla report sounds like they underestimated the impact. But I'm quite sure they were aware this would break at least some old software, it's not like it's hard to understand what exactly is happening here. Old software (or rather, builds) used executable stacks by default, and some edge cases used them for some time after that. I'll say they probably should've done a warning period.

> If you say "our compat guarantees are so strong you shouldn't keep track of versions at all",

What I said was you should never pin a glibc version, not to not keep track of versions at all :). I will admit this is hazy if you build binaries to distribute; in that case you probably want to intentionally use an old glibc. But that's not exactly a "pin", that's a "what's the oldest you want to support". The software being built basically makes no difference; glibc will do what it does, the only limit will be placed by features added in newer glibc versions. The binaries produced from that, running on a new system with any newer glibc, have AFAIK last broken during that S390 incident I linked. (e.g. you wouldn't have gotten executables requiring executable stacks out of a normal GNU tool chain for quite some time by now. It's still possible to intentionally mangle your code and build options to get that result, but you need to either be trying, or do relatively cursed things [like Mono probably some binary loading shenanigans]).

Either way — never pin glibc. And if your cmake or whatever complains about a glibc version conflict, remove the pins and use the newest version involved.

(And about the execstack thing — I'm happy to hear your complaints if and only if you show up with an actual report of breakage that you encountered. No 3rd party phoning. Because what's at question in this case is the actual impact size, which to me seems quite limited.)

> A security update that also does breaking changes is sort of the worst case, because dependents are essentially damned if they apply it and damned if they don't. They can't always be avoided if an API is so insecure it's beyond repair - but then dependents will have to update in their own time because they will also have to fix their own implementations. So this would be an argument for version pins in that case.

That's not how DSO versioning works. Unless it was a horrible disaster, the old functions would remain available, but you'd be required to jump through hoops to build new software against it.

Because glibc ships basically their entire version history in the library binary. That's the thing with DSO versioning.

I do wonder if they could've done some versioning trick with the execstack thing, the problem there is that it's more about global system behavior than actual exposed ABIs. (By the way, libc isn't even what you would be "pinning" there, it's libdl. Splitting hairs though, as that's part of glibc.)

Re:I Fixed Windows Native Development by HexDecOctBin on Tuesday February 17, 2026 @07:18PM (#47055379)
> Because what's at question in this case is the actual impact size, which to me seems quite limited.

It was widely covered in media. Some of the most popular games and software broke:

1. https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-...

2. https://www.phoronix.com/news/Glibc-WA-Steam-Exec-Stack

This is the attitude that will always prevent GNU/Linux from becoming prevalent for personal computing. There is a such a lack of empathy for users' hardships and it shows.