[2026-04-22 11:05 PM][VSCODE SIDEBAR: MIDGARDR MUSIC PLAYER]
// Hell yea... any vscode devs around? haha
// The music player is getting an update... this is solving... a first world problem for ssuuurree... well and its a ME problem since no one else has into this issue within vscode really. The issue: When I'm coding, typically I always have atleast 2-3 workspaces open if not more, and I always have music playing in... one of them. Right now, if we want to change tracks, folders or whatever... we have to go and play wheres waldo with the music player and track it down so that we can get to the original player that is currently playing the tracks... I don't feel like doing that anymore... I've been doing it for several weeks now... and you know, I'm kinda tired of it tbh... and were kinda on a roll here with taking what microsoft tells what we can and cannot do and were sticking our fingers in our ears and humming.
// Jokes aside, the update now makes it so ALL MUSIC PLAYERS across ANY NUMBER OF INSTANCES are available to us to stop, skip, back, change folders, repeat, repeat single, volume, shuffle... whatever, you get the point. Do whatever you need to do, in whatever instance as it no longer matter what instance it was exactly that you started playing music in.
// In addition to that, whenever you open a new workspance/instance the UI will reflect the current track playing, displaying its name, time, volume, along with the ui doing its thing whenever tracks are playing
// Thus the music player will communicate across all instances despite living entirely in a webivew... I wonder if we can cross app comms going since WORKSPACE-LEVEL APPLICATION VIRTUALIZATION-ISH dropped... which allows us to use vscode and vscode-insiders at the same time, with different extensions configs, by controlling the entire instances ui and extensions state progmatically from either version with just a click of a button...
// hold my BEER... If that happens I'll follow up with an update
Location -> DEVSTACK
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)