5 ms·

It’s too bad that Onivim2 development stopped. https://v2.onivim.io/ https://v2.onivim.io/ It had the potential of being all the great things of both SpaceVim

It’s too bad that Onivim2 development stopped. https://v2.onivim.io/ https://v2.onivim.io/ It had the potential of being all the great things of both SpaceVim + VS Code combined into a native app.

thecatster 4y ago
I was really hope for that to turn out well, but alas, but to Emacs or Neovim I go. I even paid for an Onivim2 license.
thomasfortes 4y ago
If I had to bet, I would guess that the ReasonML > Rescript drama/change killed a lot of the momentum in the community.
- Sparkenstein 4y ago
  The reason why you shouldn't go for obscure frameworks for new projects and stick to popular libraries like vue react
  - thomasfortes 4y ago
    Funny thing, ReasonML (the alternative syntax for OCaml) was created by Jordan Walke, who also created React. The cool thing about Bucklescript is that it generated pretty readable javascript, so dropping the compiler and working with the JS files was pretty easy, which is what I did with a project that I was working when the drama started, just used the generated js files and slowly replaced them with typescript when needed.
- triyambakam 4y ago
  I'm only vaguely aware of the change. Can you elaborate?
  - thomasfortes 4y ago
    The creator of bucklescript (ReasonML/OCaml to JS compiler) decided to drop ocaml support and gather the already built community around his new project (Rescript) and it wasn't well received by the part of the community that were interested in ReasonML (and OCaml) for native or hybrid applications, which is kind of obvious since: 1. Rescript is not ReasonML/OCaml, it is a new language. 2. Rescript doesn't compile to native code. Forks were being discussed, the creator didn't like the criticisms of his decision (which came as a surprise for most of the community), people didn't liked having the rug pulled out of their feet, aggressive comments were made, people were angry and the community got separated between web and native, both weaker than the united one. TL;DR; The creator decided that his project was for web only, alienated the native developers out of the blue and shattered the community.
  - d3nj4l 4y ago
    You can read about the ReScript change here: https://rescript-lang.org/blog/bucklescript-is-rebranding https://rescript-lang.org/blog/bucklescript-is-rebranding I wouldn't go so far as GP as to call it "drama", but the split left Reason without a reason (pun intended) to exist or any activity for that matter. Most of the people who liked Reason for frontend usecases moved to ReScript since that at least had some momentum behind it. Since the split, Reason itself has been largely on life support, with no significant changes and almost no forum activity in the past year. So newcomers to Reason see a dead community for a language which is a syntax extension for another language with a (relatively) alive community. The fact that Reason hasn't seen a surge in enthusiasm corresponding to the enthusiasm in the OCaml community with the advent of 5.0 and multicore is proof enough that Reason is dead, and projects written in Reason should probably consider moving to OCaml entirely considering there are planned changes to the OCaml syntax for effects which I don't think are going to make it to Reason. Some people in the Reason world blame the ReScript people for this, which I think is entirely misplaced. The only reason (pun not intended this time) Reason has died off is that there is absolutely no clarity on the future of Reason. The creator of Reason, Jordan Walke, has been entirely MIA for about two years now. A version 4.0 was planned in 2020 and as of now hasn't come up. This issue was opened in Nov 2020 asking for future plans and is still unresolved, and the latest comment from a new developer just makes my point: https://github.com/reasonml/reason/issues/2634 https://github.com/reasonml/reason/issues/2634.
cercatrova 4y ago
I've found Helix Editor to be a good successor [0], although it's still in development. Vim-like modal editing with fast performance due to being written in Rust rather than Electron. [0] https://helix-editor.com/ https://helix-editor.com/
- konart 4y ago
  How can it be a successor to Oni if it's terminal-only application?
  - cercatrova 4y ago
    Due to speed and vim-like editing, with certain things like tree-sitter support built in, similar to how Oni has things built in. With (Neo)Vim you'd have to configure that yourself. That it's terminal versus GUI doesn't make much difference to me, since as long as it shows text/code on the screen, I don't really care how it displays it.
    - N-Krause 4y ago
      OniVim's main selling points was it beeing close to VSCode, so saying Helix Editor is its successor but not having the main features does not make a lot of sense to me. Based on your points it sounds like Helix Editor is pretty much the same as SpaceVim.
      - cercatrova 4y ago
        I used OniVim due primarily to speed and not having to set up a vimrc. That it was a GUI app versus terminal based is immaterial to me. Now I have my own vimrc so it doesn't matter much anymore, but last year OniVim was nice enough to use.
    - konart 4y ago
      As stated already - the main selling point of Oni is\was VSCode-like UI, ease of extension installation etc. Speed or vim-like editing was not a selling point at all. >I doesn't make much difference to me Okay, but this is completely beyond the point.

