4 ms·

As a dev this is exactly what I would expect and want out of such service. The alternative is that I have all this crap on my machine. Having it on a remote VM

As a dev this is exactly what I would expect and want out of such service. The alternative is that I have all this crap on my machine. Having it on a remote VM is so much better : - my device isn't crippled - a lot of potential security issues are now not my problem - environment setup is dealt with by someone else - I can code on a potato as long as it can render the screens I need I can have what you're describing with a standard VM instance and SSH port open (or my home desktop and cloud flare tunnel)

madmulita 3y ago
Until they decide this remote machine can only be accessed from properly secured devices...
- wildrhythms 3y ago
  I get the feeling that the enterprise environments targeted by this product are already restricting access in this way.
- dagw 3y ago
  This is already standard. I've worked at several places which had hardware white lists on the VPN and only company controlled and secured hardware could connect. Working on your own hardware was strictly forbidden.
candiodari 3y ago
I don't understand. We all know corporate IT, and how this plays out in reality. 1) my device isn't crippled WHY would you assume they're not going to cripple your device? In the past they made it worse. One product that had exactly this purpose was "Sun Ray" machines. They weren't just crippled in software, they were utterly crippled in hardware. You see the problem with crippled hardware ... is that it's not really much cheaper than non-crippled hardware, but years behind. A bad chromebook is actually a pretty good crippled computer. So you get the worst of everything a) very slow processor (that actually costs more than a decent one) b) too low amount of memory (that actually costs more than a sufficient amount of memory) c) no local access whatsoever. So checking what ip address the thin client got ... not possible. d) a low-res horrible headache-inducing screen. And forget about multi-monitor or anything like that. 2) a lot of potential security issues are now not my problem Yeah because if there's one thing other departments in companies easily and quickly do it's accept responsibility for problems ... 3) environment setup is dealt with by someone else Seriously ... why would they do this. 4) I can code on a potato as long as it can render the screens I need You can't. You can only code on their potate. The one with spikes that leaks the suspicious black liquid and can't be replaced. Not because it isn't easy to replace, but because the problem is IT, not the technology. At university they tried to introduce Sun Rays for us. The main thing I remember was the horrible monitor ... and when I brought my own full hd monitor from home, it crashed. Eventually I found out why: the thin client had so little memory the higher resolution made the framebuffer not fit in memory.

madmulita 3y ago

Until they decide this remote machine can only be accessed from properly secured devices...

wildrhythms 3y ago
I get the feeling that the enterprise environments targeted by this product are already restricting access in this way.
dagw 3y ago
This is already standard. I've worked at several places which had hardware white lists on the VPN and only company controlled and secured hardware could connect. Working on your own hardware was strictly forbidden.

candiodari 3y ago

I don't understand. We all know corporate IT, and how this plays out in reality. 1) my device isn't crippled WHY would you assume they're not going to cripple your device? In the past they made it worse. One product that had exactly this purpose was "Sun Ray" machines. They weren't just crippled in software, they were utterly crippled in hardware. You see the problem with crippled hardware ... is that it's not really much cheaper than non-crippled hardware, but years behind. A bad chromebook is actually a pretty good crippled computer. So you get the worst of everything a) very slow processor (that actually costs more than a decent one) b) too low amount of memory (that actually costs more than a sufficient amount of memory) c) no local access whatsoever. So checking what ip address the thin client got ... not possible. d) a low-res horrible headache-inducing screen. And forget about multi-monitor or anything like that. 2) a lot of potential security issues are now not my problem Yeah because if there's one thing other departments in companies easily and quickly do it's accept responsibility for problems ... 3) environment setup is dealt with by someone else Seriously ... why would they do this. 4) I can code on a potato as long as it can render the screens I need You can't. You can only code on their potate. The one with spikes that leaks the suspicious black liquid and can't be replaced. Not because it isn't easy to replace, but because the problem is IT, not the technology. At university they tried to introduce Sun Rays for us. The main thing I remember was the horrible monitor ... and when I brought my own full hd monitor from home, it crashed. Eventually I found out why: the thin client had so little memory the higher resolution made the framebuffer not fit in memory.