Thread 107151076

What exactly is the point? Like do 50 year old GNU coreutils have some memory leaks in them?

Originality has slipped their mind. They can only rewrite.

That’s what they are paid for by big tech nowadays, don’t blame them

Back then these programmers would have gotten money to do something more interesting, but genius boomers are dead and what is left in power is their literal nepo-daughters with daddy issues

>>107151076 (OP)
Changing the license

it's an attempt to reduce/remove GPL, as the GPL is not friendly to corporations

How the fuck are they still rewriting unix utilities 50 years after they were invented? People routinely wrote unix-like operating systems throughout the 70s 80s and 90s that came with a full suite of newly implemented unix commands. They've been at it for how many years and with how many thousands of people contributing? WTF are they doing? You might as well just formally prove x86 correct if you want to go this slow.

>>107151287
>who cares about the most used set of programs in the world

>>107151350
we're not talking about ms and adobe products

>>107151367
trolls as bad as you should be slaughtered publicly

>>107151367
im gay btw, and a frogposter furthermoresodoitsobeit

>>107151085
who are "they"?
>>107151112
who are "they"?
what "big tech" is involved? and who is getting paid? in the context of uutils.
who are the "nepo daughters" involved in this?
>>107151128
why would you do all this instead of just picking up the freebsd utils, or one of the other non GNU licensed options which always existed, if that was really the goal?
>>107151139
an attempt by whom?
who created this master plan?
in what year?
in what dark room was "the decision" made?
and what means did/do "they" have to execute it?
and why did "they" not just pick up one of the non GNU options that always existed?

>>107151383
nooooo stop it just STOP IT!!!!!!

>>107151076 (OP)
Mental illness.
Rust cultists are unaware that we can test for memory leaks.

>>107151383
>who are "they"?
top developers out of big research universities, mit Boston, iit Hyderabad, etc.
>what "big tech" is involved?
Microsoft, Google, Facebook, etc.
>and who is getting paid?
Said top developers
>in the context of uutils.
It’s Ubuntu paying the bills, but who pays the bills to Ubuntu?
>who are the "nepo daughters" involved in this?
Top university professors, member of advisory boards of big tech, Jews and other tribal entities (such as Brahmins, Arab Muslims) with large financial liquids

Any other trivial question?

>>107151128
this

Rust runs like crap so corpos can have fun with their rewrites it won't get them anywhere

All the big corpos are in for a crash anyhow, I doubt many of them will exist by the end of the decade

>>107151383
they are rust users
it's obvious from the OP, are you retarded?

>>107151076 (OP)
What exactly is the point? Like do 20 year old UNIX utils have some memory leaks in them?

>>107151469
>>what "big tech" is involved?
>Microsoft, Google, Facebook, etc.
So like Linux and C++?

>>107151076 (OP)
GNU coreutils isn't maintained by troons, so uutils is better by definition.

>>107152521
Can you name a single tranny uutils maintainer?

>>107151469
>top developers out of big research universities, mit Boston, etc.
can you point to those in the uutils contributor list?
>Microsoft, Google, Facebook, etc.
can you point to connections to these companies in the uutils contributor list?
>It’s Ubuntu paying the bills
can you point to these bills?
>Top university professors, member of advisory boards of big tech, Jews and other tribal entities with large financial liquids
can you point to the connections between anyone mentioned above and uutils?
>Any other trivial question?
the one you didn't answer:
>why did "they" not just pick up one of the non GNU options that always existed?
(removed jeet-isms while having second hand embarrassment)

>>107152565
This does not look good for your argument. You will probably find more active tranny maintainers in literally any FOSS project than some literally who who made few commits 5 years ago kek.

>>107151076 (OP)
The """point""" is that kikes want to wrest control of ALL systems away from the open, international ISO standard languages (basically C, C++, Ada) because they can't control them fully for their own (((evil ends))). The rustroon language and other forms of commercial pozz can be easily controlled by ((($$methods$$))) readily at their disposal. Simple as.

>>107152977
There is quite a few jews in ISO, wtf are you talking about

