Announcement

Collapse
No announcement yet.

Updated GNU Framework Tries To Push "Free JavaScript"

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Updated GNU Framework Tries To Push "Free JavaScript"

    Phoronix: Updated GNU Framework Tries To Push "Free JavaScript"

    Out this Sunday is a major update to GNU ease.js, which relicenses this JavaScript framework to the GPLv3 and has several other changes. GNU ease.js helps the Free Software Foundation's case for the "importance of free JavaScript" on the web...

    http://www.phoronix.com/vr.php?view=MTYzMjE

  • #2
    Perhaps I'm not thinking Free enough, but to me JS has bigger problems than non-free code: bloated libraries and clueless JS devs.

    Site needs one small function, that transplanted would take 200 bytes, yet they include several megabytes of JS libs.
    Site overuses JS, making it extremely laggy.
    The quality of those frameworks in general is questionable: jquery for example drops browser support way too soon.

    Comment


    • #3
      The old Opera actually had userscript commands that would allow you to intercept any script and replace it.

      Comment


      • #4
        You should put quotes in italics, sometimes I'm not sure if something is a quote or not.

        Comment


        • #5
          GPL v3 question

          Does this mean that ease.js cannot be used without also divulging all the source code for any server-side components? I'm hopefully confusing this with Afferro...

          Or does this only require all other front-end JavaScript source code?

          Comment


          • #6
            Originally posted by curaga View Post
            jquery for example drops browser support way too soon.
            AFAIK they have no intention to EOL the 1.x branch that supports all the way back to IE6. I am a little sad that 2.x drops IE8 as I have to support that one

            Comment


            • #7
              Originally posted by jokeyrhyme View Post
              Does this mean that ease.js cannot be used without also divulging all the source code for any server-side components? I'm hopefully confusing this with Afferro...

              Or does this only require all other front-end JavaScript source code?
              This ^ is actually a very good question. From a legal standpoint are the scripts, the document, styling, and server side components all considered separate entities (in which case it should effect just the scripts) or are they all a singular "work" (in which case it would effect the entire webpage), or has this even been established by anyone?

              Comment


              • #8
                It's pretty naive to assume that a more restrictive license will make people open up their code. There are tons of JavaScript frameworks. In the best case, developers that use ease.js will migrate to another framework without silly license terms. In the worst case, they will ignore the license terms.

                Comment


                • #9
                  Originally posted by curaga View Post
                  The quality of those frameworks in general is questionable: jquery for example drops browser support way too soon.
                  Are you serious? Sure, the 2.x branch drops support for IE8 and before - precisely to reduce the bloat you're talking about - but the still-maintained 1.9 branch still supports IE6, for god's sake. And you accuse them of dropping browser support too soon?

                  Comment


                  • #10
                    Originally posted by AJenbo View Post
                    AFAIK they have no intention to EOL the 1.x branch that supports all the way back to IE6. I am a little sad that 2.x drops IE8 as I have to support that one
                    If you need IE8 support, then just keep using the 1.x branch. You shouldn't be sad that 2.x dropped IE8 support, because ditching "difficult" browsers like IE8 is the entire reason for 2.x to exist.... providing a leaner version that doesn't have to include the overhead of supporting those older and less-compliant browsers. Because IE9 is really the line in the sand, the point where IE became "good enough"... something that could be treated as just another browser variant instead of some abomination that nobody wants to deal with...

                    Comment


                    • #11
                      Originally posted by Delgarde View Post
                      If you need IE8 support, then just keep using the 1.x branch. You shouldn't be sad that 2.x dropped IE8 support, because ditching "difficult" browsers like IE8 is the entire reason for 2.x to exist.... providing a leaner version that doesn't have to include the overhead of supporting those older and less-compliant browsers. Because IE9 is really the line in the sand, the point where IE became "good enough"... something that could be treated as just another browser variant instead of some abomination that nobody wants to deal with...
                      No i'm just sad that i have to support it... or that it is shit, take your pick

                      Comment


                      • #12
                        Originally posted by AJenbo View Post
                        No i'm just sad that i have to support it... or that it is shit, take your pick
                        Fair enough... I certainly can't dispute that. IE8 was much better than it's predecessor in terms of standards compliance, but still pretty deficient compared to, well, everything that wasn't IE.

                        Comment


                        • #13
                          Originally posted by Delgarde View Post
                          Fair enough... I certainly can't dispute that. IE8 was much better than it's predecessor in terms of standards compliance, but still pretty deficient compared to, well, everything that wasn't IE.
                          The situation is made much wheres by MS's odd policy of only supporting IE on the latest two of there active OS's, yet supporting them for the life time of the OS they launched with (IE8 came with Win7 so it's going to hang around for a long time, IE6 will end in april!). Everybody else mange to have feature parity on all of supported Window versions, as well as other OS's. IE11 is missing major features like SPDY on Win7!
                          Last edited by AJenbo; 03-17-2014, 12:10 AM.

                          Comment


                          • #14
                            Originally posted by AJenbo View Post
                            AFAIK they have no intention to EOL the 1.x branch that supports all the way back to IE6. I am a little sad that 2.x drops IE8 as I have to support that one
                            That won't help you when $RANDOM_SITE you have no control over uses the latest shiny.

                            @Delgarde

                            Not talking about IE support, talking about Opera and FF support. Major-1 is too little. Consider the LTS Firefox version for example, that would often be unsupported by jquery.

                            Comment


                            • #15
                              Originally posted by curaga View Post
                              That won't help you when $RANDOM_SITE you have no control over uses the latest shiny.
                              What does that have to do with what you quoted? Besides, if you're using IE8 and that $RANDOM_SITE doesn't support your browser you can upgrade or go elsewhere. The site owner clearly doesn't care about you.

                              Originally posted by curaga View Post
                              Consider the LTS Firefox version for example, that would often be unsupported by jquery.
                              Unsupported doesn't mean it won't work. It means they're not writing tests to make sure that it does. Given that Chrome and Firefox are only incrementally changing between versions it's probably not going to matter anyway.

                              Comment

                              Working...
                              X