Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A native graphical shell for SSH

probablymarcus.com

Post reply on HN
Print view View original

221–230 of 239 posts

Re: A native graphical shell for SSH

#221

Post by schrodinger »

sdfsdfs34dfsdf wrote: post #193
hiimkeks wrote: post #175

Earlier quoted context omitted.

Git is over 20 years old at this point. If somebody is in their 60s now, they were in their 40s when it came out. This is not about age. They must have slept on it for a long time. Nobody expects an engineer to be a git expert, but if a senior software engineer has heard of git only yesterday or don't have a vague concept of how DVCSs like hg or git work (DAG of commits), then something has gone very wrong. Maybe the…

If you are not in an environment where it is being actively used it is not something you'll pick up. Not every programmer is on HN or being cool with blogs etc. I agree not knowing about source control at all is a .. different matter. Also, 20 years is less impressive once you subtract the time it wasn't popular. Even if it was 20 years, it is still not impressive. Perhaps if you are 15-30, but to older folks it's li…

If you're actively looking for a job, you should have some familiarity with the common dev stack when you're looking. Today you should be comfortable working on a Mac, know Bash / Zsh, a little bit of Vim for SSHing, git, docker, react, postgres, etc.

If you don't, spend a few weeks before you start your search. You're almost definitely going to need them. Unless you're in a niche where the common stack is different.

This isn't me gatekeeping or something, it's just common sense. When 80% of the jobs are Python + Javascript / Typescript, running in Docker, using Postgres, using React on the frontend, FastAPI on the backend, and git plus github for deploying and reviewing, you're going to stumble without cursory knowledge. You don't need to be an expert in it all…

Re: A native graphical shell for SSH

#223

Post by nibbula »

Is this really the future that people want?

https://raw.githubusercontent.com/outergroup/outershell/refs...

https://raw.githubusercontent.com/outergroup/Top/refs/heads/...

I am surprised at the lack of technical criticism. In the past, even an ignorance of history could be useful, since one would have to solve again the problems in detail, and so be forced to acquire a deep understanding of the issues. Now one can sell this paper clock with chaotic internal workings that thwarts human fabrication or maintenance.

Re: A native graphical shell for SSH

#224

Post by jcelerier »

tway235 wrote: post #141
jcelerier wrote: post #127

Earlier quoted context omitted.

> there's at least one customer in need for a product just because whales exist does not mean feeding them is a goal to aim for as a society. 99.9% of technology could disappear tomorrow and life would become better.

hyperbole: a lot of tech we give for granted today, started as niche products for "whales" like government agencies, so I suppose computers and Internet shouldn't exist and life would be better

> computers and Internet shouldn't exist and life would be better

I don't think that's remotely controversial

Re: A native graphical shell for SSH

#226

Post by XorNot »

rrvsh wrote: post #183
XorNot wrote: post #93

Earlier quoted context omitted.

Windows has quite a lot of remote admin tools that work pretty transparently over the network though. The issue is that they're historically never turned on or heavily restricted. Where the user is involved though RDP is a world class remote desktop never exceeded by Linux anywhere. If someone wants to impress me, point Claude at Wayland and get it so I can seamlessly open remote RDP from somewhere else, lock the loc…

