7 ms·

The kinds of things in your comment are the kind of things that make me consider actually installing Oni rather than just going "oh neat, people are making Neov

The kinds of things in your comment are the kind of things that make me consider actually installing Oni rather than just going "oh neat, people are making Neovim frontends" like I did when I first saw this post. The only thing that makes me hesitate is because I run FreeBSD on some of my computers and FreeBSD support wasn't quite there yet for Electron apps last I checked. It may have changed in the meantime. If I were to begin using an Electron app, I need to be sure that I will be able to use it on my FreeBSD computers also. This is especially important for editors and IDEs given that writing software is rather central among the things that I do. Currently I use Neovim for a lot of things and I use PyCharm for bigger Python projects. I am wondering though, would it be feasible for one person (me) to rewrite Oni so that one can use it from within their web browser instead of with Electron?

montyf 9y ago
I liked the irony in this post, considering that the main draw of Electron apps is that they are supposed to be cross-platform. (To be fair though, FreeBSD is pretty niche.)
- 1k2ka 9y ago
  I don't consider any framework cross-platform unless it also targets TempleOS.
bryphe 9y ago
Would be interesting to see if we could compile Neovim via WebAssembly... If that's the case, it would certainly be feasible to run Oni in the browser with a few (minor) tweaks. The UI layer is react-based and would be trivial to run in a browser. Interesting project that did something similiar for Vim: https://github.com/coolwanglu/vim.js/ https://github.com/coolwanglu/vim.js/
fwgwgwgch 9y ago
Can you tell us the benefits of running freebsd on a development machine?
- bringtheaction 9y ago
  I just feel at home with FreeBSD. I mean it’s not perfect. That’s why I run FreeBSD on some and not all of my computers and instead run Linux on the rest (and also macOS on one of them). I like the idea of the same group of people maintaining the kernel and the userland utilities. Also I am strongly in favor of the family of BSD/MIT/ISC licenses over GPL. I love ZFS. I think dtrace is neat. I think jails are nice. I like pf. Nowadays there are equivalents for pretty much all of that on Linux. In fact you don’t even have to go with btrfs to get something like ZFS on Linux — the ZFS on Linux project makes ZFS available on Linux too. But on FreeBSD all of these things are there in the base install without having to do anything special and they will continue to be there for a very long time. All in all, I just like FreeBSD a lot, and I feel at home with it in a way that few other systems make me feel.
yoz-y 9y ago
Electron does provide quite a lot of apis that do not exist (and hopefully never will) in browsers. Namely, complete access to the filesystem. It also does provide a way of creating native plugins. I have not looked into the way neovim communication works but from their site it seems to be using named pipes which are again, not available from a browser.
- pjmlp 9y ago
  Access to the file system can be done via HTML 5 File API.
  - yoz-y 9y ago
    The File API is very limited in comparison what can be done with the Electron fs API which has direct access to the file system.
    - pjmlp 9y ago
      Which is a lame excuse for using Electron disguised as native app, in a connected world, even native apps should be sandboxed by default. I seriously doubt it would be impossible to use Electron as it really is, a Web App.
      - yoz-y 9y ago
        As much as I prefer real native applications and like hating on electron, I have to give it some credit. It is not just chromium, it is chromium+nodejs and all the stuff that comes with it. The answer to "would it be feasible/easy to port an Electron app to a pure browser app" is no. Unless all of the communication between the frontend part and the native tooling is done via sockets. I agree that native apps should be sandboxed, however sandboxing something like an IDE will be quite difficult. Even Apple does not sandbox Xcode.
        bringtheaction 9y ago
        > Unless all of the communication between the frontend part and the native tooling is done via sockets. Admittedly I have not developed any Electron apps, but I have developed serious web apps and worked a little bit with NodeJS also. Why don’t people do exactly that when they write their code — make all communication happen over regular HTTP and websockets?

montyf 9y ago

I liked the irony in this post, considering that the main draw of Electron apps is that they are supposed to be cross-platform. (To be fair though, FreeBSD is pretty niche.)

1k2ka 9y ago
I don't consider any framework cross-platform unless it also targets TempleOS.

bryphe 9y ago

Would be interesting to see if we could compile Neovim via WebAssembly... If that's the case, it would certainly be feasible to run Oni in the browser with a few (minor) tweaks. The UI layer is react-based and would be trivial to run in a browser. Interesting project that did something similiar for Vim: https://github.com/coolwanglu/vim.js/ https://github.com/coolwanglu/vim.js/

fwgwgwgch 9y ago

Can you tell us the benefits of running freebsd on a development machine?

bringtheaction 9y ago
I just feel at home with FreeBSD. I mean it’s not perfect. That’s why I run FreeBSD on some and not all of my computers and instead run Linux on the rest (and also macOS on one of them). I like the idea of the same group of people maintaining the kernel and the userland utilities. Also I am strongly in favor of the family of BSD/MIT/ISC licenses over GPL. I love ZFS. I think dtrace is neat. I think jails are nice. I like pf. Nowadays there are equivalents for pretty much all of that on Linux. In fact you don’t even have to go with btrfs to get something like ZFS on Linux — the ZFS on Linux project makes ZFS available on Linux too. But on FreeBSD all of these things are there in the base install without having to do anything special and they will continue to be there for a very long time. All in all, I just like FreeBSD a lot, and I feel at home with it in a way that few other systems make me feel.

yoz-y 9y ago

Electron does provide quite a lot of apis that do not exist (and hopefully never will) in browsers. Namely, complete access to the filesystem. It also does provide a way of creating native plugins. I have not looked into the way neovim communication works but from their site it seems to be using named pipes which are again, not available from a browser.

pjmlp 9y ago
Access to the file system can be done via HTML 5 File API.
- yoz-y 9y ago
  The File API is very limited in comparison what can be done with the Electron fs API which has direct access to the file system.
  - pjmlp 9y ago
    Which is a lame excuse for using Electron disguised as native app, in a connected world, even native apps should be sandboxed by default. I seriously doubt it would be impossible to use Electron as it really is, a Web App.
    - yoz-y 9y ago
      As much as I prefer real native applications and like hating on electron, I have to give it some credit. It is not just chromium, it is chromium+nodejs and all the stuff that comes with it. The answer to "would it be feasible/easy to port an Electron app to a pure browser app" is no. Unless all of the communication between the frontend part and the native tooling is done via sockets. I agree that native apps should be sandboxed, however sandboxing something like an IDE will be quite difficult. Even Apple does not sandbox Xcode.
      - bringtheaction 9y ago
        > Unless all of the communication between the frontend part and the native tooling is done via sockets. Admittedly I have not developed any Electron apps, but I have developed serious web apps and worked a little bit with NodeJS also. Why don’t people do exactly that when they write their code — make all communication happen over regular HTTP and websockets?