Mastodawn

Kun nyt menneen maailman ohjelmista tuli toisessa säikeessä puhe, minun on aina silloin tällöin tullut ikävä #QEdit'iä, #PCFile'ä ja #PCWrite'ä (oikea kirjoitusasu ”PC-Write”, mutta tunniste katkeaa yhdysmerkistä). Yksinkertaisempia mutta tuottoisia aikoja. #atkjuttuja #nostalgia #shareware

Jarkko Sakkinen Jul 1, 2024

Migrated from #neovim back to #vim after several years of use because:

I neither need nor use LSP.

I don’t need two scripting languages in a text editor.

Neovim #plugin ecosystem is a dependency hell.

Neovim #plugins are fancy but that results in also a fancy configuration to maintain.

I don’t mind a slow release cycle. My vim workflow hasn’t changed for ages.

When logging into remote machines, an off-the-shelf vim installation is almost guaranteed.

Even if neovim is installed to a remote machine, it usually fails to load my configuration, given the rapidly changing upstream and plugins requiring always the bleeding edge.

I learned #vimscript in 1998 before I had even heard about #lua, and it is more comfortable programming environment for me :-) Before 1998 I was using #qedit in MS-DOS.

For local IPC with neovim, a Python package neovim-remote is required. Vim has full local IPC workflow builtin.

Karl Voit

Feb 9, 2024

@skybert My personal editor story: https://karl-voit.at/2017/06/03/emacs-history/

#Emacs #QEdit #vim

My Personal Emacs History

public voit - Web-page of Karl Voit

Jarkko Sakkinen Dec 4, 2023

I switched to #helix editor because three advantages weight me more than disadvantage of having to learn away for #vim shortcuts:

Too much legacy.

Too many plugins.

It is a varying challenge to install the latest version #neovim, which anyway needs to be done in order not to break init.lua (and that big pile of plugins).

So for the price of few weeks inconvenience I can stop spending time on text editor configuration and/or figuring out on how to install it.

I used #vim and later on neovim fo the period 1998-2023, even before using Linux. I switched to vim in MS-DOS from text editor called #QEDIT :-)

Akkoma

Gregori Fabre May 25, 2018

La start-up #qedit partage les preuves, pas les données #atelier https://atelier.bnpparibas/fintech/breve/start-up-qedit-partage-preuves-donnees

La start-up QEDit partage les preuves, pas les données - L'Atelier BNP Paribas

La start-up israélienne QEDit utilise la blockchain pour fournir aux entreprises des preuves tout en protégeant les données privées. Bienvenue dans l'ère d...

Show thread