Yeah, RDP is great. Sunshine has basically solved this problem for me on Linux, even with {way,hypr}land (haven't tried on macos yet)

Had a look and the "locked local session" problem is still not solved. The gui would be unlocked and visible on the host the whole time.

Re: A native graphical shell for SSH

#227

Post by CrimsonCape »

zamadatix wrote: post #111
guhcampos wrote: post #82

Earlier quoted context omitted.

I get it, but if the author of the article uses a biased and loaded language, I think it's fair game to do the same in the comments.

I don't think I've met many pairs of people I could ask "on a scale of 1 to 10, how biased/loaded do you think ${example} is" and get told the same exact number by both for the majority of the examples given. Now apply that to the n people reading a given post or comment! If those commenters try to communicate on what they think is "fair game" for the given conversation, then two comments deep in and you might alread…

This article felt like a classic example of "I just discovered this cool technology that seems to have massive potential! While massively blind and naive to the implications of what I think!" As others point out, the OP will learn in 5 years why people do what they do and not what OP thinks should be.

So I find myself being more sympathetic and SMH than antagonistic..

Re: A native graphical shell for SSH

#228

Post by rrvsh »

XorNot wrote: post #226
rrvsh wrote: post #183

Earlier quoted context omitted.

Yeah, RDP is great. Sunshine has basically solved this problem for me on Linux, even with {way,hypr}land (haven't tried on macos yet)

Had a look and the "locked local session" problem is still not solved. The gui would be unlocked and visible on the host the whole time.

Do you mean the local session would be locked while you work unlocked from remote? That should be doable with a separate session using a dummy HDMI plug, but your original comment read to me as being able to remote in and lock the session, which is 100% possible with Sunshine

Re: A native graphical shell for SSH

#229

Post by analog_daddy »

sdfsdfs34dfsdf wrote: post #193
hiimkeks wrote: post #175

Earlier quoted context omitted.

Git is over 20 years old at this point. If somebody is in their 60s now, they were in their 40s when it came out. This is not about age. They must have slept on it for a long time. Nobody expects an engineer to be a git expert, but if a senior software engineer has heard of git only yesterday or don't have a vague concept of how DVCSs like hg or git work (DAG of commits), then something has gone very wrong. Maybe the…

If you are not in an environment where it is being actively used it is not something you'll pick up. Not every programmer is on HN or being cool with blogs etc. I agree not knowing about source control at all is a .. different matter. Also, 20 years is less impressive once you subtract the time it wasn't popular. Even if it was 20 years, it is still not impressive. Perhaps if you are 15-30, but to older folks it's li…

Fair enough that I did not mention any timeline. And could’ve been general with “VCS”. And you are absolutely correct, that basics of some of these tools can be learnt in an afternoon.

In fact the industry i work in we don’t have git, but something similar to SVN (and proprietary, expensive and pathetic UI/UX)

Since, I am not in software industry, I won’t comment on whether such people might survive for more than 5 years without knowing about ‘VCS’.

However, I have slightly died inside when some Computer science students (graduate school, mind you) were using google drive with manually created timestamps as a backup strategy. The submission for this entire semester long actual project was on Github. as a final single commit uploaded a day before. (And no this wasn’t a squashed commit from a different repo.)

There might be a blurry line between people not sharpening their auxiliary tools vs never using or being slightly curious about them.

I am more of a glamour and bling on my tools person, and I don’t expect every engineer to derive the same pleasure that I derive just from tinkering with them; however, does make me wonder if there is a point when such an approach to not fully caring about simplifying your workflow (aka being lazy), might spill over into making poor engineering decision?

Re: A native graphical shell for SSH

#230

Post by XorNot »

rrvsh wrote: post #228
XorNot wrote: post #226

Earlier quoted context omitted.

Had a look and the "locked local session" problem is still not solved. The gui would be unlocked and visible on the host the whole time.

Do you mean the local session would be locked while you work unlocked from remote? That should be doable with a separate session using a dummy HDMI plug, but your original comment read to me as being able to remote in and lock the session, which is 100% possible with Sunshine

Yes: the RDP experience is even if I just walk away, when I log in from somewhere else the local session is locked and inputs disabled.

Then if I walk back to that console and log in, I can go back to using it directly.

Near as I can tell no one's solved this for Sunshine.

Edit: I will say though there must be good reasons, it's never been clear to me why this is so hard particularly when you have Wayland just compositing to one big buffer in VRAM. Surely we just want to hand the local buffer back to GDM and let the remote stream have whatever we rendered?

Post reply on HN