# SE-0346 and library evolution **URL:** \ **Category:** Discussion\ **Created:** [April 10, 2022, 8:30pm UTC](https://forums.swift.org/t/se-0346-and-library-evolution/56659 "2022-04-10T20:30:46Z")\ **Posts on this page:** 1\ **Showing post:** 44
**Author:** ![xwu](https://avatars.discourse-cdn.com/v4/letter/x/b487fb/32.png) [@xwu](https://forums.swift.org/u/xwu)\ **Post date:** [April 15, 2022, 1:53pm UTC](https://forums.swift.org/t/se-0346-and-library-evolution/56659/44 "2022-04-15T13:53:56Z")
> [@lorentey](#): > > I do want to point out that in this particular passage, you're expecting that people who (for whatever reason) won't update one piece of critical infrastructure (the OS) will on the other hand will enthusiastically upgrade another piece of critical infrastructure (the Swift compiler). Based on my personal experience, this doesn't ring true to me at all; in fact, from what I can tell, for a large chunk of users, the stability of the language environment is likely to be just as important (or more!) than the stability of the operating system. I have a work computer where the macOS version is fixed by central IT fiat, but on which I have broad latitude to install and run any tools I need to do my job. Therefore, the version of Swift I have on that machine is increasingly out of date, but not by choice. The general gist of the feedback you're getting is that, in fact, the scenario that doesn't ring true at all actually is the crux of the matter. That it is unaddressed is unsurprising given that there's such a lack of recognition that the problem exists at all. --- _[View the full topic](https://forums.swift.org/t/se-0346-and-library-evolution/56659)._