|
|
|
|
|
|
by kaelinl
1096 days ago
|
|
|
"In-editor chat" is mentioned as an example (the only example in the post, as far as I can tell) of a restricted API feature. Since the post insinuates that the restricted APIs are done out of malice/with anticompetitive intent, I think we'd need to see an example of the vscode devs being asked for access to this "in-editor chat" API and know how they reply. Is there an example of this? Otherwise, it seems to me that assigning malice isn't justified. It's surely a fast-moving/evolving feature which was added recently, and stabilizing the API for general use means they have to support it in that form ad infinitum. Sure, it would be ideal if they committed to that from the beginning, but I can understand the schedule pressure and priorities. |
|
|