And more importantly would you use it @ZacckOsiemo ?
And more importantly would you use it @ZacckOsiemo ?
ZThe REPL, yeah I can consider it. If DevHeads had some hardware I could ssh into and test with while watching logs and a video of an LED
ZThe thing that is odd here is that our development involves hardware so we have to find a way of tying it in
TEmulator?
PIt sounds like a great idea. Having a built-in code editor alongside a video tutorial or during live developer sessions would definitely be useful
Zno real hardware
PI think it’s possible, depending on how integrated Embeetle wants to make the experience
Twell wtf
ZSo sometimes I have hardware than @32bitSaviour doesn't have what I will do is open a vs live code session and connect my hardware to it. He will connect and run some code on it and I'll either watch the hardware or I can point my camera at it.
Tthat's great but what if there are 50 people in the session
Zit's not that hard its basically VPS based development. If you are old enough to have writtren php on your server from an ssh you have done this
Zits how your website works man
Zthis is a problem fixed by @Ming 's generation
TThat's not what i'm saying
ZOk please explain
TWhat i'm saying is if we have 50 people trying to connect to the hardware
Zwe can time slice or do priviledge based, then it becomes a sharing issue.
ZLike 00:50 till you have a chance to run your snippet
Tcorrect. that usually isn't conducive to 60 minutes, though i know how much umesh loves the camera time
Ttoo complex; bad ux
Zwell if they are observing
Thmm
Tso, barring the wild security issues here, if the connection remains open for like, two days, you could have people reserve time. basically classic terminal.
Tuntil someone bricks it
ZGitHub
Is the five guest limit in place for technical reasons, or is it something that can be increased? I tried using it for a class that I'm running, and was disappointed that most people couldn'...
Zso seems vs live code is set to 30
Zexactly
ZBut this is active participants, not observing participants
Zin theory that upper limit is unreachable
Twhat's the hw target here i can't tell
Tit's just vs code
Ti thought we were talking about deploying code... at least in your 32-bit savior example
Zyes if he can type on my ide and my stm32 is conneceted
Zhe can deploy
Zhe has access to the toolbar and the cli sections and thats what he needs to deploy
TOkay, then. What about:
- Security issue
- Device bricking
TI bet @Ming has some useful experience to contribute here
ZSecurity I suspect its a walled garden thing, the subject machine will just be used to for this purpose and will persist nothing
TYes, will have to be sandboxed; same thing with the safety of the platform. I just worry we end up partitioning out the utility of it
ZDevice Bricking might be more difficult maybe we do a userland / kernel type separarion
Zlikely not
T@Umesh Lokhande do you see this being useful
Zbecause the ideal person wants to try this and if it sort of works they want to go back to their IDE and keep on going
Texcept for the fact they probably don't have the hardware... which is the point
ZThat's true, lots of moving parts. However all this is possible.
TMaybe distributor friends would be willing to lend a discount. Everyone who wanted to do it though would probably have to be a pro and provide info
Tbut, it could work
TWho would manage this infrastructure on DH side? @ZacckOsiemo? @Phoenix?
TWhat do we need to support this at high rel
Pwe could manage it, For high reliability, we’d need a sacalable cloud infrastructure to handle increased traffic during live coding sessions. AWS or DigitalOcean could be used for this.
PLoad balancing and redundancy to ensure minimal downtime and consistent performance.
