Announcement

Collapse
No announcement yet.

Vim 9.0 Released With New Vim9 Script For 10~100x Execution Speed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • sinepgib
    replied
    IMO editors have a big advantage vs IDEs in terms of learning curve vs resource usage, in the sense that in an IDE you pay for what you don't use, and the price is not low. Maybe some wealthier individuals can use a 32GB workstation, I was stuck with 4GB for years and had to choose between then-prevalent Eclipse and Firefox, and it was more practical to ditch Eclipse than it would have been to work without a modern browser (the same happened with Chrome/Chromium, I did try), otherwise the IDE would freeze and spam me with OOM errors. I didn't make use of the IDE's advanced features, which are the only reasonable justification to pay that price, and you can be reasonably productive with Vim without using anything crazy as well at a much lower toll on your system. I never looked back, even now I have more appropriate specs. It may not be the coolest shiniest most productive tool (hardcore users will probably not agree), but it's good enough, it's light, and the learning curve for the basics isn't really that high, the tutor will guide you through it like a breeze. OTOH, discoverability in anything mouse oriented is significantly better.

    I feel the same would happen to me with advanced editors like Kakoune. All those cool features that I would never bother to learn and find practical uses for them won't add nothing personally to me. YMMV.
    Last edited by sinepgib; 02 July 2022, 01:09 PM.

    Leave a comment:


  • skierpage
    replied
    Originally posted by partcyborg View Post
    Cool, but I left him years ago for neovim and haven't looked back. Having a true async framework makes intensive stuff like coc-nvim run much better.
    I read about better editors then vim that support multiple selections and cursors and claim a more consistent operating model. I think either Ox or Kiro was the last one that that sounded interesting. It's hard to tell if they're worth the learning curve if you've been using vim for all your programming life. Any comments, besides neovim?

    Leave a comment:


  • sinepgib
    replied
    Originally posted by Nuc!eoN View Post
    Good.

    Fragmentation in the ecosystem is important, just as diversity in society.
    Fragmentation is one of the reasons Linux will never make it on the desktop

    Leave a comment:


  • NobodyXu
    replied
    Originally posted by Nuc!eoN View Post

    Good.

    Fragmentation in the ecosystem is important, just as diversity in society.
    Diversity does not mean fragmentation.

    Diversity means different, it can be that their implementation is different or one provides additional functionalities
    in additional to standard ones.

    In this case, neovim can simply implement the vim9 script while providing all the other features, like lua binding and other async support.
    It could also provide a better vim9 script implementation that is better than vim.

    Leave a comment:


  • Nuc!eoN
    replied
    Originally posted by TheCycoONE View Post

    NeoVim doesn't plan to support vim 9's new script so this effectively fragments the plugin ecosystem.
    Good.

    Fragmentation in the ecosystem is important, just as diversity in society.

    Leave a comment:


  • sinepgib
    replied
    Originally posted by TheCycoONE View Post
    NeoVim doesn't plan to support vim 9's new script so this effectively fragments the plugin ecosystem.
    It does. And LuaJIT did already too. Don't get me wrong, I'm not saying fragmentation is a good thing, but this is a different case from what my comment addresses.
    They should have gone with LuaJIT probably.
    Maybe "get part of the winnings" was ambiguous. I meant mostly performance-wise.

    Leave a comment:


  • TheCycoONE
    replied
    Originally posted by sinepgib View Post

    It's nice to see the improvements flow back tho. A lot of people have working plugins and all that that were made with Vim in mind and thus don't really exploit the advantages of NeoVim. Maybe this can help them get part of the winnings.
    NeoVim doesn't plan to support vim 9's new script so this effectively fragments the plugin ecosystem.

    Leave a comment:


  • sinepgib
    replied
    Originally posted by partcyborg View Post
    Cool, but I left him years ago for neovim and haven't looked back. Having a true async framework makes intensive stuff like coc-nvim run much better.
    It's nice to see the improvements flow back tho. A lot of people have working plugins and all that that were made with Vim in mind and thus don't really exploit the advantages of NeoVim. Maybe this can help them get part of the winnings.

    Leave a comment:


  • partcyborg
    replied
    Cool, but I left him years ago for neovim and haven't looked back. Having a true async framework makes intensive stuff like coc-nvim run much better.

    Leave a comment:


  • caligula
    replied
    So now it's using byte code, but not JIT?

    Leave a comment:

Working...
X