Live data from Hacker News

Why SourceForge Lost

usersinhell.com

31–40 of 52 posts

Re: Why SourceForge Lost

#31
The first battle SourceForge lost was against Google Code hosting. Google offered a nicer interface and had some features SourceForge hasn't, the most important one, subversion.

SourceForge, like other sites managed by VA Linux/SF/Geeknet, has a terrible record of user friendliness. How many Slashcode-based sites are still running?

Re: Why SourceForge Lost

#32

You know as much as I hate these terms, I think nothing captures the undeniable yet intangible difference between SourceForge and GitHub as Web 1.0 vs Web 2.0. For the younger members here I think it's hard to imagine just how freaking cool SourceForge was when it first came out. The idea of free, featureful project hosting was amazing. Back in the 90s, even if you had free hosting, there wasn't the selection of easy…

Sourceforge seems unable to evolve because its business model is stuck in Web 1.0: bring as many visitors as you can and throw as many intrusive ads as possible in front of them before they can get what they wanted in the first place and leave.

Re: Why SourceForge Lost

#33
post #22

I would only argue one point in this: Github is not a developer's paradise. It's good. In fact, it's really good. But it has one huge weakness, something which all DVCS repositories seem to have followed: they charge per repository. This is a terrible pricing model. It should, if anything, be based on per-GB of storage regardless of repositories. Otherwise it gets hideously expensive for people to, say, have many sma…

Unfuddle charges by space used, not per-repo. For Git projects, the per-repo pricing of Github is insane. They don't even have a public pricing plan for the number of repos I'd need for my personal (and private) coding. I use Unfuddle for my private and business code.

100% Agree. I have 5 different GitHub accounts to cover all of my repositories, and I'm constantly having to shuffle active projects in and out of GitHub. I've emailed them asking for different pricing, and "they don't support that".

It's the only thing that has me looking for alternatives.

Re: Why SourceForge Lost

#34

Here's another take on this - programmers hate ads and SourceForge is riddled with them. GitHub isn't. Also, if I want to setup a repo and put it on GitHub, it's stupidly, ridiculously easy. SF isn't hard, but it isn't as easy. Open source software is about PROGRAMMERS collaborating. GitHub makes that incredibly easy and straightforward. Want to join a project? Fork the code and tweak til your hearts content. Your co…

Programmers that hate ads use Adblock.

Re: Why SourceForge Lost

#35

You know as much as I hate these terms, I think nothing captures the undeniable yet intangible difference between SourceForge and GitHub as Web 1.0 vs Web 2.0. For the younger members here I think it's hard to imagine just how freaking cool SourceForge was when it first came out. The idea of free, featureful project hosting was amazing. Back in the 90s, even if you had free hosting, there wasn't the selection of easy…

Sourceforge seems unable to evolve because its business model is stuck in Web 1.0: bring as many visitors as you can and throw as many intrusive ads as possible in front of them before they can get what they wanted in the first place and leave.

As far as the terms themselves, O'Reilly was talking about a change in focus from software to data... http://twit.tv/floss73

From that angle, then: SourceForge is a great place to download installers, while GitHub is a great place to get the nitty-gritty details about making a bit of software.

Re: Why SourceForge Lost

#36

Here's another take on this - programmers hate ads and SourceForge is riddled with them. GitHub isn't. Also, if I want to setup a repo and put it on GitHub, it's stupidly, ridiculously easy. SF isn't hard, but it isn't as easy. Open source software is about PROGRAMMERS collaborating. GitHub makes that incredibly easy and straightforward. Want to join a project? Fork the code and tweak til your hearts content. Your co…

I think that's an understatement. Sourceforge is so bad that for years (well before Github) I have dreaded downloading anything from it or needing to use its navigation in any way.

Also, a fair bit of malware has been hosted there over the years and the site offers no useful search or way of finding what you're looking for.

The initial idea was a good one, but the founder cashed out long ago.

Re: Why SourceForge Lost

#37
post #22

I would only argue one point in this: Github is not a developer's paradise. It's good. In fact, it's really good. But it has one huge weakness, something which all DVCS repositories seem to have followed: they charge per repository. This is a terrible pricing model. It should, if anything, be based on per-GB of storage regardless of repositories. Otherwise it gets hideously expensive for people to, say, have many sma…

I think this is intended as a "tax" on closed source software. While it's annoying, I pay the extra $10 per month to get a few extras and don't worry about it.

The major downside is that the policy leads people to use git incorrectly by not using submodules where they are appropriate.

Re: Why SourceForge Lost

#38
post #8

Earlier quoted context omitted.

My mind got snagged on that, too, and it wouldn't let go. The rest of his arguments are not wrong, but I think they fit under that umbrella. That is, it's because GitHub's front-end is nicer, and it's front-end is nicer because SourceForge is oriented around projects and GitHub is oriented around code. The change in focus enables a better presentation.

It's not that Github's CSS is better, or their graphics are better, but that their design is better, and design encompasses everything, top to bottom. Most things on Github feel effortless, and even the tricky things are far from frustrating. This is evidence that they care, and that care shows in that the graphics and CSS are very well done. Good design doesn't start with appearance, it ends with it.

In Startups Open Sourced, Tom Preston-Warner is interviewed and says to design every detail of every page of a project before touching any code. While graphic design and technical design are very intertwined, I think in Github's case the graphic design came first, or was at least equally weighted. I don't know how SourceForge came to be, but I wouldn't be surprised to find out the backend was designed before the front end design.

Re: Why SourceForge Lost

#39

Here's another take on this - programmers hate ads and SourceForge is riddled with them. GitHub isn't. Also, if I want to setup a repo and put it on GitHub, it's stupidly, ridiculously easy. SF isn't hard, but it isn't as easy. Open source software is about PROGRAMMERS collaborating. GitHub makes that incredibly easy and straightforward. Want to join a project? Fork the code and tweak til your hearts content. Your co…

I think that's an understatement. Sourceforge is so bad that for years (well before Github) I have dreaded downloading anything from it or needing to use its navigation in any way. Also, a fair bit of malware has been hosted there over the years and the site offers no useful search or way of finding what you're looking for. The initial idea was a good one, but the founder cashed out long ago.

E.g., wget support was broken for a very long time. So, you had to either a. algorithmically compose a URL or b. navigate to the real download link using the browser, collating all of them together and then wget -i blah.

These days, it feels much better though.

Re: Why SourceForge Lost

#40
One key point that I think this article missed is the activation energy required to create a new project. On SourceForge, at least when I last used it, it was a very involved, explicit process, where you created a new project and went through several screens of populating license, status, etc., and then you finally had a place where you could stick code.

Whereas github lets you get a repo up and running with just about a single click and a 'git push', and then add on features and information as you grow. So it became the place to stick all of your one-off, throwaway, or experimental code, which got developers in the habit of using it, and it also had the room to grow if once of those things grew into a "real" project.

Post reply on HN