(no title)
logicrime | 10 years ago
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|10 years ago
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|10 years ago
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!