>>107152977
so iso, a tool of the world order, is not under (((their))) control?
and (((they))) hate closed committees and doing things "under the table" (i.e. in private committee meetings) and prefer everything being discussed and decided in the open?
interesting. almost sounds like "reverse psychology" propaganda for (((them))) even.
would like to know how rust is "commercial pozz" too. that also sounds interesting. is it the language (vs. the iso standards), or the implementation (vs. ???), or both, and how?

>>107151128
Won the quiz.

It's all just much ado about nothing. The GNU Coreutils are practically obsolete these days. They were certainly useful in the 80s and 90s when your main alternative was writing it yourself in C/C++, but now we have modern scripting languages like Python that can achieve the same thing just as easily but with a more pleasant syntax. Not to mention the Unix-like utilities are designed for working with plaintext data which we've now realised is stupid and creates a fuckton of issues.

>>107153159
Coreutils are not obsolete. Bash shell is still the standard way of managing Linux server and often desktop too. As long as shell will exist, so will coreutils. And no, REPL of a general scripting language will never be as handy as bash shell. And no matter of how relevant coreutils are now or in future, it still doesn't change the fact that Ubuntu fucked up by replacing a working part of their system with unfinished, halfbaked solution. This is not like Linus' effort to allow for more languages in kernel or Mozilla's effort to optimize and harden their browser, this is a plain regression for no good reason whatsoever.

>>107153464
You are probably replying to a bot. Real people can't be this stupid.

The point is to give autistic tinker trannies something to do because otherwise they'd rope.

>>107153464
Yes, I said practically obsolete because they still have a single valid use case: Bash scripts for system administration tasks. But this is a niche use case, the GNU Coreutils are nowhere near as important as they used to be.

Bear in mind people used to actually use those UNIX programs for ordinary computing purposes. Bc was their go-to calculator, AWK was their go-to text processing tool. Now those programs are much more niche.

>>107151383
Troons
>in what dark room was "the decision" made?
Discord
>and why did "they" not just pick up one of the non GNU options that always existed?
mental illness

>>107153592
NTA. Since when Canonical is managed on Discord? I literally never heard of that.

>>107151383
based

>>107153552
Retard

>>107151139
Ahhhhh. Hmmmm. I didn't consider that. I thought the rust cult was purely destructive for the sake of it.

>>107153686
>NTA. Since when Canonical is managed on Discord? I literally never heard of that.
Lots of very big, very important decisions are made outside the "official" channels. There was an episode of Friends where Rachel tried to take up smoking because she was sick of her boss and her rival leaving her out of shit because she was stuck alone in the office while they conversed "casually" outside over a smoke. That was typical of office culture. Meetings are where ideas go to die, smoke breaks are where the big decisions get made.
In the modern globalist world you get fuck all done on the official mailing lists and zoom calls, but you make all sorts of important decisions during discord grooming and furry roleplay sessions.

I hope Rust and Wayland both crash and burn, along with any distro and dev supporting them, so that GNU/Linux can finally return to white traditional values like God intended.

>>107153488
>Real people can't be this stupid.
Oh god I wish I had your optimism. No, I often have to clean up the mess caused by zoomers and their willingness to make everything fucking complicated and done in a messy pile of containers, python and baked in dependency trees. Meanwhile anyone with more than 10 minutes on the job will want to use the already installed base utilities that WON'T require you to chase down a breakage that happened after apt dist-upgrade made a tiny point upgrade to python and broke your totally isolated venv.

>>107155261
Probably will. Inorganic corpo backed slop like them tend to fall apart once the money runs out. There will be a new hotness that replaces both eventually. It probably won't mean a return to C++ and X11, XLibre probably won't be the long term future. But I'd put money on it not being Rust+Wayland.

>>107151469
>Any other trivial question?
Yeah. Where's the proof of any of these claims?

>>107155232
sounds cool. what llm is this?

>>107151076 (OP)
> Why
To replace GPL code with MIT/BSD code.
> Is it necessary from a security perspective?
No. Coreutils are very small programs and are battle tested and have very few CVEs.
> Is there a conspiracy?
Yes. Both the uutils and Ubuntu team refuse to discuss the licensing issue. So obviously that's the real "innovation" in uutils.
> Are uutils feature complete compared to core utils?
No. Uutils lack many features users expect from core utils.
> Why is this happening?
So Linux can be even more corporate friendly. I'm sure they're dreaming of a kernel written entirely in Rust with an MIT/BSD license. Babysteps.
> Should I uninstall Ubuntu and fight to keep Ubuntoids and uutils out of Debian?
Absolutely.
> Should I fight to keep Rust out of the Linux kernel?
Absolutely.
> Should I suspect everyone who pushes 'oxidiation' meaning rewriting in memory safe Rust for security reasons?
Absolutely.

