The JIT compiler of Java does the optimization you’re talking about. So that advantage of C++ is not really there.

You can compile C++ for all architectures you want as well. The reason you don’t normally use Java for clients is that the garbage collector runs at undefined times, causing stuttering. This has been rectified through new algorithms though, so the real reason why you don’t wanna use Java is because it simply doesn’t have the best tooling and libraries that C++ has, no Unreal engine and no Godot.

Why the fuck would you go for Backend in C++ and frontend in Java 🤣 just the wrong way around

Of course there’s a best solution… it’s whatever you end up with

I think what people mean when they say this is that they are looking for the same price point as the equivalent Windows device… I don’t know all these companies but every time I looked for a Linux PC/laptop it was 25-30% more expensive than the equivalent Windows thing.

You’re the one who brought up runit and insinuated it doesn’t have this problem ¯_(ツ)_/¯

I don’t know runit. Maybe runit didn’t even have a way to delay or customize shutdown, maybe it always just waits 5 seconds and then forcibly terminates a process, resulting in you never noticing when a cleanup job was too slow. Maybe you just randomly never installed a particular program with a slow shutdown job while using runit. There’s a bunch of reasonable explanations and possibilities for why this difference exists, and they can all mean systemd is perfectly reasonable.

systemd moment in the sense that someone not affiliated with systemd used systemd to write a stop job that doesn’t terminate quickly? Or that you willingly installed software that brought along a slow stop job with it?

This is like so far away from systemd’s fault, idk, it must just be a meme right?

This is one of the funniest posts I’ve seen here so far. Thanks for that! I unfortunately don’t otherwise have anything to add that hasn’t already been said, just wanted you to know that I enjoyed it a lot :)

Lemmy is tech-minded, there are safe spaces for trans people. You can basically do the math.

I like to use “Top of X” a lot 🤔

we should ignore the “advice” from reddit that tells us that people are too stupid to sign up for anything

Definitely agree. The problem is just when someone in the past said “you should join <forum x>!”, you were always able to just immediately go to forum x’s signup page and sign up. But if someone hears of Lemmy, and goes to join-lemmy.org, there is no way to go to a signup page directly. They have to first learn about the multiple servers, and choose one. I think a “fast join” button like you say should be fine, and immediately next to it something to catch all the advanced actually curious users with something like a “advanced sign-up”

In lemmy-ui we have a post-deduplicator for feeds

That’s weird, because that’s exactly from where I’m coming from, I’m always using the lemm.ee website directly on all my devices, and I constantly see duplicate posts.

Copying historical content and rewriting history isn’t possible in a federated system

I have less knowledge of this topic so I’ll defer to you, but I have the feeling this may not be true. You might of course not be able to ensure consistency between all instances, ensure that it’s been changed everywhere, but I really can’t see why this is any different than “editing” a comment’s content or a post title, which is already possible. Why wouldn’t it be possible to “edit” the comment/post author in exactly the same way?

Thanks for your response and all you’re doing!

That’s why no one suggested “simply consolidating”. I didn’t suggest any solution at all. I’m just posing a question of if this actually pretty big problem is attempted to be handled.

gives a prepopulated list

The official one also does that. I’m talking about choosing a username, password, and email maybe, and then clicking register, and being done. No thinking involved.

Crossposts only show up once on the default UI

False, you get links to the other posts, of which you posted a screenshot, but each post is handled as being completely separate. If you are in the subscribed, local or all feeds, you would see all of these posts separately. Have you really never noticed scrolling by “the same” post multiple times? You have to go to each post manually to get all the comments to the “same” thing.

but Mastodon doesn’t allow it either […] due to technical limitations

Yes, I know that. But I’m also a programmer and I know that “technical limitations” is mostly a term for “that’s how we started it and it would be too costly to solve now, so we’ll just dismiss it” and not for actual limitations (i.e. not technically possible). It’d maybe require breaking changes of some kind or some kind of annoying backwards compatibility workaround, but that is why I’m asking. I’m not completely familiar with activity pub, but there’s likely some key used to verify posts/messages are made by a certain user, and there’s currently no way to transfer or change that key to a new account. But it seems very technically possible to me, and also possible without massive security issues. So that was my question, is there any plans to do this or no?

Are there any plans to deal with the most common annoyances regarding Lemmy? In my opinion these are all based on federation:

1. Some completely automated way for users to join Lemmy. Yeah, it’s not hard to select a server and it’s a “good thing to do”, but it’s still better to give people the option to go for convenience instead of the “proper” path. Maybe some kind of system where instances sign up for this general, convenience way of signing up, and the registered users just get automatically distributed evenly across those instances.
2. Duplicate post aggregation. The nature of federation will always make it make sense to have duplicate communities, but this will also make posts with the same links, same images, same videos, etc show up in people’s “all” feeds multiple times. It is technically possible to algorithmically detect these duplicates and offer users a UI option (not actual backend merge) to merge them all visually into one post.
3. A way to backup your whole user data and completely restore it on any instance you want. If an instance goes under, it should be possible to keep all subscriptions, all your posts, all your comments, and migrate them to a new instance.

I’ve got backups. Haven’t updated or looked at my server in months. If I’m ever compromised by missing security updates, I just load a backup and regenerate all keys.

I don’t put any critical data on public facing servers.

Until you run into some kind of problem :D

The close message should just say exactly this. If it’s one click to reopen, then the click is the response to your suggested notification.

Well the reason to auto-close is that this is not an entirely unlikely resolution. When I inherited a project with a bunch of issues and started going through the backlog, around 50% of tickets were duplicates, already solved, unreproducible, etc etc

When you’ve only got limited time, having less of those issues to analyze and then close anyway is a very valid reason. It leaves more time for fixing real issues. Of course it comes at the cost of ignoring perfectly valid issues as well, that’s why this is obviously never an optimal policy to implement, and should only be done in desperate situations.

That’s why the “easy way to reopen” is so important. Your concern is theoretically valid, but if tickets are usually ignored for years, then it really is a desperate situation for the project whichever way you handle it. You can decide between an endlessly growing list of issues that likely aren’t valid anymore, or pissing some users off.

I don’t really see why it would be harder to find an existing or similar bug. You should be looking (or rather you should be automatically notified) before/during creating a new ticket for existing tickets describing the problem. If a closed ticket describes the exact problem, you should be finding that too, and then should just be able to use the easy way of reopening if necessary. You should also be able to find the workaround in there if someone posted it.

It’s definitely not a beautiful solution, but if you implement something like this, the project is already in a desperate state, there’s not too much good choices there anymore.

I… know… that’s why I explicitly mentioned this already xD