Correlation between vi and convoluted software architecture

I adore vi but use windows. Searching for vi on windows I can't help but notice: every vi clone is a complicated mess.

There is something about vi that attracts schizos. Or maybe the other way: vi molds you into a mental midget.

How do you know the correlation is exclusively with vi and not windows?

>>2
There are good editors for windows.
There are good emacs clones for windows.

Vi clones are bad on all platforms. I dare you to name me one which isn't terribly hostile and complicated. Being written for a 50 year old terminal rules one out.

>>3
|good editor for windows
Such as?

>>4 Notepad++

Why are you being an anus and not just using vi with Cygwin?

>>4,5
Notepad++ is an example. Before it there were bunch of many similiar, quality editors such as TextPad.

Before that there was brief, which now even has a good, modern version.

After that, thanks to sublime and enthusiastic youngsters, we've realized that the editors we stare into 1/3 of our lifes don't have to look like shit. The new generation includes 4coder, codewriter and notepads.

These all install/uninstall and configure neatly, look acceptable, interact well enough with the os, don't have needlessly complicated, redundant functionality and have a minimal sense of direction. Vi clones on the other hand can't keep themselfes from adding unelegant ideas just so their autism juices give their tranny live a small glimmer of happiness. They don't mind that their editor looks crooked and doesn't work properly without spending a considerable amount of time scripting in a atrocious scripting lang. They know all the pitfalls and they feel smart knowing them.

Another way to work with multiple files aaaaaaaaaaah 💗 Another abstraction aaaaaaaaaaaaaaaaaaaaaaahhhhhhh 💗💗💗 Yes, Bram, give me another command I can learn to hack rust faster ✨✨✨ I can't imagine a better way the spend a friday night than to do drugs, code and masturbate to the thought of getting raped by people of color 💦💄🚀

>>6
I don't use terminals. Terminals have shit latencies, look shit, feel shit and are primitive. Time has moved on. Kids are making beautiful diagrams on the web. We can draw our beautiful math instantly not just receive cold numbers after waiting 20 minutes for the programm to run. All visions can be made reality and you choose ASCII drawings.

I also don't use shitty emulation layers. If I wanted to use unix I'd use unix. It's never first class on the host os. I don't use Wine on Linux either.

>>4
sublime text with vi binds

>>9
Is it good? I've a licence but I thought the vi mode was more like an afterthought/compatibility thing.

correlation between dubs and not being an anus

vi on windows

You're supposed to use Visual Studio on Windows. It's literally the best IDE in existence and possibly the reason for Windows's desktop dominance the past two decades.
You would have to be a schizo to use anything else if you're on Windows, honestly.

I mean you're using fucking Windows, you can't claim that you're about FOSS or UNIX hacker bullshit.

>>9,10
Ok, I've tried it and it's a shitty emulation layer, not a first class concept. I tried the vi emulation in vs and it's the same.

Maybe using vi is irrational and that's why all clones are irrational because their made by people that didn't get the hint that it's not the optimal input method anymore.

I'm even more convinced that using vi changes your brain and makes you more autistic. Maybe a bit of autism helps in our profession and the new way of thinking furthers your brain. But too much is too much, as always.

>>12
I realize that and I use it exclusively. The editing experience however is mediocre.

And vs is part of the tooling but not everything. There are a plethora of high quality dev tools for windows, the best of which are stand alone (such as WPA and Nsight). Also vs is close to the peak debugging experience as one can get in an IDE. Current avant-garde debuggers are crippled by the restriction an IDE gives. And there a lot of them in development, people have realized the value of debuggers. Microsoft is working on some, game devs are working on many.

About the vi thing: It's comfy. Not a word I'd use to describe vs. It has something peaceful. Minimal interface and everything is deterministic: no hiccups, no annoyances. Also the normal mode is fun.

A thing vim got right is low latency: Input feels good. Shame everything else doesn't.

What's wrong with gVim?

>>16

1. ugly
2. bad defaults
3. terrible, complex configuration
4. not interactive: you've to use a backward ass way to config it. of course your config isn't remembered when you change it, you've to change it another time and write it to the vimrc so it stays. having a gui with all options and instant feedback is appropriate. this wouldn't be such a problem if you didn't have to configure that much to even use it properly.
5. bad assimilation: last time i tried it searched > 5 locations for the config file, including a slow network drive. of course they're all nonstandard and wildly different from what you expect on windows. spawning a new buffer resizes the actual window. remembering the window size and position and implementing fullscreen is apparently rocket science.
6. file browsing, grepping, window management is solved with plugins, which are a mess (buggy, slow, inefficient, doesn't handle edge cases).
7. terrible mouse support

Vi > *

Deal with it.

>>18
Vi normal mode > other editing modes.

Vi itself is nice but there has been some advancement in the last 40 years.

Holy shit.

They've fixed many of my complaints. It's usable now. No more than maybe 1 major version since I last tried. The answer seems to be that gvim is good enough that nobody cares for a clone.

I'm very happy to disprove my hypothesis. Things are improving.

_{Stoic vi user of many years continues being comfy.}

Continue your endless quest for the perfect dev environment or take heed from an old wiz and learn the 6 scrolls.