3 ms·

This actually makes sense in 2021 since we have the resources to allow things like this. 20 years ago this might have seemed insane.

vidanay 5y ago
30 years ago we used DOS and DLL Hell was a completely unknown concept. We did have to deal with himem.sys though.
- justin66 5y ago
  On the contrary, 30 years ago we were using Windows 3.0, which is about when dll hell started being a real thing. (DLL hell stopped being a problem a lot sooner than you probably think, too...)
  - nisegami 5y ago
    >DLL hell stopped being a problem a lot sooner than you probably think, too Does not match my experience at work unfortunately.
    - justin66 5y ago
      If you're seeing this on any version of Windows made in the last 22 years or so, it's because a software developer fucked up in a really creative way. My condolences. Sometimes the issue is that people have tended to conflate "dll hell" and "dependency hell." That's an old pet peeve of mine and I realize it doesn't matter...
ourmandave 5y ago
"Insert floppy disk 435 of 880 and press [Enter] when ready..."
- vidanay 5y ago
  Invalid media type Abort, Retry, Fail? FFFFFFFUUUUUUUUCCCCCCKKKKK!!!!!!
svick 5y ago
Keep in mind that it's just one option. If you want, you can still deploy your app separately from the .Net runtime. Also, to keep the size at least somewhat in check, unused parts of the base library are not included in the single-file mode.
cm2187 5y ago
Keeping in mind it's also a double edge sword. TLS deprecations alone will ensure your app will die after a few years if it doesn't run on an up-to-date CLR.
- dotancohen 5y ago
  This sounds quite the argument for basing critical workflows only on software for which the user has both access and permission to modify the source code.
- alasdair_ 5y ago
  Timezone and DST fuckery is another, I assume?

3 ms·

This actually makes sense in 2021 since we have the resources to allow things like this. 20 years ago this might have seemed insane.

by kingcharles 5y ago

vidanay 5y ago
30 years ago we used DOS and DLL Hell was a completely unknown concept. We did have to deal with himem.sys though.
- justin66 5y ago
  On the contrary, 30 years ago we were using Windows 3.0, which is about when dll hell started being a real thing. (DLL hell stopped being a problem a lot sooner than you probably think, too...)
  - nisegami 5y ago
    >DLL hell stopped being a problem a lot sooner than you probably think, too Does not match my experience at work unfortunately.
    - justin66 5y ago
      If you're seeing this on any version of Windows made in the last 22 years or so, it's because a software developer fucked up in a really creative way. My condolences. Sometimes the issue is that people have tended to conflate "dll hell" and "dependency hell." That's an old pet peeve of mine and I realize it doesn't matter...
ourmandave 5y ago
"Insert floppy disk 435 of 880 and press [Enter] when ready..."
- vidanay 5y ago
  Invalid media type Abort, Retry, Fail? FFFFFFFUUUUUUUUCCCCCCKKKKK!!!!!!
svick 5y ago
Keep in mind that it's just one option. If you want, you can still deploy your app separately from the .Net runtime. Also, to keep the size at least somewhat in check, unused parts of the base library are not included in the single-file mode.
cm2187 5y ago
Keeping in mind it's also a double edge sword. TLS deprecations alone will ensure your app will die after a few years if it doesn't run on an up-to-date CLR.
- dotancohen 5y ago
  This sounds quite the argument for basing critical workflows only on software for which the user has both access and permission to modify the source code.
- alasdair_ 5y ago
  Timezone and DST fuckery is another, I assume?