When you are building in go or rust keep an eye on your disk quota
The crappy rust/go cargo of redundant coder specific libraries (instead of those that exist in the system) are loaded while the program is compiled,
go : in ~/go/pkg AND in ~/.cache/go-build/
rust in ~/.cargo/
Before you know it your builder's home partition may get full and you will run into building errors you can't explain (can't write disk full) ..
just a heads up on why we also don't like go and rust code
Digit reshared this.
alostfella
in reply to joborun linux • • •Could I get some context as to why Rust does not seem to be very welcomed in this community? As far as I can tell, it's ""very odd"" that it is getting pushed out of nowhere and endorsed by three letter agencies despite having lots of issues right now. But, as far as I can tell, they're "not that that bad" and perhaps solvable.
Nothing to say about go though, not only do I hate it as it's completely stupid and horrible, but they also made it impossible to look for things related to the ancient game of Go, anywhere, absolutely disgusting.
joborun linux
in reply to joborun linux • • •Say you have gnulib or glibc or libx11 in your system, built and provided by the distro, and you build some fediverse gui in rust
The code doesn't use what all other software use in common but draws from a specific fork of the code that is defined, a specific version and who know what hacking from an alternative source called libx11
and contains whatever parts it picks and chooses as static libraries within the binary it builds. So it doesn't care if you are running a 10yo debian old-stable (like 7 wheezy ) or arch-testing or gentoo-experimental, it will build what it wants.
Now this is this instance of space time 20250703114635 ... because the next millisecond the same exact build may be different as one of the "cargo" sources have now changed. So it is like trying to skateboard on quick sand ... not 2 consecutive instances may be exactly the same.
NOW, given the possibility, and it is no sci-fi, of a MiM attack, especially against anti-establishment activists, while building your "mesa" rust pkg a unique injection and retraction can affect you alone and nobody else.
It is like seeing the same exact cat walking and wiggling its tail the same exact way passing by the door in the same direction twice without returning.
Hello Mr.Smith, I am paranoid, terminate me, don't listen to whateve I say, keeping chewing on your blue pills.
Rust and Go and pips and snaps and all kinds of other "modern" things come to replace the old fashion common public source we all build from the same we all report based on the same build what we may have found wrong.
I may be wrong, totally, paranoid, I can negotiate and listen well to how I may be wrong, or call me an old fool addicted to seeing C compiling "matrix" screens flashing through my screen. I feel a bit more comfortable building from a single source that is reasonably identified as the same with the same compiler with thousands of others, instead of this undefined pick and choose code sources from here and there and google
we build mesa
can we do otherwise?
joborun linux
in reply to joborun linux • • •By the way, on the content of this post you can not deduce we are so "negative" about rust, you must have read it elsewhere but yes we try not to have much to do with it as "reasonably" possible.
Is it about rust and the kenel?
Personally I'd rather use MS-win7 than trust the likes of Linus and Greg with shoving rust packaging into the kernel.
Is there a single fediverse related software or server that is not rust based? I haven't found one. What a coincidence ... they are all written in rust they all require scripts enabled by the user to be even read, let alone login and participate.
Iri Yan
in reply to joborun linux • • •There many many projects of really high quality and use-value that remain in the dark, no mention by common unix/linux/sysadmin media, no adaptation by distros , while total bubbles get immediate and disproportionate publicity. Daemontools, perp, anope, runit,s6 were among such obscure projects. What about seatd, libudev-zero, while you can have guis of no more than aesthetic value that became popular overnight. So there is funding for some projects and publicity to draw attention and sometimes even indirect, as client media pick up on their customers' "pet projects and interests" and give them a boost while deny mentioning others from which they don't expect benefits.
Reverse engineer this observation to be really cautious and worry about seeing too much smoke, too much prop.mentioning, too many praises ... and follow funding. This trick of separating the project itself and its participants from a funding source called a "foundation" which does not need to disclose the source of funding, even to leading members of the project, is a nice front. So who funds rust? We know who funds go, but rust is more obscure.
Zstd was such a phantom miracle, popped up from nowhere, adopted by the majority, and even incorporated internally to some projects as a mechanism, disregarding intentional choices by the distro or the sys-admin. All the red flags that you can find zstd has them.
So even if you don't have concrete evidence to blame some projects, you can at least show some reservation and caution.