4 ms·

I'm more familiar with luajit than Lua itself (as a project I mean). I'd be curious to know more about the fragmentation that vanilla Lua has. I know the issues

I'm more familiar with luajit than Lua itself (as a project I mean). I'd be curious to know more about the fragmentation that vanilla Lua has. I know the issues that the luajit devs have with the features themselves but I wonder how and why those are decided and implemented. Is there an article or blog that goes into more details? Google isn't helping me here haha.

wruza 2y ago
It’s from a simple fact that there are rocks that were not maintained seriously (as in “business”), and there are big embedders that work as version anchors. As a result, rocks were full of 5.?-specific at the times of 5.2/3, cause people have no time nor desire to reimplement things. Idk how it is now, but my bet is on nothing changed, some popular libs became multi-headed. Lua-http doesn’t even list 5.4 as a target. Maybe 5.4=5.3, can’t remember. But if daurnimator decided to ignore it, oh my. As of motivation, I guess the best source is their mailing list around release dates. It was hot every time. Idk if anyone blogged about it, maybe just ask there.
- daurnimator 2y ago
  hmm? https://github.com/daurnimator/lua-http/commit/54606a9d3fea9780468601ed0c8be48748e97204 https://github.com/daurnimator/lua-http/commit/54606a9d3fea9...
  - wruza 2y ago
    Ah, visited this first, sorry for the noise https://daurnimator.github.io/lua-http/0.4/ https://daurnimator.github.io/lua-http/0.4/