Need to save them within porn jpg.
That way, when mandatory face recognition for age verification comes into play, I will know who you all are! Har har har!
wrapper_last_version_update.py
Git is so easy to host yourself and everyone went and handed over all their code to evil corp to farm on anyway.
(Though I do understand that they were bought, but that was a while ago and it was only a matter of time before the evil seeped in.)
It’s such a simple reason tbh. Github is expected to stay online indefinitely. My VPS? As long as I pay the bill, which I may not want to at some point.
Codeberg is a decent middle ground - open source projects only. The site itself is open source too.
Their CI/CD minutes are very generous (unlimited!). Plus, if Microsoft wanted to scrape code, it doesn’t have to be on Github. They can scrape it off codeberg too. And I can be sure Github won’t shut down.
If Github does decide to screw users over, switching to self-hosted forgejo would be trivial.
If it’s easy why are the open source developer class using Microsoft so much ?
Convenience and reputation. People expect github to be a legitimate source of software (despite the fact that there’s little moderation). The UI is familiar already too.
It’s easy to do a lot of things people don’t do.
Like OP’s mom
I think you may be mixing up git, which is a command line tool that’s still open source, AFAIK, with github that’s a closed source, git-based code hosting platform bought by Microsoft.
You can use other hosting services with git, and get an almost identical experience. Gitlab does it, as well as many others.
You can serve up a git repository remotely very easily on any machine that has a remote access path.
No. You can use got itself. https://jasonmurray.org/posts/2020/selfhostedgit/
🤯
I prefer reading my code out loud and saving it as a Audio file
That’s ridiculous.
I write mine on paper in cursive so no one can use it anywhere
Yeah, but do you organize the audio files when you make changes?
An audio diff file that explains through voice how to modify the previous code to be like the new code
Reject GitHub. Embrace Codeberg!
I would love a subscription to Codeberg to be able to store private projects though. Codeberg is nice but you need an alternative for those special projects and it’s annoying.
Try Codefloe, it has a free tier and you can host both public and private projects.
It looks good. Thanks.
If you work alone you can just use git local without a remote repo. Otherwise there is always self hosting forgejo (the software behind Codeberg). But I also expect there to be other hosting services for that purpose.
can’t you set codeberg repositories to private?
You can but it’s for specific stuff, not real projects. Everything should be open source and public by default.
I would gladly pay them to host private projects.
It’s a small thing but I appreciate how you didn’t use the image of the rapper of the original meme who seems like an overall terrible person.
Fuck Drake. Me and all my homies hate Drake
Yeah I don’t get how he was taken so seriously for so long by so many. I get that not every rapper needs to come from a broken and messed up background, but his verses don’t hit that hard due to all the inauthenticity, as if he did grow up on hard streets lol.
Python 27??? Does tech in the future go full circle and starts to look like windows XP again?
It’s 2.7 lol
Well it says 27 >:(
I know :(
there is a better fork called forgejo
gitlab:
You don’t need GitHub for Git.
And for those who don’t know: git was there first, then github offered it for code management (they are two different things, don’t confuse git with github!)
Armatures!
Project. New Project.new.new
Project. New Project.new.new
What kind of OOP hell have I fallen into here?
Project.new.new.final.2
Untitled.new.new.optionB.MomsVersion.final.FINALFORREALTHISTIME.jokehaha.okOneMoreEdit.typo.killMePlz (copy 2)
Neither. Version control and remote sync to your self hosted gitlab or gitea, or whatever (or no remote at all if you wanna go gambling with your hard drive).
I wanna go gambling with your hard drive.
I like git(hub) because you can track changes. Not just versions
Just use git. It’s what all these front ends use at their core. It’s all just git which doesn’t need any hosting at all. If all you want is tracking changes you don’t even need to set up a remote to push / pull from. Just install git on your local development machine, make a folder for you project, and run ‘git init’. Now you have a local repo which can track and commit changes and you have all of the incredibly powerful tools available that git provides with ample documentation. Wanna back it up? Just backup the folder with any standard backup application like any other folder.
Gitlab, Gogs, Gitea… you can run all those locally.
But how often do you need that for your personal projects? I just have a git repo on a server that’s accessible by ssh. I only use a web frontend when I have to share with other people and then you might as well use a free third party service.
You don’t need it on a server even. For simple versioning just use a local git repo without any bells and stuff
True, I used the remote to access the code from other machines and/or as a remote backup. If you don’t need that, there’s no need for a server.
One of the most useful features is rolling back from origin when you’ve borked your local repo (not that I ever have…)
I’m not that accustomed with it myself, so my question: how can you bork your local repo so you can’t roll back? Did you tinker in the .git folder? xD
There are many ways. Like the other user said, fucking up a merge/rebase then fucking up the merge abort.
Or (one of my personal favorites) accidentally typing
git reset --hard HEAD~11instead ofHEAD~1I’ve had colleagues who’d panic when they had merge conflicts, then fuck something up, remove the whole dir and create a new clone. If you’re competent I don’t think it should be necessary.
aint that just
gittho? i upload my code on github as a backup and so others can see it?
Uuuh Mrs/Mr professional programmer and their fancy individual version folders!
The bottom picture should be SVN. I miss incremental revision numbers.
The mixed-revisions bug was fun… Also cannot clean history or make shitty branches everywhere, it was one of my worst experience. Nowadays Jujutsu is my favorite.
SVN is still great if there is a need for strict access controls and central control matters a lot. Auditing is also a bit easier with SVN.
It caters more for a linear workflow, though. So modern large teams won’t find joy with SVN.
It caters more for a linear workflow, though. So modern large teams won’t find joy with SVN
For what it’s worth, I work at a FAANG company and we don’t use branches at all. Instead, we use feature flags. Source control history is linear with no merges.
All code changes have to go though code review before they can be committed to the main repo. Pull requests are usually not too large (we aim for ~300 lines max), contain a single commit, aren’t long-lived (often merged the same day they’re submitted unless they’re very controversial), can be stacked to handle dependencies between them (“stacked diffs”), and a whole stack can be landed together. When merged, everything is committed directly to the main branch, which all developers are working off of.
I know that both Google and Meta take this approach, and probably other companies too.
What’s the difference between that and feature branches? Sounds like you still have PRs that get merged to main from somewhere - forked repos I guess?
Usually, feature branches mean that all the work to implement a particular feature is done on that branch. That could be dozens of commits and weeks of work from several developers. The code isn’t merged until the feature is complete. It’s more common in the industry compared to trunk-based development.
My previous employer had:
- Feature branches for each new feature.
- A dev/trunk branch, where features branches were merged once they were done.
- A beta branch, branched from dev once per week.
- A live/prod branch, branched from beta four times per year.
This structure is very common in enterprise apps. Customers that need stability (don’t want things to change a lot, for example if they have their own training material for their staff) use the live branch, while customers that want the newest features use the beta branch.
Bug fixes were annoying since you’d have to first do them in the live branch then port them to the beta and dev branches (or vice versa).
On the other hand, feature flags mean that all the code goes directly into the trunk branch, but it’s turned off until it’s ready. A basic implementation of feature flags would be a static class with a bunch of booleans that get checked throughout the code, but they’re usually dynamic so a misbehaving feature can be turned off without having to redeploy the code.
Some codebases use both feature branches and feature flags.
Ah okay, places I’ve worked have tried to keep tasks as small as possible so you don’t work on your feature branch more than a day. If it takes over a day, should’ve been an epic (and therefore multiple feature branches). Seen different approaches to the whole release thing too. Weekly deployments, 3x per year, or in my current company: deploy as soon as someone has tested it
This makes me happy. 🙂
Trunk based dev is GOAT.
git rev-list HEAD | wc -l
