• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: January 17th, 2024

help-circle

  • I can understand Hellwig’s fear, though.

    From what I gather as a bystander, it’s apparently common that a refactoring in your module that breaks its API will involve fixing all the call-sites to keep the effort on the person responsible for the change. Now the Rust maintainers say “it’s fine; if it breaks, we’ll deal with it” which is theoretically takes away the cross-language issue for the C-maintainer. Practically I can very well see, that this will still cause friction in the future.

    Let’s say such a change happens and at that time there’s a bit of time pressure and the capacity on the rust maintainers is thing for whatever reasons. Will they still happily swallow that change or will they start to discuss if it’s really necessary to do that change? And suddenly, the C-maintainer has a political discussion on top of the technical issue they wanted to solve.

    As someone who just wants to get shit done, I would definitely have that fear.

    (That doesn’t mean it’s still a bullet not worth swallowing. The change overall can still be worth the friction. I am just saying that I think it’s not totally unwarranted that a maintainer feels affected by this even though current pledges from the other parties promise otherwise; this stance can change or at least be challenged over and over.)


  • It was an example. I don’t have a fucking clue how all the maintainers are named.

    The main question was: why can a maintainer NACK something not in their responsibility? Isn’t it simply necessary to find one maintainer who is fine with it and pulls it in?

    Or even asked differently: shouldn’t you need to find someone who ACKs it rather than caring about who NACKs it?









  • Heh, yeah. I had to fix that earlier this year on another machine, but that one was ooold and went through a bunch of upgrades so I figured it was due to its age (even though I still didn’t get how they could be so lazy to not automate this process as part of the update or … well… slim down the rescue tools again). But then they apparently didn’t even care enough to release a new installer that prevents the issue. So they either don’t give a crap or even do it deliberately to break Win 10 in favor of Win 11. Either case: that’s not what I pay for.


  • Just this weekend I had the pleasure of installing Win 10 on a blank disk. The install went ok, but then it bothered me logging into the MS Account. After cursing for a while and since it wasn’t my PC, I gave in. I know I can fight it, but it’s not worth it here. Then it continued trying to get me to consent to all kinds of shit. NO, I DON’T WANT FUCKING OFFICE AND I DON’T WANT MY FILES IN ONEDRIVE you assholes!

    Then it forces me to choose a PIN for “secure login”. DUDE! That motherfucking PC is used for a bit of office work and gaming. Just let these poor people boot up the machine and use it! 0000? Too simple. 1234 too. Fuck you, MS. Ok, random PIN and a sticky note it is, asshats.

    Anyway, after getting it to fuck off, I continue to the desktop. Oh wow, 10 updates and a ton of missing drivers? It’s a fresh install! What the fuck did it install?! Of course the installation of all these updates takes an hour and countless restarts… AFTER A FRESH INSTALL! Not even my overblown super slow Ubuntu server takes that long for updates; and that runs on a HDD not a SSD like that PC I set up.

    But wait. One update failed. Why? Ah, the rescue partition is too small… THE ONE THAT DUMB SON-OF-BITCH CREATED ON ITS OWN AS PART OF THE INSTALL! How to fix? Ah, execute a bunch of commandline foo with diskpart and other tools. Wait, isn’t that exactly the kind of shit that Windows fans laugh about when looking down on us Linux nerds?!

    So … ugh … just one simple anecdote of why Windows can fuck off.