>>107151076 (OP)
NIH syndrome

>>107151076 (OP)
Well, they for sure don't anymore. And that's a good thing.

>>107151128
>>107151139
/thread

>>107151128
This anon gets it.

>>107151128
What does changing from GPLv3 to MIT do here?

>>107153014
I'm quite well-aware, fren. And the fact they can't simply destroy it outright is giving them the rage. They could devolve something like oh say -- (((The Mozilla Foundation))) -- practically overnight. Not so C & C++.

These programming languages are treaties, in-effect. The independent nations are signatories. They themselves will fight tooth-and-nail against such kike machinations to protect the language's integrity, since they themselves have so much critical infrastructure that depends on it.

>>107155502
google guidelines forbid use of gpl code

>>107152859
There comes a point where all you need to do is go to the ubuntu website and check the donors, and then the license of the new code vs the old.

>>107151076 (OP)
>What exactly is the point?
Mailing lists are scary to zoomers. They want projects to contribute to using GitHub issues and pull requests.

>>107155502
allow microjeets to embrace, extend and extinguish

>>107151076 (OP)
Anons are correct that it's about re-licensing software, but it's deeper than that.

Why not rewrite everything in C then?

The problem is that "they" want the entire toolchain congenitally permissive. They do NOT want independent compilers.

A from-scratch C compiler is a big achievement but it's doable by a single turbo-autist. Want an independent Rust compiler? Hire a team of PhDs and get back to me in a decade.

Terry Davis was right about everything. MIT niggers want compilers under lock and key. They dream of a world where the entire open source toolchain is MIT/Apache. Rust's prohibitively complexity helps them achieve the goal.

>>107151469
>big research universities, mit Boston, iit Hyderabad
saar your cover is broke

>>107151076 (OP)
rust re-writes are glowie ops

>>107155936
>>107155998

How?

>>107156009
Where there's a will, there's a way. Java is similarly complex compared to C but there's been other compilers from toy bytecode assemblers all the way up to Dalvik/ART. The main constraint is more language popularity. People hate Java therefore fewer hobby projects to replace the toolchain outside of corpos that have already sunk their costs willing to sink more money into an oracle divorce. Rust is still early days. People hate it which limits hobbyists and the only users of Rust are the cultists so they aren't going to fork or rebuild. If there's a need for a non-tranny rust, it'll happen. But we are a LONG way away from a need. Right now there's a greater need to fork AWAY from the rust zealots

>>107155284
>sounds cool. what llm is this?
old-man-rantings-r34:344B.safetensors

>>107156074
Stop questioning things, goyim. This is your final warning.

>>107151128
Lmao, as if a total Rust rewrite were the best way to accomplish this.

>>107155502
It avoids license struggle sessions with retards.
MIT lets everyone just no longer have to deal with each other, unless you really enjoy tranny superblocs fighting with you and US litigation.

>>107151076 (OP)
the point is to kill the GPL

>>107155320
>Debian
Already compromised, only a matter of time now.

>>107155320
/based

>>107155957
can you answer any of the questions directly instead of vague-theorizing like a retard?
i know the answer is no, because you're just yet another tech illiterate /g/eet. but i will entertain you anyway with some additional ACTUAL facts:
* non-gnu distributions already exist, like Chimera Linux, and they use ZERO core rust components. no uutils. not any other rust "replacement" or alternative.
* the other component ubuntu decided to replace (sudo), is licensed under a hodgepodge of liberal non-gnu licenses.
* your system right now depends on multiple core decades old liberally licensed C projects. do you want a list?
* uutils existed for years before ubuntu thought about switching to it.
* ubuntu doesn't pay any uutils bills. and you don't need to check the ubuntu side for that, because uutils simply doesn't have any bills. lol.
* the "theory" would be even more funnily retarded if ubuntu was actually paying, because it would mean they are actually PAYING a 3rd party, not even their own employees, to replace what they got for free from the gnu option, hypothetically just to change the license, with no prospective on how would that be in any way directly profitable. makes great financial sense that. lmao.

