We're Leaving Kubernetes

Re:We're Leaving Kubernetes by hosh on Monday November 04, 2024 @01:26PM (#42044533)

I have used remote dev machines just fine, but my workflow vastly differs from many of my coworkers: terminal-only spacemacs + tmux + mosh. I have a lot of CLI and TUI tools, and I do not use VScode at all. The main GUI app I run is a browser, and that runs locally.

I have worked on developing VMs for other developers that rely on a local IDE such. The main sticking point is syncing and schlepping source code (something my setup avoids because the source code and editor is on the remote machine). I have tried a number of approaches, and I sympathize with the article author. So, in response to "Devs need to create the software tooling to make remote dev less painful. I mean, they're devs... making software is kind of their whole thing." <-- syncing and schlepping source code is by no means a solved problem.

I can also say that, my spacemacs config is very vanilla. Like my phone, I don't want to be messing with it when I want to code. Writing tooling for my editor environment is a sideshow for the work I am trying to finish.

[ Parent | on HN ]

Re:We're Leaving Kubernetes by pjmlp on Monday November 04, 2024 @05:56PM (#42046930)

Me as well, specially in the days that there was only a UNIX dev server for everyone.

It was never an issue to use X Windows on them, with hummingbird on my Windows thin client.

I guess a new generation has to learn the ways of timesharing development.

[ Parent | on HN ]

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 ]

Re:We're Leaving Kubernetes by djbusby on Monday November 04, 2024 @11:36PM (#42048642)

That puts a "scary" VSCode blob on the remote-server. Some orgs do not like that, even if it's a "work" class box.

[ Parent | on HN ]

Re:We're Leaving Kubernetes by pjmlp on Tuesday November 05, 2024 @03:03AM (#42049550)

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

Re:We're Leaving Kubernetes by pjmlp on Tuesday November 05, 2024 @04:14AM (#42049926)

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.

[ Parent | on HN ]