Web Developer by day, and aspiring Swift developer at night.

  • 13 Posts
  • 669 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle






  • GPLv3 is virally open source (copyleft), BSD 2-Clause is not.

    Your first statement is patently false and misleading.

    Two variants of the license, the New BSD License/Modified BSD License (3-clause), and the Simplified BSD License/FreeBSD License (2-clause) have been verified as GPL-compatible free software licenses by the Free Software Foundation, and have been vetted as open source licenses by the Open Source Initiative. (Wikipedia)

    Being “copyleft” is not a requirement for being open source. Maybe you’re thinking of free software. There are differences, but as the FSF is quoted, they are also very similar.

    GPLv3 ensures free software remains free and contributions cannot be exploited and withheld from the community. BSD2C does not.

    To my understanding, and if I’m wrong I’d love to know why, both GPLv3 and BSD2 both ensure the openness of software. They just go about it differently. GPL (I’m not super versed at v3) basically means any modifications to GPL’d code must also be GPL’d, and source made available; also, if you statically link against other GPL’d code, your code must be GPL’d. Dynamic linking (or linking against LGPL code, like glibc) does not have this requirement.

    With BSD code, your only requirement is that the code (or binaries) must remain BSD2. Sure, someone can make modifications and keep them to themselves for fun and profit. But that doesn’t mean the rest of the community has to follow suit. The original code remains open and available with no license modifications. If a company owns BSD2 code, and goes under, the community can simply fork the code and take ownership as they please.

    Neither license is perfect, and I’m sure we could find plenty of examples of people/companies that have abused both licenses.





  • Not true. Look up the Americans with Disabilities Act (ADA) by the EEOC. Here, I’ll do it for you. But if I am mistaken, I’d love to know where it defines the vision criteria for exclusion.

    Actually, when I was looking it up, it sounds like you’re talking about being considered legally blind and qualifying for Social Security disability benefits, which is not the same as being protected under the ADA.






  • dohpaz42@lemmy.worldtoMalicious Compliance@lemmy.worldWork from home
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    1
    ·
    2 days ago

    According to the EEOC, it’s a disability:

    A vision impairment does not need to “prevent, or significantly or severely restrict,” an individual’s ability to see in order to be a disability, as long as the individual’s vision is substantially limited when compared to the vision of most people in the general population.

    And it sounds like her employer is doing the right thing. But if ever she feels she is not being treated fairly, she should talk to a lawyer to be sure. Don’t just let it slide because she has one good eye. Hell it might be good to talk to a lawyer anyway, so she knows what to look out for in the future if things happen to change.





  • I’m probably going to get a lot of hate for this, and I do recognize there have been problems with it all over the place (my code too), but I like null. I don’t like how it fucks everything up. But from a data standpoint, how else are you going to treat uninitialized data, or data with no value? Some people might initialize an empty string, but to me that’s a valid value in some cases. Same for using -1 or zero for numbers. There are cases where those values are valid. It’s like using 1 for true, and zero for false.

    Whomever came up with the null coalescing operator (??) and optional chaining (?->) are making strides with handling null more elegantly.

    I’m more curious why JavaScript has both null and undefined, and of course NaN. Now THAT is fucked up. Make it make sense.


  • dohpaz42@lemmy.worldtoProgrammer Humor@lemmy.mlWorst is UTC vs GMT
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    3 days ago

    You obviously don’t suffer from a sensitive circadian rhythm. To that I’d say, lucky you. But there are plenty of people who do suffer. And by the time they finally get used to the time change, it’s time to change again. It’s vicious and disruptive; to more than just scheduling. It has a direct (negative) impact on physical and mental health.