Comments by "George Albany" (@Spartan322) on "Brodie Robertson" channel.

@terrydaktyllus1320 There's a lot of things that are broken with xorg, just because you don't feel a UX break doesn't mean it isn't broke, we don't define broken by what the user of the software feels is broken.
1
I'll never get the desire to "stable release" alpha and beta functionality.
1
@zxq_5 ABI stability, proper support for shared libraries, dynamic linkage, and static linkage that doesn't routinely break. There is no feasible reality for which any language should sacrifice ABI stability if its supposed to be stable, glibc causes enough issues in userspace when it breaks it, Linus gets routinely mad at them for this, (and if Rust is adopted, he'll be doubly mad at the Rust standard library because its even worse) the chaos of having an entire language library that is freestanding (which Rust also does not work with) which breaks ABI is an insurmountable problem. Just because we have a new fancy language does not mean we get to ignore the rest of software needs. There is never a justification to break ABI at any level of the standard library, any standard that doesn't comply with this will be worse then the C++ standard any serious software project.
1
Gnome is dumb anyway.
1
To be honest, a distro is only a single distro until its installed on your computer, then its a totally new distro, 95% of a distro's distinction is the install script and package distribution host, and majority of those still at some point will or can redirect to the parent distro's package distribution, (Mint, Ubuntu, Manjaro) dumb thing is when a distro makes its own custom install systems that make it different in slight ways, like how Manjaro screws with all the popular packages on Arch for no reason which causes install breaks, even had programs utterly crash because I used the Manjaro packages, like what is the point of overriding the packages that already exist, could just addon to the package in the main package distribution host anyway.
1
@poly9306 And how are those behaviors being introduced into the spec? Why does everyone have their own non-spec conforming implementation?
1
I'm excited to know the next list of disappointing things our favorite distro punching bag Manjaro is gonna screw its consumers over with again.
1
Probably for a a goop many more years tbh, Wayland will take a lot longer then pipewire to functionally replace X11.
1
Truthfully I think Linus is a fool, my biggest issue with him is that all tools must be all or nothing, his software perspectives have a lot of stupid presumptions, like his perspective on C++ in the kernel was absolutely dumb, yes sure C++ exceptions and RTTI is a pain, there are definitely annoyances with C++03 and before, but you can disable both on every compiler, its an unfortunate requirement of the standard that both be supported (making them optional extensions would be a lot better) and you can use C++ without the standard library if necessary, plenty of FOSS projects already do, the only really big backing behind Linus having beef against C++ is because he's a C fanatic and was frustrated with C++03. (even though it was still better then C) RAII and simple span-like types were completely feasible even going back to C++98, and it would've saved a lot of headaches in the Linux kernel. C is a worse language then C++, Linus has never once made a valid complaint of C++ and I would love to say this to his face and call him out for being an idiot. Literally everything that can be written in C and be written in C++ almost exactly, you can even selectively disable name mangling in C++ when you need a C API, you don't need to use anything that bloats your compilation nor your binaries if you disable RTTI and exceptions.
1
@Poldovico Yeah but the big issue is that nobody questioned the binary files being included in the build process (regardless of the fact they were test files) even just for testing purposes, had that not been accepted, it wouldn't have been possible for that backdoor to even be made, any other backdoor would've required being written in the source code or somehow constructed completely from the build system, something that is more able to be validated by code review. (and at that point it often becomes impossible to distinguish between bugged code and malicious code)
1
@necoji4910 Okay cool, if you can't read what I wrote, there is no point dealing with you, this is a Youtube comment section not a bachelor thesis. Nobody cares about run on sentences.
1
@CamaradaArdi Its not entirely, its better, but it definitely still takes longer then not having one at all.
1
librewolf masterrace
1
Especially when the only people that will care about FUTO would've been mostly the fans of the OSI definition of open source, but by attacking the OSI definition and trying to make it more inclusive they are shooting themselves in the foot ensuring nobody will care about FUTO.
1
Honestly probably better then bricking your system every other week when you need to use the AUR Manjaro, but you'll never have the AUR packages then, which sucks for all but the most basic of cases.
1
Some of these issues are functionally fabricated for twitter, like performance has nothing to do with Elon and the only way that would be relevant is if one of the other scenarios happens first, (especially moot since Elon was trying to fix long standing issues at twitter related to this and it didn't kill the platform) making it a moot point anyway since if one of the other scenarios that crashes the network or infrastructure happens, a slow app is the least of your damn problems, and as for moderation tools, those still exist regardless of the moderation team, and has nothing to do with the copyright system because it was automated anyway, they just broke the copyright detection. And there are plenty of things he did not mention that don't apply to twitter in a danger scenario despite applying to a tech conglomerate.
1