3 ms·

For those who want fast and lightweight without falling all the way back to emacs/vim, I’m really digging Lite-XL. Lua for customization, thin accelerated rend

For those who want fast and lightweight without falling all the way back to emacs/vim, I’m really digging Lite-XL. Lua for customization, thin accelerated rendering layer in SDL2+freetype, zero nonsense. Binary packages are like 2MB. The code itself is clean and readable. The plugin collection is still young and won’t have everything you’d find in the Electron-family of editors, but that’s also a plus when it comes to it staying lightweight and streamlined like some might want in these tools.

jorvi 4y ago
No need to fall back to Vim, Sublime has stellar performance already.
- sourcecodeplz 4y ago
  Have used: dreamweaver, vi, nano, notepad, ++, atom and sublime. Sublime so soo superior, it's not even fair. Haven't tried vscode but I understand it's a resource hog.
  - ricardobeat 4y ago
    I reluctantly switched from Sublime Text to VSCode about four years ago, but now it's simply unimaginable to go back. It's heavier, but fast enough to have four or five different workspaces open, in very large projects. The language support, intellisense, and plug-in ecosystem are miles ahead.
    - bobajeff 4y ago
      I'm curious as to why that is. I would think it's LSP support would close the gap on languages (and intellisense) at least.
  - ElectronBadger 4y ago
    Sublime Text (plus Sublime Merge) all the way. I've been on Emacs, vim, nvim and always get back to ST.
- FunnyLookinHat 4y ago
  Sublime performance can't be beat, but I'm seeing the end of the road for active plugin development. It's getting harder and harder to adopt new tools without farting around with configs all day. At least, this was my experience trying to get Deno development to feel "right". It feels like vim and VSCode are the platforms that get plugin support nowadays, and the rest are a hack.
khimaros 4y ago
i'm keeping my eye on https://github.com/lapce/lapce https://github.com/lapce/lapce
- khimaros 4y ago
  native frontend (Rust/druid), LSP support, tree sitter syntax highlighting, command pallette, vim key bindings, modal editing, plugins in any language with WASI target, remote development, community led, open source plugin registry, it checks a lot if boxes. https://lapce.dev https://lapce.dev

jorvi 4y ago

No need to fall back to Vim, Sublime has stellar performance already.

sourcecodeplz 4y ago
Have used: dreamweaver, vi, nano, notepad, ++, atom and sublime. Sublime so soo superior, it's not even fair. Haven't tried vscode but I understand it's a resource hog.
- ricardobeat 4y ago
  I reluctantly switched from Sublime Text to VSCode about four years ago, but now it's simply unimaginable to go back. It's heavier, but fast enough to have four or five different workspaces open, in very large projects. The language support, intellisense, and plug-in ecosystem are miles ahead.
  - bobajeff 4y ago
    I'm curious as to why that is. I would think it's LSP support would close the gap on languages (and intellisense) at least.
- ElectronBadger 4y ago
  Sublime Text (plus Sublime Merge) all the way. I've been on Emacs, vim, nvim and always get back to ST.
FunnyLookinHat 4y ago
Sublime performance can't be beat, but I'm seeing the end of the road for active plugin development. It's getting harder and harder to adopt new tools without farting around with configs all day. At least, this was my experience trying to get Deno development to feel "right". It feels like vim and VSCode are the platforms that get plugin support nowadays, and the rest are a hack.

khimaros 4y ago

i'm keeping my eye on https://github.com/lapce/lapce https://github.com/lapce/lapce

khimaros 4y ago
native frontend (Rust/druid), LSP support, tree sitter syntax highlighting, command pallette, vim key bindings, modal editing, plugins in any language with WASI target, remote development, community led, open source plugin registry, it checks a lot if boxes. https://lapce.dev https://lapce.dev