5 ms·

Highlights include an api for a built in Lua(JIT) : https://github.com/neovim/neovim/pull/4411 https://github.com/neovim/neovim/pull/4411

kosinus 9y ago
Isn't LuaJIT stuck on Lua 5.1, and no longer in development?
- rijoja 9y ago
  excellent opportunity for somebody to step up!
  - wruza 9y ago
    First of all, it was never unmaintained, and has two parts: interpreter and jit-compiler. The interpreter is rock-hard and was battle-tested in many production environments for years. There is nothing to do in it anymore[1]. Jit part is under active development. For one, among many others, they recently patched GC to remove the famous 2Gb memory restriction for LuaJIT. Jit was also always production-ready, but their sense of “ready” is too responsible, so their current version is beta3. [1] yeah, the language doesn’t have to change and “evolve” constantly, if its roots were planned thoroughly.
- _dcwr 9y ago
  It's 5.1 compatible plus some nice-to-haves from 5.2: http://luajit.org/extensions.html http://luajit.org/extensions.html I wouldn't call it 'not in development' and even if, then 5.1 is a fine version of Lua and LuaJIT is battle tested very well and rock solid still. Changes in Lua 5.2 and 5.3 are breaking (and some are deep, like the ints, bit ops, function environments) but most of 'usual' code is compatible between 5.1, 5.2 and 5.3. I learned Lua 5.2 and then went back to 5.1 when 5.3 came out because I didn't like the int stuff in 5.3 and didn't want to use an obsolete version (5.2) with no upsides (5.1 has the upside of being compatible with LuaJIT).
  - vog 9y ago
    To those who downvoted FRex's comment: Do you care to elaborate? I don't see anything wrong with it. (And it's definitely more insightful than the slightly older sibling comment, which apparently has not been downvoted.)
    - oblio 9y ago
      Maybe someone fat-fingered it?
      - vog 9y ago
        No, it had more than one downvote when I upvoted it, i.e. stayed grey after upvote. Moreover, I just saw it being black, then grey, then black. So it still receives a mix of downvotes and upvotes. Very strange.
      - aidos 9y ago
        I tried to upvote and it's still grey. There's obviously something wrong in the information, but those who know better aren't taking the time to impart that to us.
        FRex 9y ago
        If you or someone can't come and point out that 'obviously wrong something' then don't say that just because a comment got downvoted for some bizarre reason. That same comment now has 11 points. I hope it didn't now become 'obviously right' to you just because of the point count. The fact this (going into 'grey' or 'black' with 0 retort or correction given by anyone) even happened is just stupid to me. I believe nothing I said is wrong and anyone is welcome to prove me wrong. I also answered the original questions/doubts clearly (Is LuaJIT stuck on 5.1 and no longer in development - no and no and there is nothing wrong with 5.1 itself). The only downside could be how brief I was but I gave plenty of keywords ('ints', 'bit ops', 'function environments') for an astute reader to google or look up in the documentation of Lua (which is a Ctrl + F friendly one pager plain HTML with minimal styling and no JS, I have it as a single .html file with inline PNG and css on my desktop to use offline). This stealthy downvote drama is why I use HN passively, logging in only to do a fire and forget comment. I've just avoided seeing this entire downvote debacle unfold in real time during my normal browsing (and thus avoided wondering what's going on or if I were providing people wrong information or something else wrong on my part, since it's not like any downvoter told us why they did it) because of that habit.
landr0id 9y ago
So what's this API do? Allow you to ditch vimscript for lua or something else?
- pmoriarty 9y ago
  It's been possible to script vim in Lua (and various other languages including Python, Ruby, Perl, and even Scheme) for a long time.. long before neovim existed. The problem is that the overwhelming majority of vim scripts are written in vimscript. So even if you switch to using some other language to script vim, virtually all the rest of the vim ecosystem will still be in vimscript.
  - fmoralesc 9y ago
    Sure, but now, because neovim is guaranteed to have lua available (not necessarily the case in all vim builds), you can count on it, which in turn eases the problem of consuming the scripts.
  - alphaalpha101 9y ago
    >The problem is that the overwhelming majority of vim scripts are written in vimscript. And thank god for that. Vimscript is an actual scripting language. Lua is... not.
  - DigitalJack 9y ago
    Not the same. At least pre vim 8. I don't know if this has changed. https://geoff.greer.fm/2015/01/15/why-neovim-is-better-than-vim/ https://geoff.greer.fm/2015/01/15/why-neovim-is-better-than-... Example for python from the post import vim # Show current directory in Vim cwd = vim.eval('getcwd()') vim.command(':Explore %s | redraw' % cwd) Technically it's python, but it's a shim.
  - superflyguy 9y ago
    Who is that a problem for?

kosinus 9y ago

Isn't LuaJIT stuck on Lua 5.1, and no longer in development?

rijoja 9y ago
excellent opportunity for somebody to step up!
- wruza 9y ago
  First of all, it was never unmaintained, and has two parts: interpreter and jit-compiler. The interpreter is rock-hard and was battle-tested in many production environments for years. There is nothing to do in it anymore[1]. Jit part is under active development. For one, among many others, they recently patched GC to remove the famous 2Gb memory restriction for LuaJIT. Jit was also always production-ready, but their sense of “ready” is too responsible, so their current version is beta3. [1] yeah, the language doesn’t have to change and “evolve” constantly, if its roots were planned thoroughly.
_dcwr 9y ago
It's 5.1 compatible plus some nice-to-haves from 5.2: http://luajit.org/extensions.html http://luajit.org/extensions.html I wouldn't call it 'not in development' and even if, then 5.1 is a fine version of Lua and LuaJIT is battle tested very well and rock solid still. Changes in Lua 5.2 and 5.3 are breaking (and some are deep, like the ints, bit ops, function environments) but most of 'usual' code is compatible between 5.1, 5.2 and 5.3. I learned Lua 5.2 and then went back to 5.1 when 5.3 came out because I didn't like the int stuff in 5.3 and didn't want to use an obsolete version (5.2) with no upsides (5.1 has the upside of being compatible with LuaJIT).
- vog 9y ago
  To those who downvoted FRex's comment: Do you care to elaborate? I don't see anything wrong with it. (And it's definitely more insightful than the slightly older sibling comment, which apparently has not been downvoted.)
  - oblio 9y ago
    Maybe someone fat-fingered it?
    - vog 9y ago
      No, it had more than one downvote when I upvoted it, i.e. stayed grey after upvote. Moreover, I just saw it being black, then grey, then black. So it still receives a mix of downvotes and upvotes. Very strange.
    - aidos 9y ago
      I tried to upvote and it's still grey. There's obviously something wrong in the information, but those who know better aren't taking the time to impart that to us.
      - FRex 9y ago
        If you or someone can't come and point out that 'obviously wrong something' then don't say that just because a comment got downvoted for some bizarre reason. That same comment now has 11 points. I hope it didn't now become 'obviously right' to you just because of the point count. The fact this (going into 'grey' or 'black' with 0 retort or correction given by anyone) even happened is just stupid to me. I believe nothing I said is wrong and anyone is welcome to prove me wrong. I also answered the original questions/doubts clearly (Is LuaJIT stuck on 5.1 and no longer in development - no and no and there is nothing wrong with 5.1 itself). The only downside could be how brief I was but I gave plenty of keywords ('ints', 'bit ops', 'function environments') for an astute reader to google or look up in the documentation of Lua (which is a Ctrl + F friendly one pager plain HTML with minimal styling and no JS, I have it as a single .html file with inline PNG and css on my desktop to use offline). This stealthy downvote drama is why I use HN passively, logging in only to do a fire and forget comment. I've just avoided seeing this entire downvote debacle unfold in real time during my normal browsing (and thus avoided wondering what's going on or if I were providing people wrong information or something else wrong on my part, since it's not like any downvoter told us why they did it) because of that habit.

landr0id 9y ago

So what's this API do? Allow you to ditch vimscript for lua or something else?

pmoriarty 9y ago
It's been possible to script vim in Lua (and various other languages including Python, Ruby, Perl, and even Scheme) for a long time.. long before neovim existed. The problem is that the overwhelming majority of vim scripts are written in vimscript. So even if you switch to using some other language to script vim, virtually all the rest of the vim ecosystem will still be in vimscript.
- fmoralesc 9y ago
  Sure, but now, because neovim is guaranteed to have lua available (not necessarily the case in all vim builds), you can count on it, which in turn eases the problem of consuming the scripts.
- alphaalpha101 9y ago
  >The problem is that the overwhelming majority of vim scripts are written in vimscript. And thank god for that. Vimscript is an actual scripting language. Lua is... not.
- DigitalJack 9y ago
  Not the same. At least pre vim 8. I don't know if this has changed. https://geoff.greer.fm/2015/01/15/why-neovim-is-better-than-vim/ https://geoff.greer.fm/2015/01/15/why-neovim-is-better-than-... Example for python from the post import vim # Show current directory in Vim cwd = vim.eval('getcwd()') vim.command(':Explore %s | redraw' % cwd) Technically it's python, but it's a shim.
- superflyguy 9y ago
  Who is that a problem for?