Re:We're Leaving Kubernetes
by xcrunner529 on Monday November 04, 2024 @07:55PM
(#42047668)
I am hardly a dev but occasionally have had to do some or some scripting or web stuff and have really loved VSCode and using the remote SSH support to basically feel like I’m coding locally. Does that not work for your devs?
[ Parent
| on HN ]
That puts a "scary" VSCode blob on the remote-server. Some orgs do not like that, even if it's a "work" class box.
UNIX, and other competing timesharing systems of the time, have always been remote first, with Windows catching up with Citrix, followed by RDP, and nowadays finally headless as well.
Nowadays Web frontends and SSH/cloud shell, have replaced what used to be X Windows / telnet / rsh, but the underlying workflows aren't much different than running an IDE / emacs /vi / joe /... from a UNIX development server in a 1990's office.
Re:We're Leaving Kubernetes
by 0xbadcafebee on Tuesday November 05, 2024 @03:34AM
(#42049713)
The funniest (?) thing to me about all this: we're still hoping, if we do things right, to replicate the technology (terminals) from 50 years ago.
I honestly don't understand why nobody has simply invented some software to solve this problem, after 50 years.
Add to it the whole TUI fashion, as if we weren't doing them already 50 years ago.
We did, it is called GUI and language REPLs, like Smalltalk and Interlisp-D development enviroments, with graphical based terminals, not dependent on replicating virtual teletypes.
Still something that seems problematic to take off the way it should.