• 1 Post
  • 133 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?








  • But that’s the neat thing: the system is well structured into different layers and subcomponents. They are not all involved to control lightbulbs; that’s mostly your local hue bridge. One component will make sure, Alexa can control your bulbs (if you want that). If that component fails, only Alexa stops working. Another component handles push notifications to your mobile devices. If that fails, the rest is unimpacted. And so on.

    That was, for a long time, the main reason I heavily recommended Hue: the bridge can be used completely offline and still offered a good local API and pairing system. Unfortunately last year that made online accounts a requirement. I assume besides the App you can still use many things even if your network connection is broken, though.










  • glibc’s malloc increases the stacksize of threads depending on the number of cpu cores you have. The JVM might spawn a shitload of threads. That can increase the memory usage outside of the JVMs heap considerably. You could try to run the jvm with tcmalloc (which will replace malloc calls for the spawned process). Also different JVMs bundle different memory allocators. I think Zulu could also improve the situation out of the box. tcmalloc might still help additionally.


  • I ran Arch on a convertible laptop around 2006-2010. Most notes I did using OpenOffice Writer, with hotkeys to quickly add formulas. Drawings were done with the pen. Homework (where speed didn’t matter as much but where I wanted high quality) were done in ConTeXt.

    Programming was done in FreePascal using Lazarus IDE or Java using Netbeans IDE, depending on the course and my personal preference.

    I think I had no complaints from anyone. Quite the contrary, one professor even gifted me a book as a thanks for the high quality typesetting in my homeworks, since most students didn’t give a shit and had no fucking clue how to really use their beloved MS Word.