>>107151128
>>107151139
all tranny interlocutors trying to kill GPL'd projects are getting paid by Microsoft and other big tech companies to disempower and destroy GNU and Linux/BSD in general.

>>107156009
i feel charitable today. so i will give you a pro-tip.
this may surprise as a tech illiterate /g/eet, buy you can relicense MIT/Apache code to (A)GPLv3, but not the other way around.
sudden rug pulling is NOT one of the reasons why liberal licenses can be bad.
and liberal licenses don't have a lock or a key, which a retard could have inferred from the name. the legal right for a corpo to just relicense a random project to something proprietary, is the exact same right (you) have to relicense the same project to (A)GPL.
rustc itself is only months away from having a fully usable gcc code generator. gccrs however is still years away indeed, but it is an option that is being actively worked on.
on the other hand, your GPU stack has a hard dependency on the liberally licensed llvm, which should be of much bigger concern for you, that is if you were both informed and genuinely bothered.

don't worry I'll bump for the poster above, he's shy

>>107157101
No, but who else is willing enough to rewrite some old, boring ass piece of software

>>107151383
>why would you do all this instead of just picking up the freebsd utils, or one of the other non GNU licensed options which always existed, if that was really the goal?
because none of them are compatible with GNU you fucking cretin?

>>107158419
let me draw from you expertise on this matter.
so picking up the freebsd utils and making them gnu-compatible would have been harder than writing everything from scratch in idiomatic rust code?
very interesting. can you expand on that with specific technical info?

>>107158827
bsd utils are basic and bare bone the only reason GNU became THE userland is because their tools were much more powerful and stable compared to sun or whatever the fuck shitty unices there were in 80s-90s
ls is probably good 5-10k of highly technical C code that has 30+ years of development time
and openbsd ls is like 500 LOC because it does fuck all
now check grep, i wont because i dont give a fuck but youre a pretentious cunt

>>107151076 (OP)
it's a war on GPL and free software in general

>>107151383
>who are the "nepo daughters" involved in this?
Dennis Ritchie from Bell Labs.

>>107155502
you can use MIT code in proprietary software / without sharing changes back

>>107157953
highly permissive code is at high risk of being EEE'd than GPL code. just look at nextstep/macos

>>107158894
BSD can never keep up with GNU because the GPL enforces enhancements to be made available, BSD licensed stuff encourages people to take what's available, extend it to make it more suited for their purposes, but never share those changes back

>>107151076 (OP)
Humiliation ritual, rust is deep-glued to a compiler that puts glowie backdoors hidden in bloated binaries.

>>107157817
sounds like somebody hasnt seen the antioxidant manifesto

>>107151128
its over

>>107151128
>>107151139
fuck the GPL. copywrite is a spook, it exists ironically to benefit corporations (y'know, the only people who can afford to litigate stuff?)
they don't care about muh gnu utils. you yourself (nocoder) could rewrite them. even if they did, big fucking whoop.
>oh noes, microshit has cat now!!1!1 they want to profit off cat guise
oy vey.
note also, GNU didn't invent or design these programs, they only reimplemented and extended (bloated) them to shit. anyone can do what they did, as these troons are demonstrating.
>>107151287
that's how projects are now, they just keep going forever. nobody ever says enough, its finished. what they do, I don't know, but I keep getting updates for just about everything I've installed. maybe its for the sake of routine. in this case, its trannies and rust autism.

>>107159827
this
alternative implementations independent of each other inspire a lot more trust than a bunch of faggots spouting pseudoacademic nonsense on their child grooming forums

>>107159827
>>107159908
This. Never forget 1984, bros.

>this 1984:
https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf

>>107155502
so companies can use it without having to contribute anything back

Decades ago it was absolutely necessary to optimize software as much as possible due to hardware constraints. Newer software is so lazy and bloated that they need to move the goalposts to not look like absolute retards in comparison.

>>107156009
There's no Rust spec so it doesn't matter how turbo autist or phded you are. How could you write an independent implementation?