points by anonymous908213 3 days ago | 0 comments
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.
[–] wolttam 3 days ago
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
[–] adamnemecek 3 days ago
This was the announcement https://devblogs.microsoft.com/python/announcing-tsp/
[–] roarcher 3 days ago
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.
[–] ameliaquining 3 days ago
I've usually heard it called "ASP.NET MVC" except when the former part was clear from context.
[–] ta2345fa59be 2 days ago
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?
[–] ameliaquining 2 days ago
That's an argument against any descriptive name at all.
[–] ta2345fa59be 1 day ago
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".
[–] Blackarea 3 days ago
100% - it would make more sense if they also supported elixir or other dynamic languages
[–] pantsforbirds 3 days ago
I do wonder if it generalizes outside of python similar to how LSPs do.
[–] fnord123 3 days ago
So now I need a TSP AND an LSP eating loads of memory?
[–] rzzzt 3 days ago
[–] cobolexpert 3 days ago
[–] Waterluvian 3 days ago
[–] kstrauser 3 days ago
[–] nazgulsenpai 3 days ago
[–] keitmo 3 days ago
[–] wseqyrku 3 days ago
[–] zemo 3 days ago
[–] warkdarrior 3 days ago
[–] awesome_dude 3 days ago