I've started writing my own SuperCollider synths to use in Tidal Cycles! This one is a classic acid bass, and I'm using it for the bassline from “365”
#TidalCycles #SuperCollider #Algorave #Acid #ElectronicMusic #Neovim
I've started writing my own SuperCollider synths to use in Tidal Cycles! This one is a classic acid bass, and I'm using it for the bassline from “365”
#TidalCycles #SuperCollider #Algorave #Acid #ElectronicMusic #Neovim
@umbraroze There's actually little to no benefit in this, unless you have an affinity for Lua.
RE: https://hachyderm.io/@bbatsov/116199710611909979
What a great elaboration on the future of editors like Emacs and (Neo)vim in times of AI and the "IDE gravity well" as the author puts it.
@mrmasterkeyboard Is anyone doing a NeoVim fork yet? I'm not ready to give up my client/server architecture or Lua config yet...
@mrmasterkeyboard @reiddragon I mean, that would be cool based upon the command it's called up.
evi: basically vim minus #AIslop. init.vim (like #vim does) configuration file and moves on from there`nevi: basically neovim minus #AI #slop.init.lua configuration like #neovim would.neville: basically something to add/remove NvChad or other preconfigs.It would also make it convienient to go between "basic mode", "comfort mode" and "perdormance mode"...
-noconf flag to ignore all configurations and just load the blank evidefaults... After all, people accept that with "#StallmanOS" aka. #GNUemacs too. (See org mode)...
vi implementation buy calling the binary and then the vi subcommand like ./toybox vi ...@reiddragon well, @mrmasterkeyboard did #fork #vim at the last pre - #vommit point of the #git...
evi, which I think is a good name...nevi (basically neovim on #evi basis)...Cuz I wish for that to happen, not only because I want to see a better #neovim but also because we better become more #intolerant to the #intolerable #Enshittification!