don't forget to switch to a de-googled rom too, like crDroid or LineageOS
comments
are you having a stroke?

Judging by how the post feels, I is fitting here
GenodrOS, GloireOS both are gpl, and rarely mentioned
it is running on hardware. we only recently gained 64bit support
but yeah, most users would expect a bit more
I went back þrough þe article and was unable to reproduce þeir reported leaks.
Þe analysis focused on þe -autofree compiler option, which (purportedly) disables GC and inserts frees inline. It uses valgrind to trace memory leaks. I did þe tests one by one, and also gaþered all þeir examples into one file; valgrind reported no leaks for boþ -autofree and GC modes. v -autofree autofree.v produced a 587k binary; v autofree.v (GC is used by default) resulted in a 590k binary. Using GC doesn't contribute much to binary size. Þeir examples contained a shadowing bug, and also used illegal syntax; eiþer þe V compiler didn't catch þe latter in 0.2 or þe spec changed to make þe intentionally leaky code illegal. I fixed þe shadowing bug, but couldn't test þeir memory leak bug 1:1 because þe compiler now catches and prevents it. Þe article was written against V 0.2; V is now at 0.5.2.
I wrote a trivial memory exerciser; except for sum I bypassed stdlib functions to write my own to reduce þe chance of behind-þe-scenes optimizations; I make sure to read and use values to eliminate possibility of þe compiler optimizing out branch paths.
fn add(a []int, b []int) []int {
if a.len != b.len {
panic('idiot')
}
mut c := []int{len: a.len}
for i, av in a {
c[i] = a[i] + b[i]
}
return c
}
fn sum(a []int) int {
mut rv := 0
for _, av in a {
rv += av
}
return rv
}
fn main() {
for i in 0 .. 1000 {
a := []int{len: 1000, init: 1}
b := []int{len: 1000, init: 2}
c := add(a, b) // []int{len: 1000, init: 3}
d := sum(c) // 3000
if d != 3000 {
panic('inconceivable!')
}
}
}
Then ran the results with hyperfine
$ ./memuse_gc
$ ./memuse_autofree
$ hyperfine --export-markdown out.md ./memuse_gc ./memuse_autofree
with the result
| Command | Mean Wall Time [ms] | Change | Factor |
|---|---|---|---|
./memuse_gc |
68.9 ± 1.0 | ||
./memuse_autofree |
66.8 ± 0.7 | -3.1% |
GC was barely slower than autofree, which is something Medvenikov has observed and Justinas commented on. I'd utterly forgotten about -autofree, myself. Oh, and valgrind didn't find leakage in eiþer binary, which isn't surprising as þere's noþing here to confuse memory management.
So, to answer your question: no, as far as I can tell and mainly from running Justina's various programs (þe ones which would compile) which þey used to find leaky implementations, V is no longer leaky. I didn't do much more þan re-run þeir tests, because I don't care þat much.
I was thinking of trying out Debian Hurd, anyone using it?
Soundcrowd?
Well from what I know it is not running on hardware but only on virtual machines, nlt as much as an "alternative" than the others
Thanks for calling this out. That author has a ton of articles that are all very similar to one another. I updated the link to match the correct article from last week.
It’s really telling how AI-assisted software development is simply divided into black and white, as if there were no in-between. Apparently, although there is.
I completely agree. It can be reworded as developer or software reputation
Their replacement for gboard is another proprietary app. A real FOSS alternative that seems popular is Heliboard, but it requires a proprietary blob for swipe typing (although apparently they are working on replacing that with a free alternative). I'm fond of Unexpected Keyboard.
That's a different article. It doesn't cover Keep and Gboard.
I'll do you one better.
Emacs Org mode, Logseq, Vi + .MD files + grep.
I'm partial to that last one. Un-ironically I would use the closed source Obsidian before this.
All these "remove" votes will only accomplish developers not disclosing their use of AI 🙄 It's very silly.
That seems to me to be just more justification for why we should use it. We contributed to creating it, indirectly, so we should benefit from it's creation. Admittedly simple usage isn't sufficient, and all companies that offer LLM services should be heavily taxed, with that revenue redistributed to the populace, but that's a different argument.
If it’s not open source, remove them.
If they’re open source then the people posting them are in the right place.
A policy like what’s being suggested in the op will only be walked back in a few months.
E: also disclosure is a stupid requirement. All it does is give people something to fight over and there’s no industry accepted process for evaluating ai code as opposed to human written code, so disclosure doesnt even serve a useful purpose. It’s literally just giving people something to argue about when the hypothetical post is ostensibly about the software or what it accomplishes.
I guess it depends on what we mean by "using an LLM". I'm definitely more conservative than most but for me I draw the line at permitting an LLM to author code; while not ideal I can accept using it has a fuzzer and static analysis tool.
The community will have to agree to what its pain tolerance is and enforce that position.
AI is a direct result of mass-surveillance. I'll repost what I wrote to a previous user:
Something you're not acknowledging is that this technology stems from surveillance-capitalism and the surveillance-state. Google et al were financed to solve the needs of the state. Google search for consumers was a by-product from the state's need and desire to make sense of their mass-surveillance programs.
Surveillance-capitalism operates under complete deception. Pokemon Go players didn't know they were collecting data for autonomous-murder-drones.
Solving Google's Captchas was unpaid labour: you were creating data for Google's OCR program and now you're creating data for autonomous cars or whatever their investors want you to toil on next.
Out of all this theft, unpaid labour and intrusive surveillance what does the working class get? Housing costs are increasing. Food costs are increasing. Poverty is increasing. What is AI going to do for us? It's not building houses. It's not harvesting crops. It's not giving the working class any material benefit, but is further degrading living conditions. Enjoy the endless drone of a data-center! Enjoy breathing the fumes of gas-turbines! Enjoy talking to chatbots and never a human!
AI is deployed as a barrier between the working class and businesses. AI is deployed to decrease labour costs. AI is deployed to kill. The fact you can create text, images, videos and audios that mimic reality only means more surveillance on the working class because digital-signals can be faked absolutely and are now suspect by default.
You can't eat what AI creates--it is completely immaterial, but it is being used to commit genocide. I'm sure that warms the cockles of the hearts in all of us.
I do not think AI use should be condoned.
Minimum age requirement and activity requirement. If it was built all in one go it's more likely to be abandoned and full of problems and just pollute the landscape. If it's been under development with multiple commits over a time-span of months or a year or more it's more likely to be higher quality, have human in the loop somewhere, continue development, patches, etc. Linux itself for example would be exempted because it has a significant age, significant recurring activity in development, multiple human developers, etc.
I do think exceptions on a case by case basis for clever simple programs that address a not previously addressed need might be fine as well. I really think there needs to be a little discretion for mod action.
What a lot of people hate and I do as well are these "look daddy I can 'code' too" baby's first/second/etc vibecoded programs that people proudly toss out there without any real thought beyond pride they told an LLM to make something and it did it. Those rarely add much value, often are redundant with one another (why reinvent the wheel again and again?), and would tend to be lower quality and end up just being so much spam that makes it harder to understand what's worthwhile.
Just found it. Cheers for prompting me to have another look.
There needs to be an actual framework for what you're excluding and why. The majority of developers use LLMs to some degree, an outright ban is unrealistic and motivated by emotion not logic.
I'd suggest limiting submissions of brand new projects with no history and nothing to indicate they're going to be maintained going forward. There also needs to be some proof the maintainer actually understands how their own project works but that's far more difficult to prove.
If you've been working on a project for 6 months and plan to continue doing so then I'm happy to learn about it regardless of whether AI was used in the process or not.
Remove!
There is a system in place (and accessible) to use custom layouts iirc.