S_S

GitHub and Codeberg are not Version Control Systems, they are Git platforms

Git is a VCS

I don't like platforms and unnecessary information that are being stored in them or Git, also it is more in the way to be honest

It is not that hard to:

tar -xzf antman-1.0.0.tar.gz
cd antman-1.0.0
git init .
git add -A
git commit -a -m "initial commit"

if anyone wants to use Git, generate me a patch file or send me a link to your fork and I'll handle it fine if you want to contribute back

I'm not going for another arguing here, if you want to check out my previous answers to this question check my profile and find my other threads

It is obviously about that since no good arguments are really made for anything else. There is just a constant nonsense talk why to use git and git platforms. Developers seems to have got stuck in some mindset that everything needs to version controlled all the time, if you make a change or at least a couple you gotta have to make a git commit, or otherwise most of the benefits are lost anyway, but of course I don't really know how much of developers you really are. I don't care what the industry standard is for public development, I'm not making public development, I'm only making a public release here. Are you really saying that using a VCS isn't a pain in the ass? I do it because I most and when someone pays me to do it. Everyone is acting like it is just a natural piece in the workflow of any software project, I strongly disagree. It is in the way and causing extra job in every step on the way (or is everyone using a auto-commiter or a full blown CI/CD system for everything?). But that is the point when you develop something in group or for money, it has strong benefits then. Here I have time to develop it linearly and in my own pace and do all the testing I need. I don't need git as a CTRL+Z tool or as a unfinished feature branch tool. My text editor alone got me covered, I've trusted it with my life for over 10 years. I couldn't be happier and more productive with it than I already am. It might be simple to use git, but it is still extra, and in this case unnecessary extra. It literally doesn't give me anything. Why would I also setup a git provider account, even if it is one time, ssh keys are made in a split second but you got to manage them as well, add them to the provider website and take them with you where you want to develop. I got all that setup on private instances, I fully manage myself, I know exactly how everything of that works.

It is a fact that most software skip unit tests and functional tests, I don't believe it is good and neither do I brag about that I don't have that yet. This project doesn't need to be exposed to the public internet at all. You can run them perfectly fine in a own VLAN or something. I'm not saying anyone should run anything they aren't fully trusting. I would much rather be discussing design decisions or security concerns than why I'm not using git or have any unit tests yet. I know exactly how sensitive it is for software to run in someones infrastructure, and tools that could alter and manage that, and protect the traffic between the node and the endpoint. But then give something real critical of that and refer to the code or design and not just good practices. I know they are good and useful, but it is not everything. What matters is the code in the end. Don't run if you can't trust it because its lacking automated testing then. I don't care if I'm the only one ever using it, I created it for myself and it is solving a whole lof of issues no other tool or solution comes close to. I'm sharing it if anyone else is looking for something like this and maybe wants to just take a look on how I solved it when developing their own tools. I'm more than happy to help with setting it up or answering any questions related to it or the things it does

Yes unfortunately most of the comments on my last post was also about me not using git and git platforms, seems very controversial.

I totally understand it, I've also wanted to have everything git and social development platform before when it was new

No problem, your thoughts are welcomed

I mainly developed it for myself, and sharing it if others want to do what ever they want to do with it, took many hours to just put together all the readmes and examples and cleaning up the code, I understand everyone wants me to release it on some git platform, but I didn't develop it using any cvs at all and don't plan to do that either

I just like to release it this way, I didn't have much reason or benefits to releasing it on a git service, hosted or my own

Sure it might creates some hurdles for potential contributors, and cause some discomfort for users

For the user case I believe downloading the archive or even the diff text and applying it is quite straight forward, there isn't any more steps in that than if it was in a repo, it is another way of pulling the code, I'm pretty used to handle software this way anyway, but most people aren't, I even doubt people would have pulled the SVN URL if I had released it on SourceForge for example, they would have downloaded the source archive from the website, so I don't believe that the fact that I don't upload it to a git/svn service makes it much harder for a user

It is a lot more work to setup a git repo, create an account somewhere, manage ssh keys, setting up configs, making commits, pushing code etc for me

Offers changes back to me is more a me problem, if you create a git repo and send me the patches or URL I can figure the rest out, anyone doing that can still benefit from my diff files as they can be applied to a git repository as well, or they could create two repositories (or branches), one with just my changes and one with theirs mixed in, and get full three way merge as well

For the easily checking what has changed it is quite the same thing, there is an extra step unfortunately

For the relying and trusting me all I can offer is the transparency, I don't believe many people would notice when a project get forced pushed either, some developers might use the same directory every time to make a pull, and then it would tell them there's a mismatch, but it is a legit concern nonetheless

I think using git solves that a bit, you would notice if something was forced pushed, as the auto-updating would fail with an error, but applying patches would also fail the same way, but that is of course a manual operation, having it in a SVN repo feels like it would produce the same problem also

SVN is probably as much of obfuscating as these files because git is what everyone uses, so it is more a problem of not using git than not using a (D)VCS I believe

Yea finding it is hard, there are a lot of other benefits with centralized social development platforms, but there was also a time before all that started, I think this community in particular is about not giving up to centralized platforms

If I ever stop the development, die, go rouge, get hacked or anything else I hope the community figures that out on their own and solves the problem then, anyone who wants should download the text diff files and/or the tar.gz files and take a few different checksums of them so they do not change maliciously at least

Yes I know it is built in into the package management in golang and other languages, I'm pulling things into my project that way

I know it is free also and that I can have private repos, it is one of the first tools I also install on dev machines

But I don't see how that means I always have to use git or any other VCS for every project I make, it is a good tool, but why do I have to use it if it doesn't help me?

I've done a lot of testing, not skipping that, writing automated tests are a whole different thing however, it is not as straight forward and is very often skipped for a large amount of projects to be honest

Git was made to handle the sheer amount of commits and people contributing to the linux kernel, the first versions of linux is just Linus uploading the code to a FTP, git is just a tool for Linus to patch his local git tree in a fast way with all the patches he gets from different channels and manage a large public repository

Unlike Linus I'm not planning to be of control of a public development process for my software, so a VCS doesn't make much sense in my opinion

Before git it was far from standard to use a source control system on small projects that weren't about to be a public development process anyway, while it is a gold standard for source control today, I don't think one have to use source control on every software project, like it used to be

Thanks

I just don't think I need to use one on every one of my projects, it didn't add any (or enough) value to me for this project for bringing in another tool into the development or release process

For me this isn't controversial to skip either, I'm using (and even contributing some to) software all the time with just using folder archives without needing to use any repo tools, historically a lot of software development haven't need it as well

I totally agree it is no different than a random untrusted git repo, so I believe no additional trust is gained if I uploaded it to any of them

I think version control this way is totally fine, every commit in the linux kernel is mailed as a text diff on the different mailing lists

As of trusting this or any security related software I believe you have to ultimately read and understand the software you are using, or someone you trust has to do it, I can't do that, I can only answer questions as they arrive

I also agree unit tests are probably a good idea for those reasons as well, I don't have any right now but I'm open to do them some time or receive patches with them

I like your feedback, thanks for it

No worries, I understand

There are just text files there anyway

I'm pretty much just sharing my public backup with everyone, it is the only thing I need when deploying it, maybe someone else uploads it to some repo one day!

No, no public repo, no repo at all tbh, only the public code posted at the cloud drive, but the code is fully inspectable in the drive and there are no compiled binaries (you must compile it yourself to use it)