• 14 Posts
  • 1.12K Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle




  • Coming at it from the Rust ecosystem, I’d primarily opt for uploading release binaries somewhere. You don’t particularly need a setup script, since Rust programs are generally self-contained.

    Publishing a package in addition to that really isn’t hard, but would be my secondary choice, since users are not likely to have cargo on their system.
    Well, and cargo compiles on the target machine, which is great for supporting unusual architectures, but you may have C libraries included where it’s just a gamble whether you can compile them on a given target system.


  • Ephera@lemmy.mltoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    12 days ago

    Should perhaps add that you can generally run Linux distributions off of a USB stick for that first impression.

    Just follow a tutorial for how to install Linux and when you see the actual installer on screen, you can just close the installer without installing and then click around in the UI.

    It will be slow, because it’s running off that slow USB connection, but otherwise this is pretty much the operating system as it is when fully installed.


  • I do enjoy how much time they spent explaining that mommy and daddy are not arguing. Makes it feel all the more like they’re arguing.

    Really doesn’t help, though, that they are effectively saying “stop doing that right now and explain yourself”.
    Like, man, what predates this post? Did they ask the JIT devs before to submit a PEP and they just didn’t do it?

    I will say, a lot of this impression comes just from how open-source works.
    You can’t really go up to someone privately before you make the conflict public, because all communication is public.
    And of course, many people are involved here. Setting a deadline and all that helps those people to actually get coordinated. Maybe the folks on the Steering Committee just know that to be the case…










  • Had a refinement yesterday, where we decided that we should add all tickets of an epic individually into the milestone (except for two).
    And for whatever reason, our project manager had decided to use the in-browser split view and was struggling against that, but also just was about to do it in some cumbersome way. I think, he wanted to manually compare the list of issues in the epic vs. the milestone.

    Either way, I could tell that he’d need 10+ seconds to even get started. And telling him how to do it would probably take equally long. So, I just open each issue of the epic in a new tab and check on each tab that the issue is in the milestone or add it, then close the tab. And yep, I was long done when he was still trying to find the issue list for the milestone.

    That was certainly one of those moments. 🫠

    He isn’t entirely familiar with that issue tracking UI, so it’s fine, and of course, it is my job to be good with computers and all that, but still felt wild that he could’ve easily needed ten times as long to do the same thing.



  • Last week, some LLM bot commented under one of our issues and it became apparent pretty quickly, that it is a bot. So, I went to report it (incredibly the report menu did say they want reports for bots).

    I filled out the reporting form probably five times in total, trying at different times of the day. Every time, I got an error 500 (Internal Server Error) as response.
    Later, I checked my mails, and saw that actually two of my reports did go through, meaning I created two tickets on their side.

    What those mails also said: They’re very sorry, if it takes longer, since they’re currently experiencing a higher number of reports.

    Gee, I wonder why.