(untitled)

If Vim is bloat, then what isn't?(USER WAS WARNED FOR THIS POST, You should always elaborate on your opinions rather than just spilling the soykaf.)

sussex sussy sex ඞඞඞඞඞඞඞඞඞඞඞඞ

>>33160 vi https://ex-vi.sourceforge.net https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/vi

>>33160 >If Vim is bloat, then what isn't? NeoVim removed some of the bloat (but added other things). Try Busybox vi. https://www.busybox.net/downloads/BusyBox.html

ed(1) is the standard unix editor

>>33160 There's a small but statistically significant number of computer science types who confuse UNIX-style minimalism for reductivism and declare that every feature that isn't literally essential to a program's operation to be bloat. In my mind, something is bloat if a) it's complex for reasons that have nothing to do with its functionality, and/or b) can be removed without most users noticing or caring.

>>33176 >Simple questions belong in the questions thread. Who are you to determine if this is simple or not? The answers are good so far, such as what bloat is and text editors with less of it. This thread is where it's supposed to be. Just add onto the discussion.

>>33160 Emacs. Bloat is a relative thing – how far something oversteps what it should do. Emacs aims to be an all in one type program and it achieves that in a surprisingly small footprint. Vim should really just be a simple universal terminal editor with some useful stuff like ex built in, and it goes hugely beyond what is needed to do that. It has a smaller absolute size than Emacs, but a much larger relative bloat.

Is there a more modern alternative to vim? Such as reasonable defaults and such. I enjoy using vim, currently i'm on vscode with vim bindings, but making vim usable ends up as a configuration nightmare where everything is a mess and takes up far more time than i'm willing to give to an editor. I'd like something along the lines of vim, same principles, but more reasonable defaults and configs.

>>33262 GNU Emacs. It's literally everything you will ever need and more.

>>33262 Depends on what you want/need. A pre-riced Neovim "distro": https://www.lunarvim.org/ https://nvchad.com/ Or pre-riced Emacs with Evil mode: https://www.spacemacs.org/ https://github.com/doomemacs/doomemacs Or maybe https://helix-editor.com/ >>33263 >GNU Emacs. It's literally everything you will ever need and more. *if you're willing to put man-weeks into customization and maintenance

>>33270 You need weeks to learn any editor. Customizing you'll just do as time goes on. You don't NEED anything customized in emacs or vim, you'll find uses for customizing them based on your experiences with them.

>>33262 >Is there a more modern alternative to vim? Such as reasonable defaults and such. NeoVim was created for this purpose. >>33271 this

>>33160 Pen and paper. Takes 0MB RAM and 0 CPU cycles.

>>33270 >Or maybe https://helix-editor.com/ I think kakoune is better. https://kakoune.org/why-kakoune/why-kakoune.html

>>33160 >If Vim is bloat, then what isn't? >unironically being this new user sed red ed qed

echo "string you want to write" >> /path/to/file removing text from file is bloat, think before you type

cat > source.c Then just start typing.

>>33279 where the fuarrrk is my mcedit???

>>33288 >>33289 $ cat << eof > file.c main() { ... } eof $cat file.c main() { ... } $

>>33299 >needing a full shell to edit files

>>33302 Ah yes, all the computers I have that I develop on with no linux user space at all, not even /bin/sh Mel-larp

http://skullcode.com/bootstrap/hexboot.txt Anything beyond this is bloat

>>33303 At least show you actually know sh and use <<'eof'.

Microsoft Word has literally everything you need to write good code and it comes installed with the OS, AND you can write code in the CLOUD. Like hooooly soykaf that's way more advanced than your stupid eds and vims and macintoshs. fuarrrk you all. I write better code than all of you. I could make Windows in my code

>>33471 Absolutely this. Rich text coding really is the future here. We'd just need to take a run button somewhere on the action menu and we'd have a fresh IDE to toy with.

>>33160 use ed or acme. you can de-bloat vim when compiling i.e. vim-tiny in debian

vim is not bloated. It's cpu and memory consumption is negligible on normal computers. It's latency is the same as vi and lower than any other editor I've seen tested.

>>33160 Who even says Vim is bloat?

Wait, I have a question... What if... bloat is a subjetive thing?

Important question is the feature not liked or simply unknown? Both would lead to a dead unused feature. Most older software seems to fall under unknown features because they extend functionality beyond what users can retain memorized. By the time you finally encounter a situation where a fringe feature would really help you already forgot about it and you can't use it when you don't remember it exists. The other aspect is >>34006 usefulness depends on the user - beginners and pros use different features. When you create a UI for beginners most things are bloat because its easier to learn limiting it to core features everyone needs. Pros in contrast tend to work in niches and will rather need some specific feature than a basic general feature set. This is why good UI design needs to choose its customer before starting and the fancy devs with time do different default ui setups for beginners & pros you can pick from.