Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)UB
Posts
6
Comments
1,534
Joined
8 mo. ago

  • Apparently, it hasn't happened. Because nobody else beside R4L is helping it along.

    Sorry, but ya'll just have more work to do, is all. Do it, or don't, I don't care. I honestly don't care one iota if Rust ever gets in the kernel, or not. What I do care about is that the Linux kernel remains a stable project.

    Take the advice, or don't. Its on you.

  • And, again, prove him wrong, maintain a tree that shows it's workable, and with minimum maintainability concerns. If there truly are minimal maintenance concerns, a separate tree would be quite simple to maintain!

  • The maintainer literally says the issue is that there are two languages. There is no way to convince them, there’s nothing anyone can do.

    Sure there is! Maintain your own tree, like I said. Eventually, it'll be proven to be workable. Or not.

    The maintainer didn’t say “I worry about the maintainability, please prove that it works outside the tree” (this concern was already discussed when the R4L experiment was officially OK’d). They are explicitly saying they’ll block Rust in the kernel, no matter what.

    No, they aren't. They are blocking how it's being done, with R4L folks wanting to toss the maintenance headaches over the wall, for someone else to deal with, because they don't want to build their own C interfaces, that match the already existing ones.

    I don’t know how to better explain this to you.

    Try to understand the problem better, so maybe you'll be able to understand why maintaining your own tree to prove the conceptual implementation works, and doesn't hand maintenance overhead to another party.

  • I already did: maintain your own tree, and prove it out, that it's better.

    If the maintenance load is so light, it'll be easy work to do, to keep the tree in line with upstream.

    If it's so obviously technically better, people will see it, and more people will push to mainline your tree.

    It's work. And you need to convince others on technical merit. So, do the work.

    Just like what folks did with OpenBSD, the grsecurity tree.

  • but what can stand in the way of wholesale dismantling of the democratic process

    An armed, and radicalized proletariat.

    This is a major difference between fall of the USSR Putin, and the US of A today - We have a fucking lot more guns in the hands of civilians than they had in Russia. Remember, anything besides a shotgun was essentially banned in Russia.

    And, historically, when things hit "Great Depression" levels of bad... We use them, oddly enough, to benefit our comrades in the working class. For example, Deacons for Defense, or Penny Auctions.

  • The 21st century tech oligarchs are more powerful than nations.

    No, they aren't. At least not most nations.

    Unless a 21st century tech oligarch is able to pinpoint their enemy's position to within 10m, and send a Drone Strike to take them out? Then no.

    Because right now, Trump could rid us all of Elon, should he choose, with merely an order.

  • This is not the Democrats fault.

    No blame goes to the Dems at all?

    None?

    Not even any blame for running bad campaigns, with bad candidates? Three times in a row? No blame for relying on "Not Trump" as a campaign strategy? No blame for insisting the economy is grand, even though all the voters are saying otherwise?