I experienced the same bug in winslop: It is not the neovim fault, but the terminal emulator. While WT (default for 11) is good enough, for some computers it is pretty laggy. I recommend wezterm.
Source: I manage many onprem windows PCs with automation, and some 1 of them experienced this issue.
Funny thing is, I would do that if there are no requirements, and the vibecode is unreadable. I would let the token-predictor create the requirements, after proof-reading and correcting it, I would create cooked-down list and run through a manager for approval, then rewrite it from scratch. My limited time and precious brain cells are too valuable to waste on reading and deciphering the half ton of sh!t an LLM produced.
If there are requirements (which are hardly applicable unfortunately) I would just rewrite the thing.
Can I ask what phone did you buy? Only if you confortable to share it ofc. I am looking for a new one. I loved my Samsung Note9. Everything was great, it had stylus, jack, battery life, oled screen, decent cameras. The only thing missing is andoid OS update support. It still better than most middle range phones…
I am happy that I’ve been useful 😄 The experience on windows will always be worse than on linux sadly. But I have no choice, I have to use winslop for work, so I made it work. 😅