• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • There is no section 15 or 16 in GPLv3, but I did find section 7 saying:

    Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or

    But that’s an optional thing that you must add onto the GPLv3 license. I’ll have to keep that in mind for the future.

    That would explain why what I’ve read mentioned it’s not guaranteed in GPLv3 (when comparing to MIT). I’ll have to figure out what that notice would look like.



  • I don’t care if people make money to use my code. I just want my name attached to it somehow, even if you make it closed sourced which is MIT and OpenBSD. I hope you do use my code and even if you heavily reference it to make something new, carry that forward so more can learn and benefit.

    I also don’t understand “better for the end user” arguments either. I have a library that people want to be included in another project, but that project is GPL. They won’t merge my code unless I change my code to be GPL. So everyone who wants them merged is out of luck. I can’t merge their code either with mine. What is supposed to happen is I freely give up my name to the code and restrict it to only being GPL and for GPL projects. Essentially, assimilate and join with the Borg. No, thanks.

    And while that’s from my experience, I’ve also seen good projects get traction, have excitement over it, and fall off the earth because they end up making it GPL. Everyone interested in adopting it, personal or business, just disappear. Then something with less restrictions comes along and gets adopted.

    End-users move to what’s better for them, and if you have a library that is only for GPL, you can end up limiting your options with a wasteful purity test. If you want it to be free you’d give freely with no restrictions. And if you think, “You can contact me to discuss licensing” that doesn’t happen. It’s still a restriction and almost nobody actually bothers.








  • ShortFuse@lemmy.worldtoFirefox@lemmy.mlHow about no?
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    6 months ago

    Definitely not.

    I have to version check to workaround Chrome, FireFox and Safari bugs. Some things they fix and I can flag around version (eg: FF113 has buggy focus detection with Web Components), but some just have never been fixed (eg: Firefox does not support animated styles with CSS variables in Web Components).

    That’s not to pick on FireFox. Chrome doesn’t support scrolling two elements simultaneously which breaks any type of fancy horizontal scrolling in horizontal tabs. Safari has some buggy implementation with ARIA tags for Web Components and [type=range] doesn’t follow spec for min.

    If we were going to just not support new features because browsers are buggy, we’d never get any new features. It’s better to feature detect and that includes knowing what versions need workarounds.