←back to thread

224 points cspags | 1 comments | | HN request time: 0s | source
Show context
jedbrooke ◴[] No.46178725[source]
> Consumer electronics naming is very simple. Make a good product with a simple name. “iPhone”, “comma”, “Z Fold”. Then every year or two, add one to the number of that product. If it’s a small refresh, you can add a letter after the number. “2 3 3X 4” “4 4s 5 5s 6 …” “2 3 4 5 6 7” Why is this so hard for companies like HP?

Oh man I feel this every time there’s a games console launch. I still have no idea what the latest Xbox is called but Sony gets it right with “Playstation <N>”

Apple loses some points here since every macbook from like 2007 until 2020 was just called “Macbook pro” with no year officially in the name so you have to be really careful when eg looking at used listings for macbooks. But since the M1 it’s been good with M<1-5>

replies(13): >>46178779 #>>46179366 #>>46179994 #>>46180113 #>>46180522 #>>46181272 #>>46181366 #>>46181858 #>>46182298 #>>46182443 #>>46182531 #>>46183580 #>>46193674 #
pjmlp ◴[] No.46179994[source]
What to expect, when Microsoft decides to do stupid things like renaming .NET Core into .NET 5, thus everyone that doesn't pay attention to Microsoft world keeps thinking .NET is Windows only, as the .NET Framework was always known as plain .NET in most circles.
replies(2): >>46181325 #>>46192003 #
ThunderSizzle ◴[] No.46181325[source]
I can't tell you how many people are confused that (1) Microsoft dropped "Core" from .NET 5+, and that .NET 4.8 and .NET 8 are not the same thing.

Microsoft jumped from .NET Core 3 to .Net (Core) 5 to avoid people conflating .NET Core 4 with .NET Framework 4.

Now tech adjacent people in my world, including people from Microsoft, think .NET Core 8 and .NET Framrwork 4.8 refer to the same version.

Luckily that problem will go away as we do our now biannual ritual of upgrading .NET versions, frustratingly.

replies(1): >>46181430 #
1. pjmlp ◴[] No.46181430{3}[source]
Easy, do you want links to podcast interviews from .NET team members where they mention this still being an issue with .NET adoption outside traditional Microsoft shops.

For example, see Mandy Mantiquila interview with Nick Chapsas, if I remember correctly it is one of them.