You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
At this point in time developing multiple micro-services for a scalable kubernetes deployment is common.
This often involves something like this:
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.
The text was updated successfully, but these errors were encountered: