311–320 of 641 posts
Earlier quoted context omitted.
I guess Github uses a lot of cache vs Codeberg.
I think you read that backwards. In skydhash's test, Codeberg's data was 72% cached, and GitHub's data was 28% cached. Maybe you meant that GitHub's cached 4.28MB was, in absolute terms, more than Codeberg's cached 1.41MB?
Earlier quoted context omitted.
Any analysis of Github's functionality that begins and ends with blaming individuals and their competency is deeply mistaken while being insulting. Anyone who has ever worked at a large company knows exactly how hard it is for top performers to make changes and it's not difficult because the other people are stupid. At least in my experience, almost everyone holding this "they must be stupid" opinion knows very littl…
But should you care about MS's internals? Product is useless, you move along. Save your compassion for those actually needing it.
Earlier quoted context omitted.
I guess Github uses a lot of cache vs Codeberg.
I think you read that backwards. In skydhash's test, Codeberg's data was 72% cached, and GitHub's data was 28% cached. Maybe you meant that GitHub's cached 4.28MB was, in absolute terms, more than Codeberg's cached 1.41MB?
The transferred part is for the gzipped transfer. That makes sense if the bulk of the data is HTML (I have not checked).
I’ve disabled the cache for the network requests.
IMHO, the main advantage of github is that it is an ecosystem. This is a well-thought-out Swiss knife: a pioneering (but no longer new) PR system, convenient issues, as well as a well-formed CI system with many developed actions and free runners. In addition, it is best to use code navigation simply in a web browser. You write code, and almost everything works effortlessly. Having a sponsorship system is also great,…
> a well-formed CI system Man :| no. I genuinely understand the convenience of using Actions, but it's a horrible product.
Every time.
The edit history of the announcement is quite a ride: > [2025-11-27T02:10:07Z] it’s abundantly clear that the talented folks who used to work on the product have moved on to bigger and better things, with the remaining losers eager to inflict some kind of bloated, buggy JavaScript framework on us in the name of progress [1] > [2025-11-27T14:04:47Z] it’s abundantly clear that the talented folks who used to work on the…
Earlier quoted context omitted.
I think you read that backwards. In skydhash's test, Codeberg's data was 72% cached, and GitHub's data was 28% cached. Maybe you meant that GitHub's cached 4.28MB was, in absolute terms, more than Codeberg's cached 1.41MB?
Some parts of Github are SPA island, which is why the DOM load fast, but then it has to wait for the JavaScript files and the request made by those files. Codeberg can be used with JavaScript disabled and you don’t have that much extra requests (almost everything is rendered serverside). The transferred part is for the gzipped transfer. That makes sense if the bulk of the data is HTML (I have not checked). I’ve disab…
The edit history of the announcement is quite a ride: > [2025-11-27T02:10:07Z] it’s abundantly clear that the talented folks who used to work on the product have moved on to bigger and better things, with the remaining losers eager to inflict some kind of bloated, buggy JavaScript framework on us in the name of progress [1] > [2025-11-27T14:04:47Z] it’s abundantly clear that the talented folks who used to work on the…
I say this as someone who has been cautioning about Microsoft's ownership of GitHub for years now... but the Zig community has been high drama lately. I thought the Rust community had done themselves a disservice with their high tolerance of drama, but lately Zig seems to me to be more drama than even Rust. I was saddened to see how they ganged up to bully the author of the Zig book. The book author, as far as I coul…
Zig people want Zig to "win". They are appearing on Hacker News almost every day now, and for that purpose this kind of things matters more than the language's merits themselves. I believe the language has a good share of merits though, far more than Rust, but it's too early and not battle tested to get so much attention.
Earlier quoted context omitted.
It’s silly to assume that someone isn’t competent just because you know about a tool that they don’t know about. The inverse is almost certainly also true. Is there some kind of Google-centrism at work here? Most devs don’t work at Google or contribute to Google projects, so there is no reason for them to know anything about Gerrit.
> Most devs don’t work at Google or contribute to Google projects, so there is no reason for them to know anything about Gerrit. Most devs have never worked on Solaris, but if I ask you about solaris and you don't even know what it is, that's a bad sign for how competent a developer you are. Most devs have never used prolog or haskell or smalltalk seriously, but if they don't know what they are, that means they don't…
I feel that training copilot on Github repos without maintainer consent was a betrayal - this pushed many projects over to Gitlab.
Earlier quoted context omitted.
I don't agree with this at all. I think the reason Github is so prominent is the social network aspects it has built around Git, which created strong network effects that most developers are unwilling to part with. Maintainers don't want to loose their stars and the users don't want to loose the collective "audit" by the github users. Things like number of stars on a repository, number of forks, number of issues answ…
> Things like number of stars on a repository, number of forks, number of issues answered, number of followers for an account. All these things are powerful indicators of quality Hahahahahahahahahahahaha...