Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add tab groups like chrome/edge has, needed for developing micro-services #240830

Closed
lknite opened this issue Feb 14, 2025 · 1 comment
Closed

Comments

@lknite
Copy link

lknite commented Feb 14, 2025

At this point in time developing multiple micro-services for a scalable kubernetes deployment is common.

This often involves something like this:

  • a rest api which can scale to multiple replicas
  • the rest api sends a message to a message queue using something like NATS
  • a message queue listener which can scale to multiple replicas
  • the listener watches for a message, performs work, and then sends a reply back

When developing this sort of micro-services based architecture, which I'd say has become the norm, it is normal to jump between the micro-services projects. Implementing a new api in one project then jumping over to the microservice which is going to listen for it, jumping back and forth between different microservices all the time.

In the past I'd have loaded up the separate projects in separate instances if visual studio, and that's still possible. But, this was before the idea of tab groups was introduced via chrome/edge, which is a better solution.

With tab groups, the problem is solved. I find myself looking for multi-row plugins, such as what firefox used to have, and tab group plugins, looking for what chrome/edge offers. The tab-group plugins are not what chrome/edge has but seemingly hacked-solutions which really aren't that helpful, which use a separate menu at the side (if this was the better approach surely chrome/edge would use it by default). So far running multiple instances of vs code is the answer, but tab groups would be much much better. This is enough that today I found myself looking for a new editor solution.

Let's bring vs code up-to-speed with the new standard of tab groups as a standard feature available in the same way the most popular browsers on the planet do it with a right-click create tab group, and the dragging/dropping of tabs into and out of tab groups.

Image

@lknite
Copy link
Author

lknite commented Feb 14, 2025

/duplicate of #100335

@lknite lknite closed this as completed Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant