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

Before GitHub

lucumr.pocoo.org

Post reply on HN
Print view View original

241–250 of 255 posts

Re: Before GitHub

#241

Post by 3form »

wredcoll wrote: post #231
echelon wrote: post #211

Earlier quoted context omitted.

GitHub was one of the first popular places to 1. not use query params for key entities in the URL 2. to stick user identifiers at the root path! totally unheard of to occupy such an important path at that point! Taken together, this was entirely novel. Next to nobody did this. Twitter was the one other notable example, and that's literally all I can think of. The URL bar was so different back then. It wasn't search b…

Reddit did it, linked in, most social media really, this is all just a throwback to /~user/ paths from apache and other early webservers. I think slashdot used the same convention.

Reddit doesn't have users at top level (point 2 of the parent post). This is I think a very distinctive factor, at least at that time.

Re: Before GitHub

#242

Post by ImPostingOnHN »

3form wrote: post #241
wredcoll wrote: post #231

Earlier quoted context omitted.

Reddit did it, linked in, most social media really, this is all just a throwback to /~user/ paths from apache and other early webservers. I think slashdot used the same convention.

Reddit doesn't have users at top level (point 2 of the parent post). This is I think a very distinctive factor, at least at that time.

Top level would be your name is the tld.

2nd level would be yourname.com.

3rd level would be yourname.site.com, like LiveJournal and Blogspot had a long time ago.

4th level would be site.com/yourname, like Myspace had a long time ago, and Facebook had after that, and Github had after that.

Once you sink all the way down to the obscure depths of 4th level, there's not much difference between site.com/yourname and site.com/whatever/yourname

Re: Before GitHub

#243

Post by saghm »

dijit wrote: post #169
saghm wrote: post #165

Earlier quoted context omitted.

I don't hate using Gitlab CI once it's set up; I just hate "put shell scripts in YAML to define how this should work". The least annoying experiences I've had with them are when every entry is literally just a single line that invokes an external script; shell scripting is already annoying enough without having to also spend the time to understand a YAML schema for what order they get invoked in and what environmenta…

Ah, super valid point. I use the command invocation to run python scripts. I tend to believe that CI is just a controlled way to do things you would do locally.

Somehow most teams I've worked on ended up with the worst of both worlds: lots of stuff in the CI yaml file and then still shelling out to a bash script at the end to run the tests. Neither the config or the script is enough to understand what's going on, and woe to anyone who tries to invoke the scripts locally with the assumption that the scripts don't implicitly depend on the extra scaffolding in the YAML.

Re: Before GitHub

#244

Post by echelon »

ImPostingOnHN wrote: post #242
3form wrote: post #241

Earlier quoted context omitted.

Reddit doesn't have users at top level (point 2 of the parent post). This is I think a very distinctive factor, at least at that time.

Top level would be your name is the tld. 2nd level would be yourname.com. 3rd level would be yourname.site.com, like LiveJournal and Blogspot had a long time ago. 4th level would be site.com/yourname, like Myspace had a long time ago, and Facebook had after that, and Github had after that. Once you sink all the way down to the obscure depths of 4th level, there's not much difference between site.com/yourname and site…

I said "root path".

Very few companies do this. Github and Twitter are some of the only ones. And they were certainly incredibly novel at the time.

Back in the 90's and 2000s, URLs looked disgusting. Remember this [1] nonsense?

[1] https://www.php.net/manual/en/session.idpassing.php (see "example 1")

Re: Before GitHub

#245

Post by ImPostingOnHN »

echelon wrote: post #244
ImPostingOnHN wrote: post #242

Earlier quoted context omitted.

Top level would be your name is the tld. 2nd level would be yourname.com. 3rd level would be yourname.site.com, like LiveJournal and Blogspot had a long time ago. 4th level would be site.com/yourname, like Myspace had a long time ago, and Facebook had after that, and Github had after that. Once you sink all the way down to the obscure depths of 4th level, there's not much difference between site.com/yourname and site…

I said "root path". Very few companies do this. Github and Twitter are some of the only ones. And they were certainly incredibly novel at the time. Back in the 90's and 2000s, URLs looked disgusting. Remember this [1] nonsense? [1] https://www.php.net/manual/en/session.idpassing.php (see "example 1")

> I said "root path".

That may be, but the user I responded to said "top level". Anyways, what looks disgusting about:

yourname.livejournal.com

yourname.blogspot.com

myspace.com/yourname

?

This was all before github, so objectively not novel by then.

Re: Before GitHub

#246

Post by alfg »

LtWorf wrote: post #118
alfg wrote: post #100

Earlier quoted context omitted.

Very strange take. A lot of software is built on trust and the people behind it. Hence why the social aspect of Github was so important to a lot of open source software.

I don't think it was important. It just came at a time when sourceforge was being heavily enshittified.

There were many other options for git and version control in general at the time, though. GitHub made the onboarding to git much easier while using the platform as a social tool.

Re: Before GitHub

#247

Post by pjmlp »

kelnos wrote: post #52

It's fun to read stuff like this and then reflect on the journeys of the projects I've been involved with. Most of my open source work has been done with self-hosted infra. My main example is Xfce: back when I started with them in 2004, we had a SVN server, using (I think) CVSweb's then-new SVN support for the web interface, and... maybe that was it? My memory is telling me that I set up Bugzilla at some point after…

Not only Github, the whole Microsoft Just like many others are actually dependent on IBM, Oracle, NVidia, Intel, AMD, Google,...

Which is understandable when only those provide paychecks, even if they could actually do much more given how much they use.

Re: Before GitHub

#248

Post by robertlagrant »

Izkata wrote: post #203
robertlagrant wrote: post #180

Earlier quoted context omitted.

It happened, but not as often as you'd think. In 2017 I was arguing with someone that the back button should work and URLs should be obvious in a fairly large project and they said "people are used to the back button not working - like a bank website".

Path parameters has nothing to do with history replacement breaking the back button, did you mean to respond to someone else?

That was the "URLs should be obvious" bit - sorry, it was a bit buried.

Re: Before GitHub

#249

Post by achenet »

dijit wrote: post #132
hdrz wrote: post #129

Earlier quoted context omitted.

You should continue with a name which is related to fossils, fossillab.io, boneyard.dev and so on…

fossilised.dev .. maybe british spelling. palaeontology.dev ... too awkward. museum.dev has a sort of "this is dead" ring to it. Ironically what fossils are stored in within a museum is referred to as a "repository".. Well, there's only 2 hard problems in computer science right?

> Well, there's only 2 hard problems in computer science right?

Yes there are only 2 hard problems in computer science - caching, naming things, and off by one errors.

Re: Before GitHub

#250

Post by dijit »

achenet wrote: post #249
dijit wrote: post #132

Earlier quoted context omitted.

fossilised.dev .. maybe british spelling. palaeontology.dev ... too awkward. museum.dev has a sort of "this is dead" ring to it. Ironically what fossils are stored in within a museum is referred to as a "repository".. Well, there's only 2 hard problems in computer science right?

> Well, there's only 2 hard problems in computer science right? Yes there are only 2 hard problems in computer science - caching, naming things, and off by one errors.

precisely
Post reply on HN