1. 11
  1.  

  2. 7

    We don’t know! There are a couple of barriers to open-sourcing this work […] This is not off the table - but no immediate plans either. Again, time will tell.

    Oi vey. For a game that relies so much on unpaid software development labor by its own users, they could at least give a little back to the community. I’m almost ashamed that Roblox game-making was a path into programming for me as a kid; it’s a weird microcosm of the worst of “open source”.

    1. 3

      I’m almost ashamed that Roblox game-making was a path into programming for me as a kid; it’s a weird microcosm of the worst of “open source”.

      I think game modding in general seems to be a vortex of that. A single thread, some stickies (often reserved) at the top, and throwing tarballs over a fence. I was relieved when I saw a mod using git mostly properly for once!

      1. 2

        This is really interesting to me, as someone who spends most of my video-game-playing time in Kerbal Space Program. Everyone uses GitHub as project management, most things are properly licensed, and we even have a nice package manager.

        What I was really referring to, though, was that they foster a culture of people giving them stuff for free and then never contributing anything back.

      2. 1

        Yes, I agree completely - and I don’t see the excuse given of ‘wanting to protect our customer/developers from decompilers’ as being of much substance either, given that the point of having all of this be open-source in the first place is that the customer/developers would be able to see where the weaknesses are, also, and make that decision for themselves (or: come up with contributions to improve the scene).

        And, on that subject - contributing to improve - I totally fail to see why they don’t just grave-dig LuaJIT’s efforts, and add some commercial/open-source energy to the project - especially since they seem to want to take some of the other gems of the LuaJIT community for their own.

        This all just reeks of grand-standing and bike-shedding. But I say that as a grumpy Lua developer where, because Lua is just so fucking great, such endeavours are the norm.

        1. 1

          Not sure I’m super clear on the LuaJIT-being-dead thing, just the other day I was reading docs for the OpenResty fork, which has commits from only 2 weeks ago, and the README mentions syncing with upstream. Has it died super-recently? Or is more that it’s not had any changes for a couple years?

          1. 2

            I think its more like a NIH syndrome conclusion - basically “I don’t see enough activity recently to satisfy my curiosity as to the state of this software, and I’m too lazy to evaluate the condition on the basis of source reading - so if nobody is showing up lately to fix things, ‘it must be abandoned’” ..

            1. 1

              Makes sense. Even if it’s just “nothing needs fixing right now” :-)