• 0 Posts
  • 32 Comments
Joined 22 days ago
cake
Cake day: April 20th, 2026

help-circle





  • Not sure, if you’re actually looking for an explanation or rather just want to rant and/or hope for dating tips, but maybe still helpful to be aware of:

    Diagram of a normal distribution

    With your specific expectations, you’re somewhere to the far left or far right, whichever way you want to read it.
    For example, this graph could be applied to alcohol consumption, with 0 on the left and lots on the right. Then you’re on the far left.

    The Y-axis shows how many people exist in that range. There’s some median alcohol consumption, which is going to be in the center of this diagram, where most people are. At 0 alcohol consumption, there’s very few people, because it’s an extreme.

    Obviously, this simplifies a lot. In a real survey, there’s probably actually somewhat of a bump at 0 alcohol, because certain religions prohibit consumption.
    But yeah, in general, you’re hoping for relatively many extremes, so the number of people that match that are quite low. You will naturally get magnitudes more romantic interest from Average Joes, because there’s just magnitudes more of them.

    As somebody else already said, try to find groups that naturally attract folks from the extremes that you look for, like outdoor sports groups.
    Online dating, as problematic as it is, can also be rather good at finding very specific extremes.


  • trem@lemmy.blahaj.zonetoAsk Lemmy@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    6 days ago

    You can’t generally just add license terms to an open-source license. At that point, it is not anymore an open-source license, but rather your own custom (a.k.a. proprietary) license.

    As in, there’s a list of license texts that are approved by the Open Source Initiative and you don’t really want to deviate from that. (There’s also a list by the Free Software Foundation for the more freedom-loving among us, which is rather similar and also valid.)

    This also has larger legal implications. There’s been lawsuits for open-source licenses, to which you can point and tell a company to fuck off, if they do a similar violation. As soon as you start adding own terms, there can be contradictions and just generally surface to attack.

    In particular also, most code exists in the form of libraries. If you’re a library and you want users, you do want to stick to the well-known licenses, because no one wants to deal with each library having different custom terms (considering you can easily end up using hundreds of libraries in an application).


  • Hmm, that’s interesting. Don’t you guys generally use concrete for paving in the US? In building construction, you’re supposed to give concrete like a month to fully harden, even though it already looks firm after a day or so.

    For paving, they’re likely using a hardening accelerator, so the timelines wouldn’t be the same, but if building construction is anything to go by, it seems like you’d want to give it as much time as possible, not send cars on there while it’s still hot. 🥴




  • The old “tomatoes are not a vegetable” is pretty frustrating. They are a vegetable.

    In botanical terms, the concept of a vegetable does not exist, which is where tomatoes are classified as fruits. But in culinary terms, vegetables do exist and tomatoes are classified as such.

    I just find it frustrating, because I believed that garbage myself at some point, and I thought, I was smart for knowing that.
    Just one of those examples that you can easily spread misinformation, so long as you make it sound plausible.






  • Also worth mentioning that universities generally see themselves as research facilities first and foremost. They teach students, because they want to get the next generation of researchers.

    Sure, they’ll also do job training to some degree, because it’s a good argument to get more funding, but yeah, just not their primary goal.





  • You’re right that there is a risk, that rebasing introduces compile errors or even subtle breakages. The thing is, version control works best, if you keep the number of different versions to a minimum. That means merging back as soon as possible. And rebases simultaneously help with that, but also definitely work best when doing that.

    There may be reasons why you cannot merge back quickly, typically organizational reasons why your devs can’t establish close-knit communication to avoid conflicts that way, or just not enough automation in testing. In that case, merges may be the right choice.
    But I will always encourage folks to merge back as soon as possible, and if you can bring down the lifetime of feature branches (or ideally eliminate them entirely), then rebases are unlikely to introduces unintended changes and speed you up quite a bit.