4 ms·
The different platform argument was easy to make when it was called ".NET Core". Almost impossible to make when it's also called ".NET", quite deliberately.
by edandersen 4y ago
The different platform argument was easy to make when it was called ".NET Core". Almost impossible to make when it's also called ".NET", quite deliberately.
- dragonwriter 4y agoNo, really, version numbers within a broader brand that can indicate incompatibility are not something non-technical users with any familiarity with modern consumer society are unfamiliar with. I get that techies sometimes have preferences for perfect and eternal backward compatibility within a named product line, but trying to pass this off with “how will you explain this to non-techies”, and then treating non-techies as both more ignorant and more concerned with technical details than they are, is not a good way to promote that preference.
- edandersen 4y ago"Our app was seamlessly upgraded from .NET 3.5 SP1 to .NET 4.0 and through to .NET 4.8.2. I don't believe you when you say it won't immediately run on .NET 5.0. My PS5 plays PS4 games. Upgrade it today as I'm off to play golf."
- TeMPOraL 4y ago> My PS5 plays PS4 games. That sounds like an outlier, though. Typically, consoles were not compatible between generations. PS1 games didn't play on PS2. PS2 games didn't play on PS3. Etc.
- dragonwriter 4y agoThe first version of the PS3 had hardware PS2 emulation. I think this was removed in later versions.