Live data from Hacker News

Give up GitHub: The time has come

sfconservancy.org

491–500 of 585 posts

Re: Give up GitHub: The time has come

#491

Earlier quoted context omitted.

Windows 11 is an example of poor code quality. Bugs everywhere, while the same things work on Ubuntu/popos. Past MS engineers have been commenting for a decade on how MS has grown too big, can't manage, and has become a monolith "too big to fail". By nature when engineers are small pieces of a giant machine, they don't do their best work. And those with the experience move on to better things.

The biggest issue with Windows isn't poor code or shitty engineering, it's the support for legacy software. MS engineers are some of the smartest in the world. The devs can fix the code and make a much better OS but that would break boomer software used by big banks that haven't updated since the 80s. When Microsoft write code, it has to promise support for decades, that means having to maintain the same old outdated…

Outdated APIs don't have to affect the shell and built in programs or anything else that is kept up to date. My linux programs are no more buggy due to having Wine installed for similar compat with legacy Windows executables.

Re: Give up GitHub: The time has come

#492
post #380
post #271

Earlier quoted context omitted.

Well you can always for help from a co-worker more experienced with Git, or just search the internet for help. That could be a teaching moment.

Well, that proves the point that just having a cheat sheet isn't a complete solution. And unfortunately, I am the co-worker more experienced with Git :p. Well not quite, I have a co-worker who is roughly on my level and we keep helping each other and of course trying to google ourselves out of every corner we got us into. The practical approach was to write a simple GUI which supports the operations "Pull" "Stage" "C…

Well, be fair, grandparent argued that a cheat sheet would help "for the first few months", not that it is a "complete solution", so I don't see how my suggestion "proves" anything.

Also, without knowing which issues you're having with git it's impossible to know if it's lack of baseline knowledge or if you're running into real complicated problems.

If you have a GUI with "Pull" "Stage" "Commit" "Push" buttons, I strongly suspect you're not in the complicated end.

Re: Give up GitHub: The time has come

#493

Earlier quoted context omitted.

I see your point. The disagreement I have is I would not at all consider copilot as putting MSFT into the evil empire category yet. While it was very unnerving for the ownership to change, MSFT has really had a pretty hands-off approach on Github. I touched on it, but I still see this for-profit model as being compatible with FOSS. Specifically, make it free to FOSS so that those professional software developers then…

I'd just like to ask: when was the last time Microsoft hasn't done something evil with one of their products? Windows XP? I don't understand why you're essentially resetting their reputation in regards to GitHub.

> Windows XP?

IIRC Windows XP was the first version with online activation checks aka "Windows Genuine Advantage" so I think you need to go further back.

Re: Give up GitHub: The time has come

#494

Earlier quoted context omitted.

0-clause BSD goes even further, and completely omits the attribution requirement: Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPEC…

Ah, so boost is somewhere between zero and one clause BSD.

One major difference between Boost and e. g. MIT is, Boost allows you to omit attribution in binary form (but not source form).

Re: Give up GitHub: The time has come

#495
post #356

Earlier quoted context omitted.

Your experience its quite limited and you probably need to know how to properly update ubuntu since most of the issues I've found with it (since I started using it ~12 years ago) are usually issues caused by lack of drivers (which gets solved in 15 minutes once you know where to click) once those are solved it is sturdy and you can keep it runing for several months without having to restart it or it becoming unusably…

This comment is funny to me because it was up to date and the particular issue wasn’t driver related: it was specifically that after not touching it at all for a couple months each subsequent time I logged in it would randomly lock up, took about 15min to boot.

This is practically guaranteed to be "driver" related, unless it was only one specific binary that was "locking up".

Re: Give up GitHub: The time has come

#496
post #186

Earlier quoted context omitted.

It's been years, but as I remember it SourceForge's primary downfall was the bundling of malware with binaries. That's why people I know stopped using it completely rather than because it was run on a proprietary platform.

Also the UI sucked. I never looked forward to using it.

OTOH uploading was a lot nicer than GitHub since you could just rsync over SSH.

Re: Give up GitHub: The time has come

#497

Earlier quoted context omitted.

> As a leader of a FOSS project that is on github...Do I have that reasoning correct? The way I read the article was that by being on GitHub, you are implicitly agreeing to no longer be a FOSS project as regards licensing. GitHub customers can use Copilot to generate proprietary code that's identical to your project's code (several articles I have read call this overall idea "laundering through Copilot", which sounds…

> GitHub customers can use Copilot to generate proprietary code that's identical to your project's code How is that different/new? Anyone has always been able to just take your code and put it into their proprietary projects...

Difference is, GitHub encourages this behaviour, and profits off of it.

Re: Give up GitHub: The time has come

#498
post #271

Earlier quoted context omitted.

Well you can always for help from a co-worker more experienced with Git, or just search the internet for help. That could be a teaching moment.

> That could be a teaching moment. Given the context of this thread, comments like these are part of the reasons teams don't use Git. One probably needs 10x such teaching moments with Git compared to other VCs - including good DVCS.

Considering the popularity of git itself and the fact it is successfully taught at bootcamps and university at a satisfactory level, I would disagree that being a “deep tool” is part of the reason it’s not 100% ubiquitous. The easy parts are still very accessible to newcomers and the existence of deep part doesn’t negate that.

And I also take issue with calling its “non-100% ubiquity” a problem. There is plenty of space for other tools. If anything, there’s almost a “git monopoly”.

Sure it could improve in parts, but the general discussion here doesn’t seem to be focused on improvements at all…

Re: Give up GitHub: The time has come

#499
post #104

Earlier quoted context omitted.

Gitea (and a few others) are working on federation for pull requests, which would allow someone to fork your project to their own server, and send a pull request offering you to merge from their server into yours. It also builds on top of ActivityPub which is supposed to allow federation with the greater ActivityPub ecosystem ("fediverse"). I guess this would allow people to like or comment your issue or pull request…

> I am not that excited about that last part, but federating pull requests sounds like a killer feature Git already has a pull request feature [1] that's as federated as it can get. The 'request-pull' command can be used to request pull on upstream repositories hosted anywhere (or not at all). The only requirement is that the downstream clone must be online. I know that HN isn't particularly found of email-based work…

> But requesting a pull is as simple as copying the output and mailing it (or via any text messaging service) to the maintainer.

I love email based workflows as much as anyone but for many people this is not "simple". For one, you need to be able to send plain text email or at least not have your client mangle it too much.

Re: Give up GitHub: The time has come

#500

I publish my public FOSS work on a self-hosted Gitea. I don't allow account creation, and people can send me pull requests by email. That said, I think one thing (other than interface and brand loyalty) that keeps FOSS projects on GitHub is network effects. You can reasonably expect to search it and find the projects you're looking for, and your account lets you use the issue tracker and pull requests on other projec…

Yes! Federation is so important. Federation for issues or issue triage on something other than Gitea would probably be important.

Better start self hosting gitea right now. And you can do it for free. I think the best option is oracle cloud, or does someone know how well it works on fly.io? https://paul.totterman.name/posts/free-clouds/

Post reply on HN