It’s too bad that Onivim2 development stopped. https://v2.onivim.io/ https://v2.onivim.io/ It had the potential of being all the great things of both SpaceVim + VS Code combined into a native app.

thecatster 4y ago

I was really hope for that to turn out well, but alas, but to Emacs or Neovim I go. I even paid for an Onivim2 license.

thomasfortes 4y ago

If I had to bet, I would guess that the ReasonML > Rescript drama/change killed a lot of the momentum in the community.

Sparkenstein 4y ago
The reason why you shouldn't go for obscure frameworks for new projects and stick to popular libraries like vue react
- thomasfortes 4y ago
  Funny thing, ReasonML (the alternative syntax for OCaml) was created by Jordan Walke, who also created React. The cool thing about Bucklescript is that it generated pretty readable javascript, so dropping the compiler and working with the JS files was pretty easy, which is what I did with a project that I was working when the drama started, just used the generated js files and slowly replaced them with typescript when needed.
triyambakam 4y ago
I'm only vaguely aware of the change. Can you elaborate?
- thomasfortes 4y ago
  The creator of bucklescript (ReasonML/OCaml to JS compiler) decided to drop ocaml support and gather the already built community around his new project (Rescript) and it wasn't well received by the part of the community that were interested in ReasonML (and OCaml) for native or hybrid applications, which is kind of obvious since: 1. Rescript is not ReasonML/OCaml, it is a new language. 2. Rescript doesn't compile to native code. Forks were being discussed, the creator didn't like the criticisms of his decision (which came as a surprise for most of the community), people didn't liked having the rug pulled out of their feet, aggressive comments were made, people were angry and the community got separated between web and native, both weaker than the united one. TL;DR; The creator decided that his project was for web only, alienated the native developers out of the blue and shattered the community.
- d3nj4l 4y ago
  You can read about the ReScript change here: https://rescript-lang.org/blog/bucklescript-is-rebranding https://rescript-lang.org/blog/bucklescript-is-rebranding I wouldn't go so far as GP as to call it "drama", but the split left Reason without a reason (pun intended) to exist or any activity for that matter. Most of the people who liked Reason for frontend usecases moved to ReScript since that at least had some momentum behind it. Since the split, Reason itself has been largely on life support, with no significant changes and almost no forum activity in the past year. So newcomers to Reason see a dead community for a language which is a syntax extension for another language with a (relatively) alive community. The fact that Reason hasn't seen a surge in enthusiasm corresponding to the enthusiasm in the OCaml community with the advent of 5.0 and multicore is proof enough that Reason is dead, and projects written in Reason should probably consider moving to OCaml entirely considering there are planned changes to the OCaml syntax for effects which I don't think are going to make it to Reason. Some people in the Reason world blame the ReScript people for this, which I think is entirely misplaced. The only reason (pun not intended this time) Reason has died off is that there is absolutely no clarity on the future of Reason. The creator of Reason, Jordan Walke, has been entirely MIA for about two years now. A version 4.0 was planned in 2020 and as of now hasn't come up. This issue was opened in Nov 2020 asking for future plans and is still unresolved, and the latest comment from a new developer just makes my point: https://github.com/reasonml/reason/issues/2634 https://github.com/reasonml/reason/issues/2634.

cercatrova 4y ago

I've found Helix Editor to be a good successor [0], although it's still in development. Vim-like modal editing with fast performance due to being written in Rust rather than Electron. [0] https://helix-editor.com/ https://helix-editor.com/

konart 4y ago
How can it be a successor to Oni if it's terminal-only application?
- cercatrova 4y ago
  Due to speed and vim-like editing, with certain things like tree-sitter support built in, similar to how Oni has things built in. With (Neo)Vim you'd have to configure that yourself. That it's terminal versus GUI doesn't make much difference to me, since as long as it shows text/code on the screen, I don't really care how it displays it.
  - N-Krause 4y ago
    OniVim's main selling points was it beeing close to VSCode, so saying Helix Editor is its successor but not having the main features does not make a lot of sense to me. Based on your points it sounds like Helix Editor is pretty much the same as SpaceVim.
    - cercatrova 4y ago
      I used OniVim due primarily to speed and not having to set up a vimrc. That it was a GUI app versus terminal based is immaterial to me. Now I have my own vimrc so it doesn't matter much anymore, but last year OniVim was nice enough to use.
  - konart 4y ago
    As stated already - the main selling point of Oni is\was VSCode-like UI, ease of extension installation etc. Speed or vim-like editing was not a selling point at all. >I doesn't make much difference to me Okay, but this is completely beyond the point.