4 ms·
JGC tweeted me about how 'Oh, we get so much benefit from LuaJIT being FOSS" And we do. We paid Mike Pall to work on open source LuaJIT, we've contributed to N
by jgrahamc 11y ago
JGC tweeted me about how 'Oh, we get so much benefit from LuaJIT being FOSS"
And we do. We paid Mike Pall to work on open source LuaJIT, we've contributed to NGINX, hired people to exclusively work on open source projects. Here's the harsh economic reality: it is simply better business for us to spend a relatively small amount of money on open source support to get what we need from fantastic projects like LuaJIT than to try to develop this stuff ourselves.
My worst fear is CF taking this project into the shadows, developing it closed-source (which they absolutely have a right to do) and not sharing their insights with the community.
How do we "have the right to do" that? Whatever makes you think us trying to closed source this would have any benefit to us? How is the Github account (of which Mike Pall is an owner) us walling it off?
More than that, I don't think there has been enough narrative between Mike and the 'new LuaJIT crew' (CF) to determine how the project should be structured.
I predict that if I hadn't sent an email to the list soliciting ideas and input and had announced a new structure you would have complained that everything had been done in the shadows.
- logicrime 11y agoEverything IS being done in the shadows!! All you've done is write a few paragraphs about how great the community is, and make a repo. CF's work on nginx is of no concern to me, and even less so is the tendency of CF to hire people to work FOSS projects. Big deal. Nobody that's reading this is stupid enough to believe that it's out of the realm of possibility to spend some money on your image. What you've said about LuaJIT all but confirms my suspicions that CF will suck the project dry for efficiency until it's a dry withered husk. You are shoehorning developers at CF into LuaJIT the same way that Google shoehorns developers into the Chromium project. What ultimately happens is the work that gets done in Chromium ends up being misused in Chrome as a commercial bloat whose function is to extract and extrapolate as much as it can about the user. The user's intention is just to browse the web smoothly, and they get taken for a ride. LuaJIT is meant to be a performance implementation of Lua, suitable for embedding within larger applications and games as a DSL. At this point in time, I would absolutely stand behind the argument that CF seeks to turn LuaJIT into a more standalone project that leverages CF's infrastructure to make CF even more money. I just can't abide, and I certainly can't believe that you expect the community to watch this happen as you systematically corporatize a well-loved, well-used, well-done project.
- redxdev 11y agoWhere is the proof that CF is doing anything remotely like what you say? All they've done is create a Github repo (which is many developers preferred platform) and say that they are moving to a more distributed governance model. All at the request of the original maintainer, Mike Pall. They've even explicitly stated that CF will not be taking over the project; they're only helping move it to a new home and to find a group who can maintain it to replace Mike Pall. There's zero evidence that CF's intentions are to the contrary, so I do think what you are saying is completely unfounded. Please correct me if I'm wrong.
- nitrogen 11y ago[Responding here to the parent flagged comment] While logicrime's comments may be wrong and a bit over the top, I don't think this comment should have been flagged. We've seen a well-explained criticism of a potential, if unlikely, future. These comments are much less inflammatory than other comments that have been left alone on HN. I still plan on embedding LuaJIT into my automation software, so I personally look forward to to seeing what CF and any LuaJIT successors produce. So let's take logicrime's fears into consideration instead of just shutting them down. Thanks for looking after LuaJIT, jgc and CF!