News for hackers. Stuff that matters.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by edandersen on Tuesday March 21, 2023 @07:01PM (#35253971)
Renaming .NET Core to ".NET" was a huge marketing bait and switch, essentially a laundering of the past sins of .NET Framework. Lots of people got involved with .NET Core because it *wasn't* plain ".NET" with all the negative connotations of being involved with that.

You now have ".NET 4.8.2" applications that cannot be upgraded to ".NET 5". Try explaining that to a non technical person.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by dragonwriter on Tuesday March 21, 2023 @07:05PM (#35254016)
> You now have “.NET 4.8.2” applications that cannot be upgraded to “.NET 5”. Try explaining that to a non technical person.

“A common convention in software is that new major version number of a platform indicates that software from earlier major versions may require changes, often quite significant, to function” is pretty easy for non-technical people to understand.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by mihaaly on Tuesday March 21, 2023 @07:21PM (#35254206)
Usually non-technical persons do not give a faint fart about 'major' 'version numbers'. Is it a thing or goes somewhere? Yet about 'platforms' and 'sofware conventions'.

Is it working or not? Usually that's what they care about.

So it was ok in the old system but now there is an improved super shiny trendy best superpower new one and the previous ok is not ok anymore? [puzzled faces]

Re:Understanding the .NET ecosystem: The evolution of .NET i... by dragonwriter on Tuesday March 21, 2023 @07:25PM (#35254263)
> Usually non-technical persons do not give a faint fart about ‘major’ ‘version numbers’.

This type of user is actually usually, IME, easier to explain it to:

“It’s a different platform and our software will not work without changes”. The less they “give a faint fart” about details, the easy it is to tell them the effects and have them accept and move on.

At most, you might occasionally need to invoke a car analogy: it’s like trying to use accessories designed for an older model year, when there has been a design change between model years – some things just don’t fit right anymore.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by edandersen on Tuesday March 21, 2023 @07:36PM (#35254398)
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.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by dragonwriter on Tuesday March 21, 2023 @07:41PM (#35254461)
No, 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 technies 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.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by edandersen on Tuesday March 21, 2023 @08:25PM (#35254911)
"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."

Re:Understanding the .NET ecosystem: The evolution of .NET i... by TeMPOraL on Tuesday March 21, 2023 @08:57PM (#35255198)
> 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.

Re:Understanding the .NET ecosystem: The evolution of .NET i... by dragonwriter on Tuesday March 21, 2023 @10:23PM (#35255969)
The first version of the PS3 had hardware PS2 emulation. I think this was removed in later versions.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by rjbwork on Tuesday March 21, 2023 @07:04PM (#35254006)
Why does a non technical person care what version of .NET an application is on?
Re:Understanding the .NET ecosystem: The evolution of .NET i... by sumedh on Tuesday March 21, 2023 @08:08PM (#35254725)
They are writing the cheques, so if you tell that person upgrading from 4 to 5 is very complicated, needs time and money they will probably think something is fishy.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by bmitc on Tuesday March 21, 2023 @07:18PM (#35254174)
But .NET 4.8.2 isn't the right name, is it? It's .NET Framework 4.8.2. .NET Standard 2.0 has also been around for six years now, so the upgrade path has been around for a while.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by edandersen on Tuesday March 21, 2023 @07:39PM (#35254428)
That's why I wrote it in quotation marks. .NET Framework was always shortened to .NET in the common office vernacular.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by SgtBastard on Tuesday March 21, 2023 @08:29PM (#35254953)
So maybe be accurate when asking someone to write cheques then?
Re:Understanding the .NET ecosystem: The evolution of .NET i... by bearzdev on Tuesday March 21, 2023 @08:18PM (#35254826)
dotnet upgrade assistant or dotnet try-convert can help with that.

- dotnet try-convert: https://github.com/dotnet/try-convert

- dotnet upgrade assistant: https://dotnet.microsoft.com/en-us/platform/upgrade-assistan...

Re:Understanding the .NET ecosystem: The evolution of .NET i... by osigurdson on Tuesday March 21, 2023 @08:20PM (#35254846)
>> Try explaining that to a non technical person

Why would a non-technical person care?