←back to thread

Pragtical: Practical and pragmatic code editor

(pragtical.dev)
255 points rd07 | 3 comments | 20 Aug 24 07:15 UTC | HN request time: 0s | source
Show context
geenat ◴[20 Aug 24 08:22 UTC] No.41297978[source]▶
As an extension writer...

Writing extensions in Lua is huge. (Same as OBS) Looks very simple and productive.

It's one of the main reasons I've stuck to Sublime... extending with Python is very easy and works everywhere.

Even if both Zed and VSCode are strong in other areas.. Rust extensions makes me cringe (a build toolchain? ugh..) VSCode's inconsistent undocumented Javascript API is a pain in the butt (paste & pray driven development).

Will be keeping an eye on this.

replies(7): >>41298090 #>>41298131 #>>41298175 #>>41298234 #>>41299527 #>>41299676 #>>41300681 #
ta8645 ◴[20 Aug 24 08:43 UTC] No.41298090[source]▶
For what it's worth, NeoVim's extension language is Lua as well.
replies(2): >>41299077 #>>41303135 #
1. coliveira ◴[20 Aug 24 19:25 UTC] No.41303135[source]▶
Vim also has support for Lua scripts.
replies(1): >>41309277 #
2. maleldil ◴[21 Aug 24 11:41 UTC] No.41309277[source]▶
Not to the same extent. Neovim has extensive Lua support, to the point where you can do _almost_ anything in Lua, whereas in Vim, it's, AFAIK, a second-class citizen. For example, my nvim config is written entirely in Lua with no vimscript files, except for a few vim.cmd's that run one-line vimscript commands. (exactly three, and they're all highlighting/colorscheme–related).
replies(1): >>41312132 #
3. coliveira ◴[21 Aug 24 17:01 UTC] No.41312132[source]▶
I believe you can do the same in vim, however I agree that there is more friction in vim because Lua is not the main scripting language. Moreover, vim is not guaranteed to be compiled with Lua, so you only want to do this if you can control the installation of the vim binaries.