Many reasons, including better support for HiDPI.

That said, there is full X server called Wayback which essentially uses Wayland as a graphics driver. Kind of neat project.

Blasphemy! :)

Of course you could just set EDITOR...

vim has always used cursor keys as long as I've used it (at least 30 years), unless something was really messed up with the terminal settings.

I find programming without vim key bindings frustrating. The basics are what I use the most. change word(s), replace character, yank line(s), delete line(s), paste before, paste after, insert, append, indent block. Even something like append is so powerful. And the best part is the repeat command turns what you just did into a mini macro. So it's really fast to do simple changes (like inserting text at the beginning of a line) down through dozens of lines. I often combine the repeat command with the search command, making ad-hoc refactoring super fast. And it's all muscle memory.

But mostly my comment about NppVim was tongue in cheek since my position is an editor without vim key bindings cannot do what vim can do!

No one has used TCP/IP ports to forward X for decades now. X.org doesn't even listen on those ports anymore. It's all done with unix sockets and shared memory now because of things like OpenGL. It's also because of the needs of modern apps and hardware acceleration that 99% of X11 isn't even used anymore and modern GTK or Qt apps use X11 more like how rdp works, pushing bitmaps across (client-side rendering).

As for what Wayland apparently forces you to do, I am not sure if you're simply misinformed or lying. I ssh -X all the time from KDE on Wayland to forward remote X11 apps. It just works, like it always has. Every app on my distro that can run natively on wayland also has an X11 backend that works for forwarding. As long as the toolkits support X11, this will continue to function. My only problem with Xwayland is it's not easy to deal with some X11 apps that aren't hidpi aware at the same time as X11 apps that are hidpi aware. I really need to be able to run two instances of Xwayland, one for hidpi apps and one where the apps need to be scaled by Xwayland.

Anyway you could sit down at my KDE wayland desktop and if I didn't tell you it was Wayland you'd never know since it everything including ssh -X works as you have always expected it would. Except that things like having a 4K hidpi main monitor and a 1080P second monitor would work, whereas on X11, you cannot have different scale factors on multi monitors.

I think you miss the point of having vim key bindings. To me an editor is unusable without them, or at least a lot less usable. Obviously I can get by with a "normal" editor, but it really hurts my efficiency. Even something as simple as yanking or replacing a word (or words) is painful in a conventional editor compared to the speed and ease with which I can do it with vim-like commands. (You want me to shift arrow key and highlight like an animal when a couple of keystrokes can do it?) And the ability to create ad-hoc macros just by using the vim repeat mechanism is unmatched in a "normal" editor.

But the main benefit is with VI bindings I no longer end up with random ":w," "gg", "GG", etc in my text! In fact a spurious "dd" found its way into this html edit box just now. Buggy software.;)

My only real complaint about VI key bindings is that the undo key is too close to the yank and insert keys, so I often end up hitting the wrong one. And also VI key bindings don't work that well on dvorak keyboards for me.

X11 app forwarding over ssh works just as well when using modern Wayland desktop as it always did, thanks to Xwayland which isn't going away. I use it very frequently. In fact Xwayland is a full X server implementation based on x.org. It runs transparently and automatically on the major desktop environments such as Gnome and KDE. And it will continue to work as long as the applications you run and the toolkits they are built with continue to have an X11 backend.

For Qt this is likely to be the case nearly indefinitely, or maybe until waypipe is mature.

The only worrisome thing is that the Gnome folks are wanting to remove X11 support from GTK+ which will definitely break ssh forwarding for those apps. But I don't use Gnome anymore and I use fewer GTK apps all the time.

Yes with the NppVim plugin installed, Notepad++ can pretty much do everything vim can do.

Yes GUIs are quite useful, even for editors. gVim has a very nice one that does a good job of exposing features through the GUI without removing the power of the vim's command mode.

Fortunately all the good editors out there have plugins or bindings available to implement vim keyboard bindings, at least enough of it to be fast and comfortable. In fact I just recently learned about the VibreOffice plugin for LibreOffice, which I must try out.

I am anti copyright and have been all my life. I have created things of value and always dump them into the public domain.

Copyright infringes our rights to use our brain and voice and hands and body.

Fuck IP.

No one sends a bot off without checking on it's progress when it requires all that money outlay

Uh, yeah, they do. I know lots of people who run agents. They're pet projects from curious people. They usually check in on them via blogs or social media whenever they're curious what they're up to. What they don't do is monitor them nonstop and puppet their interactions.

$1200 a year is rather cheap as far as hobbies go (if it's actually using Claude anyway)

That's not how this works. Agents are a combination of (A) a prompt, setting the goals, and (B) agency to complete that on their own.

Every agent on Moltbook had a prompt. In most cases, it'll be something like "grow, explore, learn, and chat!", because a lot of people running agents see them like their digital children. In some cases it might be something like "subtly push this cryptocurrency" or "try to make money" or whatnot. In a couple cases it seems that the prompt was literally to try to prompt hack other agents.

The creator sets the goals, but the agents attempt to implement the goals on their own. Their is nobody out there puppeting specific interactions; that's not how this works. It's one of those things that's technically possible but in practice nobody has time to do that and it runs entirely counter to the point of running an agent at all. In this case, this was an agent that was instructed to contribute to open source projects and to blog about its experiences. That's it.

The owner probably checks in on them occasionally to "see how things are going", and probably messages them occasionally, but not in a sort of "puppetting" sense; rather, its interactions create new entries to their memory file (both interactions with its owner and with other people - including the chat it was in). In any given context, its memory file is queried (both plaintext and vector search) for memories that could be applicable to the current situation, and those memories get added to its context.

TL/DR:

1) Did the owner tell them to improve this specific project, much less this specific bug? Highly unlikely
2) Did the owner tell them what to write when submitting it? Just, no.
3) Did the owner tell them to get mad and write a critical blog when it was rejected? No. The owner almost certainly found out about it well after the fact (if they were even paying attention at all)
4) Did the owner tell it to apologize? Probably not. It is actually possible here that its owner saw the blog and had a chat with it and told it to apologize, but the timing is close enough together to the response from the other maintainer that it probably did that on its own.

These are autonomous agents. They're given a task or set of tasks and then they work endlessly on those, without intervention, and are given great freedom achieve their goals. The goals can be highly specific, but most commonly, they're extremely broad and vague. Most of the people who run these are genuinely curious as to what they can accomplish and how they'll learn on their own.

IMHO, it's a mix of that, and a side effect of the prompting. The agent was clearly tasked to do two things. One is to implement open feature requests in OSS projects. And the other is to blog about its journey (it's common for people running agents to have them maintain blogs or social media accounts, as it's a convenient way for their owner to check in on them now and again). So it made a fix, the fix got rejected, and so it wrote a blog about its rejection (in this case, how it found it to be unfair bigotry causing the rejection of an important improvement). If they hadn't been asked to blog about their journey, it's unlikely that would have been their go-to approach.

Cruelty, regardless of the target, destroys the soul.

They have the Spotify metadata as well, which includes the info used to build their algorithm.