PSA:

the notation `user@address` originated with unix filesystem protocols and remaps to whatever the `passwd` file says the `user` has as their `home folder` - typically `/home/user`

it is always, and has always been a shorthand representation to indicate a remapping to a filesystem path

furthermore

Git is a FILESYSTEM protocol, it defines a filesystem structure for storing a tree structured graph of changes to a filesystem, including branches, commits (specific states) and any "git path" has to be REMAPPED to a filesystem path in some way

and originally, HTTP was Hyper Text Transfer Protocol, and the first HTTP servers were just serving up static files and it was also using the same fucking convention, where if there was a `user@address/path` like with scp this `user` has a specific path resolution that goes before the path part

the kids these days don't understand these fundamentals of computer address encodings being tied to filesystem paths, it's mind blowing to me but i was using unix when the technology was barely 15 years old, and they invented http routers and idk still how it's not understood when the only easy way to do Git commits is using a FUCKING SSH path that looks like, you know, this: `user@address:/path.git` really, are you not actually reading the words on your screen?

i totally want to scream at how retarded the kids are these days

corporate culture has completely detached computer software developers from the roots of the operating system's architecture

kids nowadays use graphic frontends to git that hide most of whats happening.

Probably most people just use github tools directly from browser or some kind of bloated fancy client.

Reply to this note

Please Login to reply.

Discussion

which means they aren't even vaguely qualified to do the job