undefined | Better HN

0 pointsgiancarlostoro1y ago0 comments

My only complaint about VS Code is the naming. I'll be googling for actual Visual Studio (2021, 2019, 2015, etc) specific things, and find myself with VS Code specific results all the time. I wish Microsoft would have given it a better more SEO friendly name, they didn't learn from naming SQL Server I suppose.

Go has the same problem, which annoys me, a search engine company didn't think that one through.

Please, major corporations, give better names to your products that are unique enough to dominate search results. Invent new words for all I care.

0 comments

SketchySeaBeast1y ago

I agree that's frustrating, but I doubt Microsoft will be able to ever outdo itself with its .NET Framework/.NET Core/.NET naming convention nonsense.

giancarlostoroOP1y ago

.NET 7 and beyond consolidates Framework and Core. I think they're going to just stick to just .NET moving forward. Eventually Framework and Core will be EOL'd.

I do agree though, they did it very confusingly.

SketchySeaBeast1y ago

It's definitely better sorted now, but as a dev working in the .Net stack during the .Net 2.0 Core time, it was very confusing.

1 more reply

RexM1y ago

Don’t forget .NET Standard.

Their naming for all of this is a disaster.

giancarlostoroOP1y ago

Standard was supposed to be the in-between for Framework and Core if I'm not mistaken, that will likely be phased out and EOL'd.

alexvitkov1y ago

Adding "-vscode" or "vs2019" to the query usually does it for me. With go I pretty much always search "golang".

j / k navigate · click thread line to collapse

0 pointsgiancarlostoro1y ago0 comments

Go has the same problem, which annoys me, a search engine company didn't think that one through.

Please, major corporations, give better names to your products that are unique enough to dominate search results. Invent new words for all I care.

0 comments

SketchySeaBeast1y ago

I agree that's frustrating, but I doubt Microsoft will be able to ever outdo itself with its .NET Framework/.NET Core/.NET naming convention nonsense.

giancarlostoroOP1y ago

.NET 7 and beyond consolidates Framework and Core. I think they're going to just stick to just .NET moving forward. Eventually Framework and Core will be EOL'd.

I do agree though, they did it very confusingly.

SketchySeaBeast1y ago

It's definitely better sorted now, but as a dev working in the .Net stack during the .Net 2.0 Core time, it was very confusing.

1 more reply

RexM1y ago

Don’t forget .NET Standard.

Their naming for all of this is a disaster.

giancarlostoroOP1y ago

Standard was supposed to be the in-between for Framework and Core if I'm not mistaken, that will likely be phased out and EOL'd.

alexvitkov1y ago

Adding "-vscode" or "vs2019" to the query usually does it for me. With go I pretty much always search "golang".

j / k navigate · click thread line to collapse