kajika91
Joined 5 years ago
Joined 5 years ago
I try to avoid exceptions, is there any better ways? (Variant looks a bit more complicated but could be a totally OK alternative)
Is this a joke of just blatant publicity for this Billionaire "philanthropist"? This olmo uses random data of totally infringing license database such a StackEdu (https://huggingface.co/datasets/HuggingFaceTB/stack-edu).
I took this first dataset from what olmo claim to use and check a random used data -> https://github.com/rodriguescarina/URI . Boom MIT licensed (where is the credit?), 0 opt-in for AI training as far as I see.
Also funny how it's always about "the smartest guy I ever met" impliyng other dev aren't that smart. There are easily tens of thousands of devs who are way above anyone's here level but there are coding OS module, GNU tooling or other less shining stuff, or there are not American enough.
It's tiring to see the usual corp slop : github, twitter or blue sky, vibe coding, etc. Then see the complain years latter than the product was "enshitified", all was there from the beginning. Think about the real FOSS software (GNU tooling, ffmpeg, Godot, codeberg/forgejo) to see long term software than work and carry all this money-makimg mess.
As for chatto the dependency mountain is a red flag to me, this is asking for problem in my opinion, were talking primarily about sending text here.
Librewolf is, to me, the way better alternative as this is really in the FOSS mindset : a tool for everyone to use and by anyone to contribute. Seeing their plateform alone (Lemmy/Matrix/Codeberg, they also have a reddit community it seems) you can already see this is an other world than Waterwolf's bluesky/reddit/github. To be fair I can understand the SNS part but the github is a big redflag to me.
As usual I can see people that are very probably sincere in their goals not realizing the way they are going will lead to the usual enshitification: company focus, brave dependency, etc.
I note that Waterfox seems to legally originate from UK and it is refreshing to have an ecosystem that is not centralized in 1 country : for the sake of everyone it is better not to rely to much on 1 legislator (see age verification for instance).
Input data to the clipboard
Access your data for sites in the dropboxapi.com domain
Access your data for www.google.com
Access your data for www.googleapis.com
Access your data for accounts.google.com
Access your data for graph.microsoft.com
Access your data for login.microsoftonline.com
Yep! And #2 (2FAS Auth): Display notifications to you
Access browser tabs
Access browser activity during navigation
Access your data for all websites
Even better, maybe at one point web browser can get their sh* together and build better permission system (and not just disable functions like manifest v3). For now the majority of people trust opaque organization shoving them unknown code their run with way too many permissions on their computers.Talking about unknown code there is a lot of work to be done on reproducible build as anything touching web has nearly nothing about it.
The good part is that if you have better solution you actually can suggest a PR and/or implement it for yourself.
The bot verification is not specific to Forgejo/Codeberg a lot of Foss project and organization use this method to avoid unnecessary bot traffic. I understand the issue you have with it but the problem is way larger than codeberg here.
Also about the login with GitHub button would be immensely annoying for the community : you came from GitHub and you might think that your experience is more important but as this is community driven and not a business the people actually creating and using the software don't need nor want to prioritize such button but leave the option for those who wants it, which is very nice of them. Eventually if the majority start thinking a GitHub login is preferred an issue can be created and a change made in that direction.
I like the extensive benchmark from hardkernel, the only issue is that any ARM-based product is very tricky to boot and the only savior is armbian.
Aside from the bitter words against Github (and I read comments here forgetting about the very real consequences with people lives like collaboration with ICE), using codeberg is using Forgejo : those technology are by us and for us. Unlike Github we can run our own if necessary and all the technology (actions and such) can be improved and be shared between us.
An other benefit of Forgejo/Codeberg is the absence of pushing for paying more, Github is not free and lives of users going to Azure/Gemini or other Mircrosoft services. There are many parts that are made/changed to nudge people into paying more and more and be vendor-locked.
I like my life to have the fewest dark patterns as possible and Coderberg is extremely helpful.
Digging a little bit I found that git-annex is coded in haskell (not a fan) and seems to be 50% slower (expected from haskell but also only 1 source so far so not really reliable).
I don't see appeal of the complexity of the commands, they probably serve a purpose. Once you opened a .gitattributes from git-LFS you pretty much know all you need and you barely need any commands anymore.
Also I like how setting up a .gitattribute makes everything transparent the same way .gitignore works. I don't see any equivalent with git-annex.
Lastly any "tutorial" or guide about git-annex that won't show me an equivalent of 'git lfs ls-files' will definitely not appeal to me. I'm a big user of 'git status' and 'git lfs ls-files' to check/re-check everything.
pub const SinglyLinkedList(comptime T: type) type {
return struct {
first: ?*Node = null,
pub const Node = struct {
next: ?*Node = null,
};
const Self = @This();
pub fn data(self: Self) *T {
return @fieldParentPtr("node", self);
}
};"Partial clones Commutation makes it possible to clone only a small subset of a repository: indeed, one can only apply the changes related to that subset. Working on a partial clone produces changes that can readily be sent to the large repository. "
OK, now I am interested.
It is scary that someone can say it is "encrypting" a private key by applying a simple XOR.
Also :
"File-Based Index: We track file hashes in a small JSON index instead of re-hashing everything on every commit or switch. This makes commits and merges faster because Evo only re-hashes files if it notices a changed modtime"
Using modtime is not a good idea at all, this is very telling about how much author knows about different workflow. For those who don't know : you can have remotely mounted files where your machine and the server time is different (happens to me and realized that makefile is modtime based and it creates problem), also obviously clock can change and you do not want your version control system to be blind on changed file, ever.
I already know a place I want to use this.