Funny enough, that right there is the actual fundamental problem here.

I am reminded of a post or blog long ago that talked about programmable thermostats and how awful they are for most people to use despite how powerfully in the weeds one can get with them. Basically summarizing the issue as something like “People do not want to learn your arcane system, they just want the benefit it’s advertising”. A good UI knows how to minimize that gap.

The poster child of this is the Microsoft Office ribbon.

I want to set the temp. Maybe set a schedule and a timer. Once I have to start navigating multiple, deep menues with a thermostat I stop giving a shit.

I miss old VCRs that had 8 buttons and only those 8 functions

Some ideas like using viewing a linux dir over _ssh_ using native UI components.. seem cool.

I do agree, some of these do seem like they have already been solved in other ways (like an sshfs mount).

p9 was done when "current state of unix" was already fixed in form of aix, sysv and bsds, it suffered the same fate as say beos.

but unix got widely adopted and you go with what sells not blue-sky woulda-coulda

Almost all dev facing machines have ssh server installed and accessible.

Why ssh terminal has to look like character-only trash from 1960s? Why a TUI is the best thing we pipe through ssh? Why I cannot watch a 4k movie in the terminal or browse the web using pinch to zoom ?

`ssh -XC` (look up SSH X forwarding). You can also easily tunnel remote desktop over ssh.

> Why I cannot watch a 4k movie in the terminal or browse the web using pinch to zoom ?

Kitty, sixel, and iterm2

I do agree that new Linux users who have different needs from their computers might cause some incentive to change some of these 40 year old UX decisions. We don't really have a modern, capable remote desktop solution at least on par with RDP.

You take that back!

>Why a TUI is the best thing we pipe through ssh? Why I cannot watch a 4k movie in the terminal or browse the web using pinch to zoom?

The old magick speak of X forwarding. The newer wizards now use waypipe.

We should re-implement it with Comic Sans and happy shiny buttons to click everywhere? Click here for "ls -alh" ?

you want your GUI then set up VNC

People that don't understand the separation between content and form cannot separate between data and rendering, between models and views. They stuff JS in CSS and CSS in databases.

In short, they make shitty architects and are to be shunned from programming important software in general. No offense.

evil grin

puttygen.com looks super fishy, the disclaimer:

> Puttygen software is not created, nor supported by Puttygen.com. The program has been tested and is believed to be safe. [...] The use of Puttygen through Puttygen.com is done at your own discretion and risk

Edit: or is that the evil grin?

I still don't follow the evil grin. Is the apt package some kind of malware or trojan?

I know companies running on SVN and they're fine. In fact, it's a better fit for them. Yes, Git is not always superior.

I'll give you a helpful concept to navigate these issues: "Cargo culting refers to the practice of imitating the superficial aspects of a process or practice without understanding the underlying logic or reasons behind it. This phenomenon is often seen in software development, where developers may adopt certain coding styles or methodologies without grasping their true purpose."

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 there are use cases where SVN is superior (I can't come up with any but they may exist), and maybe engineers in that industry really are so specialized that they never get around to working on anything else!

But maybe it's because nobody else is willing to hire them.

Many people are not familiar with "git" and don't have to be. Picking up "git" is a one afternoon type of thing but the parent did not mention timelines. It was just about "knowing" git and I pushed back on that.

There are so, so many tools you guys on here find indispensable that don't actually get used by vast swaths of people in the field. I sometimes wonder where all you guys work.

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…

Then I don't apply. I'm not interested in working with garbage tech.

Postgres is decent for a free ($$$) database, although it's lack of clustered indexes and in-place updates (its MVCC approach) sucks for many use cases. I find it a sensible default but not the best at any one use case.

Python, frankly, sucks nowawadays. Maybe it had its time, but there are so many better lingos now. It's got type hints that are ignored, really bad patterns ("dependency injection" that's really just the singleton pattern, FastAPI encourages you to open a db connection and a transaction at the front of every request and commit at the end while you're making other requests, writing to disk, etc), and it's slow in both user experience and runtime (no real parallelism).

But generally I have to make some trades to get a great job. I love Go, personally, and the incredible simplicity it encourages.

Seriously, if you'd be willing to share, I'd love to hear what you do!

Hope this helps.

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?

http://gitHub.com/fragmede.keys, for example. Stick that in authorized_keys to let me into your server.

    - microsoft is evil, I cannot delete my github account, will never use anything by this company
    - if the attacker knows your *public* key they can enumerate the list of the servers you have access to https://github.com/benjojo/ssh-key-confirmer

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.

I don't think that's remotely controversial

I need something like this for network management tools.

Or did you mean it in another way?