3 ms·
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 becau
by scott_s 15y ago
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.
- StavrosK 15y agoI agree, it's not the only reason (being able to fork anyone's code, fix the bug, re-release and ask them to pull is a godsend), but I always dreaded visiting SourceForge.
- astrodust 15y agoIt'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.
- evilduck 15y agoIn 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.
- nitrogen 15y agoIIRC, the general wisdom during SourceForge's heyday was to design the backend before the frontend. I recall reading a zen programmer story about someone writing a finance package, who was mocked by the "wise" programmer for designing and writing the UI first, before having any finance-related code.
- scott_s 15y agoThis is true to a fault: for a while many people asked to be able to change the code font, or at least for it to respect browser defaults. They resisted because that went against what the designer thought was best - which I think is a case of form trumping function.