Hacker News Reader

Comment by anonymous908213 | Hacker News Reader

This should be called Python Type Server Protocol, no? Seems weird to mine the generic protocol namespace for a protocol that only supports Python. Especially coming from the company behind LSP, which actually is generic.

View on HN

Type Server Subsystem for Python

Copilot+ Type Server Subsystem for Python Series S

Copilot+ Type Server Subsystem for Python Series S .NET

…Server 2027.

...Subscription Edition

...365

.PYTHON

For Teams

… Home Edition

SP3

MAX PRO

Language Server Protocol Server Subsystem for Type Server Protocol Servers for Python

... for Workgroups

Python Server Subsytem Typing - PSST

It is namespaced under the pylance project. I also don't see any announcement here, just a markdown file.

Perhaps the post title could use a tweak

This was the announcement https://devblogs.microsoft.com/python/announcing-tsp/

This is the company that named its web framework "MVC". At least this time they're not eternally polluting search results for an industry standard term.

I've usually heard it called "ASP.NET MVC" except when the former part was clear from context.

MVC is still a general way of structuring code. Would it be the only way a MVC framework could or should be implemented for ASP.NET?

That's an argument against any descriptive name at all.

Not any descriptive name at all, but any name only partially descriptive, where the omitted information leads to confusion.

The fully descriptive name should be "MS implementation of the MVC pattern for the ASP.NET framework".

100% - it would make more sense if they also supported elixir or other dynamic languages

I do wonder if it generalizes outside of python similar to how LSPs do.

So now I need a TSP AND an LSP eating loads of memory?

Reply on news.ycombinator.com