With most of what we do, we should be able to run in a browser. We have to make some changes where we access the file system but that was only for debugging purposes.
We need to find an alternate way of putting debug info and we can make sure that this extension can work on the desktop or in a browser. We have proof of this with the svd-viewer. Also, the debug-tracker is also browser friendly now.
What I am trying to do overall can also help people using containers.
AFAIK, only one debugger (Keil/ARM) partially works in the browser/CodeSpaces because they are built to use DAPLink and WebUSB. Cortex-debug will have challenges abound as we don't have the luxury of WebUSB or our own probe. We launch gdb-servers and create so many local TCP ports, and none of that is secure....YET :-)
Your thoughts please:
Does anyone see any value in running in the browser? Currently, debug (partially) works in Github Codespaces (vscode.dev disables all debug functionality).
And, btw, Github Codespaces can become expensive (depending on your point of view). Even a minimum config. is USD$0.36 per hour. and total idle time also counts as billable. I got billed for 20 hours (first 120 are free) and I don't think I was actively using it for more than four. What company would deploy such a thing to their employees? Even as a hobbyist, it doesn't make sense to me. Also, it is very clunky, constantly reloading the container when you step away. Many limitations. Maybe I am too old.
With most of what we do, we should be able to run in a browser. We have to make some changes where we access the file system but that was only for debugging purposes.
We need to find an alternate way of putting debug info and we can make sure that this extension can work on the desktop or in a browser. We have proof of this with the svd-viewer. Also, the debug-tracker is also browser friendly now.
What I am trying to do overall can also help people using containers.
AFAIK, only one debugger (Keil/ARM) partially works in the browser/CodeSpaces because they are built to use DAPLink and WebUSB. Cortex-debug will have challenges abound as we don't have the luxury of WebUSB or our own probe. We launch gdb-servers and create so many local TCP ports, and none of that is secure....YET :-)
Your thoughts please: Does anyone see any value in running in the browser? Currently, debug (partially) works in Github Codespaces (vscode.dev disables all debug functionality).
And, btw, Github Codespaces can become expensive (depending on your point of view). Even a minimum config. is USD$0.36 per hour. and total idle time also counts as billable. I got billed for 20 hours (first 120 are free) and I don't think I was actively using it for more than four. What company would deploy such a thing to their employees? Even as a hobbyist, it doesn't make sense to me. Also, it is very clunky, constantly reloading the container when you step away. Many limitations. Maybe I am too old.