![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
I think people are confusing centralized with federated. Federation has benefits but Mastodon is not decentralized. There is duplication of data but it’s not the same.
I think people are confusing centralized with federated. Federation has benefits but Mastodon is not decentralized. There is duplication of data but it’s not the same.
There are multiple things in Go that make it better.
But just for giving a few thoughts about Java itself;
These are like “module 101” things. Like, you’re right that the IDEs nowadays do most of that, but IDEs also get it wrong (“oh you meant a THAT package instead of that other one”) and reading the code without an IDE is still a thing (code reviews for example) which means the longer the import section (both vertically and horizontally) the harder it is to work with. And if you don’t look at all imports carefully you may miss a bug or a vulnerability.
Also, Java is the only language I know of that has such a span on the horizontal. The memes about needing a widescreen monitor for Java is actually not a joke; I never had to scroll horizontally in any other language. To me that’s just insanity.
Also, if you’re gonna make it the whole universe as the root of your package structure, we already have DNS and URI/URLs for that. Let me use that!
And don’t get me started as only-files-as-packages while simultaneously having maybe-you-have-multiple-root for your code… makes discovery of related files to the one you’re working with very hard. Then of course the over reliance on generated code generating imports that might or might not exist yet because you just cloned your project…
*Vaguely wave arms towards the few dozens languages that do imports right*
I don’t mind Java personally, but let’s not pretend that its import syntax and semantics is at the better side of the spectrum here.
Just look at… Go, Haskell, TypeScript, Rust, even D has a better module system.
It’s not a fork though. It’s a complete rewrite in another programming language. That’s way more effort than a petty project.
The truth is, this might succeed based on developer reach. I love Rust, but I know it won’t have the reach (yet) that Java can, and more developers mean faster progress.
In the end, between this, Lemmy or another project which may be a fork of either, the success will be due to efforts of everyone involve at every stage. This wouldn’t exist without Lemmy, and Lemmy wouldn’t exist with ActivityPub.
So you agree?
If the bots are welcomed and they don’t have good enough moderation, this is just sketchy content with extra steps.
Maybe you can. But the thing about statistics like that it’s that they avoid saying “the average person”, and problems with averages is that half of the people are under it.
If it’s not just made up data in the first place.
> I’m fairly sure Reddit has something similar so users don’t keep seeing the same one popular community again and again.
For context, Reddit used to (5 years ago?) show multiple posts from the same community on /r/all, then they implemented a unique function that made it so only one post per sub was shown in the top X. This greatly improved /r/all. It was controversial and well documented.
It was weird at first but it really helped engagement and medium sized communities. I think if that PR makes it it would greatly improve Lemmy too.
People who learnt structural OOP without actually understanding typing system and their benefits really struggle with learning Rist as they try to map classes onto structs and it just doesn’t work.
Traits are not inheritance.
Box
is not polymorphism. Rust is not C++ with more keywords.