In the non-intrusive case, all you know is how you got there, you don't have return info to the other structures— particularly annoying if you're trying to destroy an object and have to speculatively look for references to it in the other lists in order to get rid of them.
- the same object can move between containers with no allocation and no need for a dedicated complex API
- the same object can be part of multiple containers at once; particularly useful for intrusive binary trees, for indexing data with different criteria.
- the container can be fully polymorphic, no need for all elements to be the same dynamic type.
- no need for complex allocators, you can just store the objects as you see fit.
I'm not sure I understand this one. Since the object contains the reference to where it belongs inside a container (e.g. object.node.next) how can it be re-used in multiple containers. Conversely, in a non-intrusive data structure, multiple containers can hold a ref to the same object through an intermediate node object
I don't understand where your comment comes from, to be honest. I use Facebook a decent amount, and every single post in my feed comes from a page that I follow, a group that I'm in, or a friend.
I think the issue is when your friend Bob shares something from a page that you don't follow. People seem to blame Facebook for showing you irrelevant content, rather than blaming their friend Bob for sharing it. People share things on Facebook with the intent for you to see it. If you don't like it, then block the page Bob shared from. If Bob does a lot of sharing, then either unfriend him entirely, or at least unfollow so his crap stops showing up in your feed.
I'm also sticking to kitty, 'cause I use some of the more funky features. But if I were to recommend a terminal to a newbie, I would recommend ghostty as it really cares about having a good default experience.
Yeah, except that the specific terminfo needed for ghostty isn't installed anywhere on the boxes you ssh into ... you need to manually install it on every single one of them.
That in and of itself makes it truly painful to switch to ghostty.
And there are still a lot of other issues, like e.g. building the tip is a freaking nightmare of dependencies and weird issues (hard reliance on specific versions of the zig compiler and of something called "blueprint compiler", etc...)
Not ready for prime time by a mile IMO.
As for $TERM, you can simply default it to `xterm-256color` which is more than enough