Seems like an interesting effort. A developer is building an alternative Java-based backend to Lemmy’s Rust-based one, with the goal of building in a handful of different features. The dev is looking at using this compatibility to migrate their instance over to the new platform, while allowing the community to use their apps of choice.

      • @twistypencil
        link
        English
        314 months ago

        I just self host and avoid Java like the plague due to how annoying it is to manage

        • @Ugurcan
          link
          English
          74 months ago

          3 billion devices can’t be wrong…

          • @twistypencil
            link
            English
            10
            edit-2
            4 months ago

            One dude writing a Java server app, compared to Google writing an operating system, pretty equal comparison lol

        • Derin
          link
          fedilink
          English
          54 months ago

          What’s annoying about it? Deploying a war to tomcat is one of the easiest things one can do.

          • @twistypencil
            link
            English
            74 months ago

            If you are a Java shop, and you do tomcat, then cool, maybe you’ve worked out the mysteries if Java deployment and managing resources (ahem, memory), and upgrades etc over the life cycle of a project. But most people doing deployment don’t want a one off Java app as a snowflake in their intra, if they can help it because it requires more buy into the ecosystem than you want

    • @[email protected]
      link
      fedilink
      English
      744 months ago

      Browsing the code makes me angry at how bloated Java projects are:

      package com.sublinks.sublinksapi.community.repositories;
      
      import com.sublinks.sublinksapi.community.dto.Community;
      import com.sublinks.sublinksapi.community.models.CommunitySearchCriteria;
      import com.sublinks.sublinksapi.post.dto.Post;
      import com.sublinks.sublinksapi.post.models.PostSearchCriteria;
      import org.springframework.data.domain.Page;
      import org.springframework.data.domain.Pageable;
      import org.springframework.data.jpa.repository.JpaRepository;
      import org.springframework.data.jpa.repository.Query;
      import org.springframework.data.repository.query.Param;
      import java.util.List;
      
      public interface CommunitySearchRepository {
      
        List allCommunitiesBySearchCriteria(CommunitySearchCriteria communitySearchCriteria);
      
      }
      

      Every file is 8 directories deep, has 20 imports, and one SQL statement embedded in a string literal. 😭

      • MeanEYE
        link
        English
        444 months ago

        Yup. Welcome to the world of Java where such things are not only silly but encouraged.

        • @YourAvgMortal
          link
          English
          74 months ago

          Ignoring the problem doesn’t make it better

          • Carighan Maconar
            link
            English
            114 months ago

            How would you do “better” imports then?

            • @hansl
              link
              English
              84 months ago

              *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.

              • Carighan Maconar
                link
                English
                4
                edit-2
                4 months ago

                Isn’t Go just the equivalent of only doing asterisk-imports in Java, just without (and fair enough, Java has 0 need to do that 😂) repeating the import-keyword?

                • @hansl
                  link
                  English
                  34 months ago

                  There are multiple things in Go that make it better.

                  But just for giving a few thoughts about Java itself;

                  • being able to import a package and use it as a namespace would already go a long way
                  • being able to import multiple things from a package without listing separate line for each items
                  • not having to go from the root of the whole fucking world to import a package would be great
                  • having the ability to do relative imports to the module I’m writing would be great

                  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…

            • @uranibaba
              link
              English
              3
              edit-2
              4 months ago

              deleted by creator

      • Carighan Maconar
        link
        English
        84 months ago

        And what’s bad about that? As in, how is the verbosity a negative thing exactly? More so because virtually any tool can be configured to default-collapse these things if for your specific workflow you don’t require the information.

        At the same time, since everything is verbose, you can get very explicit information if you need it.

        • @[email protected]
          link
          fedilink
          English
          154 months ago

          Here’s an example:

          https://github.com/sublinks/sublinks-api/blob/main/src/main/java/com/sublinks/sublinksapi/community/listeners/CommunityLinkPersonCommunityCreatedListener.java

          IMO that’s a lot of code (and a whole dedicated file) just to (magically) hook a global event and increase the subscriber count when a link object is added.

          The worst part is that it’s all copy/pasted into a neighbouring file which does the reverse:

          https://github.com/sublinks/sublinks-api/blob/main/src/main/java/com/sublinks/sublinksapi/community/listeners/CommunityLinkPersonCommunityDeletedListener.java

          It’s not the end of the world or anything, I just think good code should surprise you with its simplicity. This surprises me with its complexity.

          • Carighan Maconar
            link
            English
            34 months ago

            Yeah but that’s more on the coder. Like you indirectly say, they could just as well have had a single listener for community update events, since they all share the data structure for such events (I would assume, haven’t looked around too much).

            And to me as a professional java coder, I will say it’s just not complex. The scaffolding you mentally discard after a week of working with Java unless you’re looking for something related to do the scaffolding - and then it’s cool that it’s all explicitly there, this has helped me countless times in my career and is one of the big strengths of such verbose languages - and beyond that and some design choices I would not have made that way related to naming and organization, there’s not much code there to begin with. In modern Java you might just do this in a lambda supplied in the place where you hook the events, anyways.

          • @BURN
            link
            English
            34 months ago

            I find that Java is overly Verbose, but it’s much better than the alternative of underly verbose.

            Java really follows the single class for single functionality principle, so in theory it makes sense to have these located in different classes. It should probably be abstracted to a shared method, but it shouldn’t be in the same file.

            At least to me this looks like simplicity, but I’ve been writing Java in some capacity since 2012.

            • @[email protected]
              link
              fedilink
              English
              64 months ago

              It’s not just the visible complexity in this one file. The point of it is to keep a subscriber count in sync, but you have that code I referenced above, plus:

              LinkPersonCommunityCreatedEvent LinkPersonCommunityDeletedEvent LinkPersonCommunityCreatedPublisher LinkPersonCommunityDeletedPublisher

              And then there are things like LinkPersonCommunityUpdated[Event/Publisher] which don’t even seem to be used.

              This is all boilerplate IMO.

              And all of that only (currently) serves keeping that subscriber count up to date.

              And then there’s the hidden complexity of how things get wired up with spring.

              And after all that it’s still fragile because that event is not tied to object creation:

                @Transactional
                public void addLink(Person person, Community community, LinkPersonCommunityType type) {
              
                  final LinkPersonCommunity newLink = LinkPersonCommunity.builder().community(community)
                      .person(person).linkType(type).build();
                  person.getLinkPersonCommunity().add(newLink);
                  community.getLinkPersonCommunity().add(newLink);
                  linkPersonCommunityRepository.save(newLink);
                  linkPersonCommunityCreatedPublisher.publish(newLink);
                }
              

              And there’s some code here:

              https://github.com/sublinks/sublinks-api/blob/main/src/main/java/com/sublinks/sublinksapi/api/lemmy/v3/community/controllers/CommunityOwnerController.java#L138C31-L138C50

                  final Set linkPersonCommunities = new LinkedHashSet<>();
                  linkPersonCommunities.add(LinkPersonCommunity.builder().community(community).person(person)
                      .linkType(LinkPersonCommunityType.owner).build());
                  linkPersonCommunities.add(LinkPersonCommunity.builder().community(community).person(person)
                      .linkType(LinkPersonCommunityType.follower).build());
              
                  communityService.createCommunity(community);
              
                  linkPersonCommunityRepository.saveAllAndFlush(linkPersonCommunities);
              

              that is able to bypass the community link service and create links in the repository directly, which would presumably not trigger than event.

              Maybe there’s a good reason for that, but it sure looks fragile to me.

        • @hansl
          link
          English
          34 months ago

          how is the verbosity a negative thing exactly

          Fun fact, studies have found that the number of bugs in a program is proportional to the number of lines of codes, across languages. More lines of codes, more bugs, even for the same math and edge cases. So a more verbose language tends to have more bugs.

          • Carighan Maconar
            link
            English
            74 months ago

            Interesting, but did this include web code and code only one person really ever works on?

            Because on the pure backend level, I have observed the reverse over my career. The shorter, the “smarter”, the “cooler” the code, the more buggy it is. Not based on the code itself, but based on the developer inevitably leaving the company at some point. Meaning that what matters all of is a sudden is how verbose, how documented and how explicit the code is, because the bugs come from someone else messing with it as they get to take it over. It’s a legacy problem in a lot of ways.

            Hence me saying that if solo projects are included, they probably tilt this massively as they’ll never really run into this problem. Like say, you just scan github or something. Of course most projects in there are solo, of course the more lines the more room for bugs.
            But in an environment where you’re not solo coding, the issue is not getting the code to run and having it have no programmed bugs, but to be able to have someone else understand what you did and wanted to do in a meaningful amount of time, especially as they have to mutate your code over years and decades. Or maybe it’s just that the bugs no longer are what “matters”, as fixing code bugs is cheap compared to the endless hours wasted from “clever” code being unmaintainable. 🤷

            • @kameecoding
              link
              English
              44 months ago

              I have a similar experience, in that anytime I heard someone hating on the verbosity of Java it was never the good devs the ones who can write a code that’s readable a few months later.

      • @RookiA
        link
        English
        24 months ago

        Its still better than any python project lol

        • @TunaLobster
          link
          English
          44 months ago

          Really? I find python imports to work very similar to cpp in practice.

          • @RookiA
            link
            English
            34 months ago

            But you really dont see what the function wants or requires or returns ( except with typehints, but they dont work most of the time and then its not enforced in any way )

            • Derin
              link
              fedilink
              English
              104 months ago

              Larger, modern python projects always use type hints, for this specific reason.

              In the past you had PyDoc, which also scratched that itch.

              Barring that, contributing to a python project is very difficult without an IDE that performs type checks for you (which is unreliable).

              • @RookiA
                link
                English
                04 months ago

                Correct! As i already contributing to a big ass python project at work. We will rewrite a Big Project from python to c# in under 1 month.

                • Derin
                  link
                  fedilink
                  English
                  34 months ago

                  Just you wait until your developers learn about the var keyword - it’s going to be Python 2.7 PTSD incidents all over again 😂

      • @[email protected]
        link
        fedilink
        English
        164 months ago

        There is nothing inherently wrong with Java I would speculate, but it can be a royal pain in the ass to manage if you just need one application to work.

        I know the basics of the language, but from what I have seen managing it, I don’t like it. Just from being in security, I constantly hit barriers with devs because of versioning issues. There is always some ancient app running on a version of Java that can’t be updated, for whatever reason. Version management is always a pain, but with Java? Goddamn.

        I admit ignorance about the details of Java and how awesome it is for job security. There is no way in hell I could even debate anyone who has watched a single video on YouTube about Java. However, from what I have seen, it either works great or it fails explosively with billions of randomly allocated threads attempting to suck memory from every other server within 50 miles.

        If it’s awesome to code with, cool. I am just a little salty from my experiences, as you can tell.

        • @BURN
          link
          English
          44 months ago

          Legacy Java software is a massive pain in the ass. No arguments there. I’ve been migrating an app from Java 11->17 for the last 2 months and it’s a versioning mess. So many libraries deprecated and removed that don’t have easy replacements.

          It’s great because things don’t break when they’re running, but the problem is upgrading.

          Version management does seem to have become better with the last couple versions

          • @[email protected]
            link
            fedilink
            English
            24 months ago

            (Confirmation bias, ENGAGE!)

            We have a few of those projects coming up as well. Thankfully, I just get to poke at the apps to make sure the issues are resolved.

            But yeah, one of my examples of rogue threads is a coding issue, not inherently a language issue. Even log4j issues can’t be completely blamed on Java “The Language”.

        • Dandroid
          link
          fedilink
          English
          54 months ago

          If you have a good IDE, and Java has the best IDEs of any language I have used, then auto complete will take care of most of that for you.

    • magic_lobster_party
      link
      fedilink
      27
      edit-2
      4 months ago

      Who cares? If it works, it works.

      The biggest strength of Java is that many programmers has years or even decades of experience in it.

          • Cosmic Cleric
            link
            English
            84 months ago

            Same thing with COBOL! So many devs with … Wait. Are any COBOL devs even alive still?

            I promise you one thing, those that are still alive are making bank right now.

            • Carighan Maconar
              link
              English
              84 months ago

              Usually at banks, where they easily earn 2x+ of what I do working in Java. I happen to know one IRL, and their meetings with the boss are funny because it doesn’t really matter what number they put on the table, their boss cannot fire them. They could not replace them and they need 2+ COBOL devs in house.

              • originalucifer
                link
                fedilink
                24 months ago

                i took some cobol, i am very annoyed i did not stick with it. i could have retired by now.

              • Cosmic Cleric
                link
                English
                04 months ago

                I happen to know one IRL, and their meetings with the boss are funny because it doesn’t really matter what number they put on the table, their boss cannot fire them. They could not replace them and they need 2+ COBOL devs in house.

                I can concur, I’ve seen the same thing in real life myself. Definitely a blast watching the employee have the power.

          • @hansl
            link
            English
            2
            edit-2
            4 months ago

            PHP never went away. Wordpress, Mediawiki, Slack, Facebook, etc etc etc. IMO PHP is likely to have created the most wealth per line of code of all languages, including C (edit: since 2000). It’s completely under the radar.

      • @twistypencil
        link
        English
        44 months ago

        I care, as someone who self hosts and have been doing so for 22 years. Java has always been the most annoying thing to maintain as a holster, especially on low resourced machines, like my raspi

      • @dylanTheDeveloper
        link
        English
        04 months ago

        Also you don’t have to worry about memory management

      • MeanEYE
        link
        English
        104 months ago

        Brainfuck would be my choice if we are making things harder for ourselves.

      • Carighan Maconar
        link
        English
        34 months ago

        I bet there are forks already. NodeJS is quite popular really.

      • BarbecueCowboy
        link
        fedilink
        194 months ago

        As someone who used to be a Java programmer, I can’t make any sense of that statement.

        • Sentient Loom
          link
          fedilink
          English
          144 months ago

          Java is the first language I learned. I love how structured it is and how it forces you to work within the paradigm. I might never use it again, but it shaped how I think of programming.

          • @BURN
            link
            English
            24 months ago

            That’s why I like Java too. The fact that it’s so strict means I have to think about projects in a certain way and can’t just wing my way through it like Python.

            • Sentient Loom
              link
              fedilink
              English
              24 months ago

              Right. And then you’ll write better code when you do use Python or JavaScript or whatever.

        • @dylanTheDeveloper
          link
          English
          -14 months ago

          As someone who mostly uses C++ and C# Java is much easier for most projects

  • @[email protected]
    link
    fedilink
    English
    874 months ago

    I have a hard time believing that rewriting the backend from scratch would be faster than getting PRs approved on the main project.

    Forks like this with one guy who “knows best” usually die a slow quiet death as they get left behind by the main project.

    • @[email protected]
      link
      fedilink
      English
      574 months ago

      I think how quickly this project has gotten to near feature parity is a testament to how slow Lemmy development has been. Think about scaled sort (a feature that has been hotly requested since the migration) and how long that took to get merged in. A sort should not by any means be slow to implement.

        • @[email protected]
          link
          fedilink
          English
          24
          edit-2
          4 months ago

          IMO slow development isn’t necessarily a bad thing.

          Sure but even just recently there was the example of breaking federation over Christmas. Some of those issues persist through 0.19.3 which came out today

          Similarly scaled sort would have made a huge difference for small communities in the period directly after the migration.

        • Carighan Maconar
          link
          English
          64 months ago

          IMO slow development isn’t necessarily a bad thing.

          Quite the opposite, often it’s a benefit as you don’t end up wasting time and changing code for features where you don’t actually know yet whether your current usage demands or supports them. There’s a lot of genefit in not moving fast and not breaking things. Mostly that, well, you don’t constantly break things.

      • @[email protected]
        link
        fedilink
        English
        44 months ago

        A sort should not by any means be slow to implement.

        Sure, if the sort key is something readily available. But for scaled sort they have to compute relative size/activity of the communities the specific user is in. The cost isn’t the sort, it’s computing the metric.

        • @[email protected]
          link
          fedilink
          English
          9
          edit-2
          4 months ago

          I’m not talking about the literal sorting algorithm. Pretty sure scaled sort is exactly one more operation than hot.

      • @[email protected]
        link
        fedilink
        English
        204 months ago

        I’m a Java developer and I would much rather pick up Rust to join an active project than try to rebuild something that already works using a less-marketable language.

        • sik0fewl
          link
          fedilink
          134 months ago

          Sure, but it’s a lot more work for you to get to a point where you can be an active contributor.

          • @[email protected]
            link
            fedilink
            English
            -1
            edit-2
            4 months ago

            Is it really a lot of work for an experienced dev? I can pick up most new languages in a day or 2 unless it’s a total paradigm shift.

            • sik0fewl
              link
              fedilink
              194 months ago

              1-2 days is enough to learn the basics, but I doubt you’ll be as nearly as productive as with something you’ve been using for years. Keep in mind that new languages also mean new frameworks, etc, some which take years to actually master, but at least months to get a good handle on them.

              Also, from my understanding, Rust is a bit of a paradigm shift.

            • Carighan Maconar
              link
              English
              94 months ago

              Yeah but there’s a big difference between having “picked up” a new language and being on the level where you can viably add useful code to a distributed federated deployed platform.

              I have 12 years in Java by now, I’m fairly confident with it. Rust, yeah no, not for production code.

            • magic_lobster_party
              link
              fedilink
              14 months ago

              Sure, anyone can pick up a new language or two over a weekend. That doesn’t mean they are confident enough to contribute to large scale programs with it. That takes much longer to learn.

      • @kaffiene
        link
        English
        24 months ago

        Yeah I agree. Rust is an excellent language when you absolutely must be as safe as possible but don’t want garbage collection. But there is a level of precision required of developers which makes it slower to development in. Other languages like Java, Python and Go are all quicker to develop in. Java is much easier to refactor IMO

    • MeanEYE
      link
      English
      64 months ago

      Depends on amount of technical debt really. Sometimes rewrite is the only way. But in general fixing things can be done. It’s just matter of time, focus and effort.

  • Kawawete
    link
    fedilink
    English
    654 months ago

    Why Java though ? Like really ? It’s… Better than any other compiled language ?

    • @[email protected]
      link
      fedilink
      English
      68
      edit-2
      4 months ago

      Because modern Java is an OK language with a great ecosystem to quickly build web backends. And there are lots of java devs which means more potential contributors.

      • 0x1C3B00DA
        link
        fedilink
        274 months ago

        Exactly. It’s also using Spring Boot, Hibernate, and Lombok. It looks just like projects at work. It might be the first fediverse project I contribute regularly to.

        • @BURN
          link
          English
          164 months ago

          +1 same

          I tried to contribute to Lemmy, spent a few hours really confused by rust and gave up. I can meaningfully contribute to a Java/Spring project, not a rust one.

        • Fudoshin ️🏳️‍🌈
          link
          fedilink
          English
          -14 months ago

          Spring Boot, Hibernate, and Lombok

          Ah, yes. How about he kitchen sink and another 5000 dependencies to make Java bareable to code in? Actually lets skip Java cos it’s an over-engineered cluster-fuck that considers verbosity a virtue.

      • Fudoshin ️🏳️‍🌈
        link
        fedilink
        English
        -54 months ago

        Hello world in Java = 500 lines of code.

        Hello world in Rust = 3 lines of code.

        Java is over-engineered corporate bullshit used by banks and Android development. Nobody programs Java for the fun of it.

        • @BURN
          link
          English
          64 months ago

          Hello World is < 10 lines in Java. Just say you don’t know the language and go away.

          Java runs the majority of corporate software out there, and it is very good at what it’s built for.

          I’ll take Java over Python/Rust any day of the week

            • @BURN
              link
              English
              64 months ago

              And yet it’s still a better option than 90% of languages out there.

              Trendy languages are great until they break something or lose support. Java is consistent, and that’s the most important part.

              You sound like some Java dev personally offended you so much that you can’t separate the language from a person you hate for completely irrelevant reasons.

              Like I said, I’ll take Java and extreme OOP over Python/Rust/Go any day of the week because it’s actually readable code instead of a clusterfuck of hundreds of methods in one file

              • Fudoshin ️🏳️‍🌈
                link
                fedilink
                English
                -4
                edit-2
                4 months ago

                The only reason you don’t like Rust is it’s the first language in a long time that’s threatened the dominance of C, the bedrock of programming. If it can do that then Java is going to be under threat too. Go failed cos it’s a shit language and Python isn’t even the same category. Java is more readable than Python? You’re having a laugh or you’ve never seen a friggin line of Python in your life.

                Python:

                for i in range(1, 10):
                    print("Hello: ", i)
                

                Java:

                import static java.lang.*;
                public class BentJavaClass
                {
                    public static void main (String args[]) 
                    {
                        for(int i=1;i&lt;11;i++){
                           System.out.println("Java is shit: " + i);
                        }
                    }
                }
                

                10 lines vs 2. And you think Java is more readable?

                Back in the day Java couldn’t even handle concatenating strings and numbers and needed you to fucking convert the integer into a string beforehand (String.valueOf()). I see it only took you about 20 fucking years to figure out something most other languages had out of the box.

                What’s with all the unnecessary braces? The semicolons? Punctuation causes blindness and coldsores. Java is a cancer and it’s devs should be shot and their bodies piled high before being tipped into the sea.

                • @BURN
                  link
                  English
                  64 months ago

                  Ok, so now build an api that can handle 100k iops with a cache, db calls and everything else, and tell me how simple that is in Python.

                  Java and Python, like any programming languages don’t do everything well. They do a few things well, and most things adequately. Python is great for scripting and small applications, but once you’re hundreds of files into a corporate software project it becomes near unreadable. Java is great for large scale applications but suffers if you want to make a single purpose app.

                  I’d also argue that yes, the Java is more readable at scale. Everything is explicitly typed, braces are so much better than indents (is something 20 indents or 21 idents deep, I never know), semicolons are useful for delineating ends of statements.

                  It sounds like your only expose was Java in uni and have never worked with anything at scale.

    • @RookiA
      link
      English
      154 months ago

      Probably because everyone knows it and its more predictable

      • @mea_rah
        link
        English
        164 months ago

        Predictable in what sense?

        • @RookiA
          link
          English
          54 months ago

          If you say the function should only recieve one argument and returns always boolean. It is predictable to only allow the wanted args and forces you to return a boolean.

          For example in a less predictable programming language e.g. Python: I can do all above but python does not stop anyone to put more or less arguments to a function, or a developer not adding typehints or not complying to them and return a string instead of a boolean.

          But i had it wrong rust is similar to java on that part.

          But still it is a lot more popular and easier to start with. So there will be a lot more contributor to sublinks than lemmy ever had.

          • @mea_rah
            link
            English
            124 months ago

            Well in that sense Rust is even more predictable than Java. In Java you can always get back exception that bubbled up the stack. Rust function would in that case return Result that you need to handle somehow before getting the value.

            • @RookiA
              link
              English
              -14 months ago

              That i dont understand? How can it be a result that i need to handle? If its not correct than java will throw an error. ( As expected, shit in shit out )

              • @[email protected]
                link
                fedilink
                English
                4
                edit-2
                4 months ago

                It’s a great and probably the best error system I’ve seen, instead of just throwing errors and having bulky try catch statements and such there’s just a result type.

                Say you have a function that returns a boolean in which something could error, the function would return a Result and that’s it. Calling the function you can choose to do anything you want with that possible Error, including ignoring it or logging or anything you could want.

                It’s extremely simple.

                • @uranibaba
                  link
                  English
                  14 months ago

                  If I except a boolean, there is an error and get a Result, is Result an object? How do I know if I get a bool or error?

    • @kaffiene
      link
      English
      44 months ago

      It’s probably got the best library/tooling ecosystem of any language out there. Certainly dwarfs Rust in that regard. Easier to find devs. Reasonably efficient thou not as much as Rust and typically less memory efficient. It’s a perfectly good suggestion for a project like Lemmy. I’d reach for Java or Go before Rust for a project like this but you know, that’s just me.

      • Kawawete
        link
        fedilink
        English
        24 months ago

        You see, Go would’ve been a better option than Java.

        • @kaffiene
          link
          English
          34 months ago

          It would have been a good option. As is Java. If you want to do it in Go, go ahead.

  • @[email protected]
    link
    fedilink
    English
    614 months ago

    What missing features are so important that you decide to recreate the entire backend of Lemmy because you think the devs aren’t fast enough?

    • Ghostalmedia
      link
      English
      554 months ago

      Java instead of Rust is going to be a big thing for a lot of people who would like to contribute in their spare time. Yeah, Rust is cool, but every CS grad and their mother knows Java.

      Back during the migration surge a few months ago, you commonly saw a LOT of comments from folks saying they would love to help eat away at the project’s backlog, but they just didn’t have the time or energy to learn Rust at the moment.

      • @[email protected]
        link
        fedilink
        English
        344 months ago

        Any recent CS grad is obsessed with rust, trust me. It’s not hard to learn either with that background.

        • @[email protected]
          link
          fedilink
          English
          204 months ago

          I’m not saying that rewriting he backend is a good choice, but for me specifically, I’d like Lemmy to be written in Java. Why? I’m a Java software engineer for nearly 7 years now and I’d like to contribute. Yes, I could learn Rust, like I did learn Go, C, C++ and other languages during my cs studies. But I really don’t have the free time and motivation to do that after I already worked 8-10 hours at my computer. If I could use my existing Java knowledge to quickly fix some small bugs or whatever, I’d love to do that. But the hurdle to learn a new language (including other paradigms and best practices) just to contribute to this one project is just too high for me.

          • peopleproblems
            link
            English
            114 months ago

            Yeah, same boat. I’m continuously learning new shit with C# and I’m starting to understand Angular after all these years. I could switch back to Java with few issues.

            I would love to learn Rust, but there’s no time right now.

          • Spzi
            link
            fedilink
            English
            94 months ago

            Exactly this. It’s often about finding the right balance between technically optimal, and socially feasible (lacking the right phrase here).

            The nerds brimming with technical expertise often neglect the second point.

            Oh - wow! I was about to complain about how https://join-lemmy.org/ is a shining bad example in this regard, talking about server stuff right away and hiding how Lemmy actually looks until page 3, but apparently they changed that and improved it drastically. Cool, good job!

            Anyways.

            For collaborative projects especially, it is important to strike a balance between tech and social aspects. Making poor tech choices will put people off. But making your project less accessible will also result in less people joining. It’s crucial to find a good balance here. For many coming from the tech side, this usually means making far more concessions to the social side than intuitively feels right.

          • @[email protected]
            link
            fedilink
            English
            14 months ago

            Once you know a few languages and the principles for how a computer works moving to a new one is easy. Don’t think of it as being a “Java developer”, but a programmer. It’s just a tool.

            We did not learn languages at uni, but concepts. You use the same data structures and algorithms.

            I think you’d be surprised, try picking up rust for some advent of code challenges. If you know Java Streams and C/C++ lower level programming all that you’re missing is some pattern matching.

        • Dandroid
          link
          fedilink
          English
          94 months ago

          That feeling when you’re not a recent CS grad anymore 😭

          I never even heard of rust when I graduated in 2016.

          • @BURN
            link
            English
            04 months ago

            deleted by creator

        • Ghostalmedia
          link
          English
          24 months ago

          If I were to guess, it’s not recent grads making those posts. I got the sense those comments were coming from people who had been around for a while. Folks who are now senior enough to be trapped in draining meetings all day, and have to manage a family a night.

          The work day and home life can get longer and more exhausting the further the older you get.

      • P03 Locke
        link
        fedilink
        English
        104 months ago

        Yeah, Rust is cool, but every CS grad and their mother knows Java.

        Sure, twenty-five years ago, when Sun was pushing their language hard into colleges everywhere.

        Now? Sun Microsystems doesn’t even exist, and everybody hates the JVM in an ecosystem where VMWare, Docker, and Kubernetes do the whole “virtual machine” model much better.

        • Cosmic Cleric
          link
          English
          104 months ago

          Now? Sun Microsystems doesn’t even exist

          That was a long, long, long time ago.

          Java has continued to be very popular after Oracle purchased Sun Microsystems.

        • @uranibaba
          link
          English
          74 months ago

          Can’t say I agree. It feels like an almost even 50/50 split between Java and C# when I look at job postings.

      • @[email protected]
        link
        fedilink
        English
        54 months ago

        I think rust is a very pragmatic choice, lemmy is decentralized, the security benefits are a necessity when it comes to self hosters donating hardware

          • Dessalines
            link
            fedilink
            English
            24 months ago

            After working in java for over a decade, I will never use another garbage-collected language if I can avoid it again. I still have nightmares about debugging memory build-ups and having to trace down where to do manual garbage collection. I remember my shop eventually just paid for 32 GB ram servers, and java filled those up too.

            Rust doesn’t have these problems because its not a garbage collected language like java or go, and has an ownership-based memory model that’s easy to work with.

            • @[email protected]
              link
              fedilink
              English
              14 months ago

              Is that still a problem in newer java versions? I have to admit I have only written simple things in java.

              • Dessalines
                link
                fedilink
                English
                14 months ago

                Garbage collection is by nature imperfect, its impossible for it to always be correct about when and what things to free up in memory. The best option is to not use a garbage collected language.

                • @kaffiene
                  link
                  English
                  14 months ago

                  Wow. It’s amazing that anyone ever got anything to work in java. Must have never got used for anything

            • @kaffiene
              link
              English
              14 months ago

              That wasn’t a memory safety issue, that was a what the fuck were you thinking design issue. It would have been batshit in any language

      • @[email protected]
        link
        fedilink
        English
        04 months ago

        Yeah, Rust is cool, but every CS grad and their mother knows Java.

        This is quite an outdated view I would say.

        • Ghostalmedia
          link
          English
          14 months ago

          Perhaps, but a lot of devs wanted to contribute to a Java client, and that’s what they were saying.

    • 0x1C3B00DA
      link
      fedilink
      254 months ago

      Lemmy doesn’t have to have missing features for someone to want to write their own implementation. And in a decentralized system you want multiple implementations to exist. This is a good thing

    • @BURN
      link
      English
      194 months ago

      It seems to be more language focused than hard to PR against the main repo.

      Java is much more widely known than Rust, which means a much larger pool of developers. I never contributed to the original Lemmy server because I couldn’t wrap my head around a full production scale rust project. I’ll very likely contribute to this because I work with production Java code daily. Im sure I’m not the only other dev who has run into this.

      Also maybe there’s just too many disagreements with the Lemmy owners, who are a bit extreme for a lot of people.

    • Sean TilleyOP
      link
      English
      64 months ago

      Trust and Safety tooling, apparently.

      • kersploosh
        link
        fedilink
        English
        4
        edit-2
        4 months ago

        This looks like the major driver of the project, IMO. The Sublinks roadmap is full of feature ideas geared toward better moderation, both at the community and instance level.

  • @soren446
    link
    English
    60
    edit-2
    3 months ago

    deleted by creator

    • Ann Archy
      link
      English
      -84 months ago

      There used to be hookers, and blackjack. In fact just bring back the 80’s

      • @[email protected]
        link
        fedilink
        English
        194 months ago

        Java has been around for decades longer than Rust, comparing total code numbers doesn’t tell the whole story

      • @kameecoding
        link
        English
        74 months ago

        That’s not the whole story, most of the Java code that exists is proprietary, java is undoubtedly #1

        • @asdfasdfasdf
          link
          English
          2
          edit-2
          4 months ago

          You actually think there’s more Java code than JavaScript? Basically every website in the world feels the need to use JS nowadays.

          • @kameecoding
            link
            English
            -24 months ago

            obviously I wasn’t counting JS because by sheer volume, HTML+CSS+JS will outnumber everything because it’s the only combo for the browser.

            but if you restrict it as JS for Backend, then obviously it’s not even close to Java.

            • @asdfasdfasdf
              link
              English
              14 months ago

              If you can write off JS because “you have to use it because it’s the internet” then I can write off Java because “you have to use it for billions of 20 year old legacy applications”.

              • @kameecoding
                link
                English
                2
                edit-2
                4 months ago

                I am not writing it off, I am saying it has no competition in the browser… therefore irrelevant to the discussion at hand.

                and btw, even in the link https://madnight.github.io/githut/#/pull_requests/2023/4 Javascript is not first, Python is, over Java.

                but once again, you would actually have to look for the backed JS applications, you are not choosing java over JS for the web, at best you would choose JSF and that still uses javascript.

          • @kameecoding
            link
            English
            -64 months ago

            Js is not a real language and can’t hurt you

        • @[email protected]
          link
          fedilink
          English
          54 months ago

          If only… More seriously, I want Lemmy/Kbin/Sublinks to succeed, and the development rhythm of Lemmy made me perplex for a while.

          A new option with a more popular language could address this.

        • @Archer
          link
          English
          3
          edit-2
          4 months ago

          Check the back of every dollar for an Oracle database support contract, that’s how they get you!

    • @kameecoding
      link
      English
      144 months ago

      Every year since Java existed

    • @kaffiene
      link
      English
      74 months ago

      A year in which the number of Java developers and ecosystem dwarfs that of Rust.

    • @ohlaph
      link
      English
      74 months ago

      Java is still a strong language.

    • cum
      link
      fedilink
      English
      3
      edit-2
      4 months ago

      I think the people who say this and think Rust is the second coming of Jesus, just don’t code. You choose the right language that’s needed for the job. Server stuff like this is Java’s bread and butter. As amazing as Rust is, it has proven to not be a great choice for Lemmy’s development.

      • @hansl
        link
        English
        124 months ago

        I’m curious why you say Rust “ has proven “ to not be a great choice. There is a lack of Rust programmers, but its been the fastest growing community on GitHub for multiple years now, and has proven to be viable at all level of the stack.

        Full disclaimer: I code and work in Rust daily on the backend and frontend.

        • @[email protected]
          link
          fedilink
          English
          64 months ago

          Full disclaimer: I code and work in Rust daily on the backend and frontend.

          Would you and your colleagues be interested in contributing to Lemmy’s codebase? I’m genuinely asking, I’m still surprised by the low number of contributors for a project that has 40k active monthly users

          • @hansl
            link
            English
            24 months ago

            I barely have time to contribute to fix bugs in the dependencies I use. If I had more time for OSS contributions I might, but I’m not in my 20s anymore and when I’m not at work I’m taking care of my family.

            My colleagues and friends are free to do as they please.

            • @[email protected]
              link
              fedilink
              English
              34 months ago

              I guess that’s the same for most of the userbase. Which is probably why switching to a more spread language could increase the number of contributors.

        • @[email protected]
          link
          fedilink
          English
          3
          edit-2
          4 months ago

          Not to mention a lot of massive companies also use it at every part of the stack, Rust is good at it all and it is beautifully and perfectly suited for tasks like these.

  • Margot Robbie
    link
    English
    404 months ago

    Having a frontend rewrite seemed more critical than trying reimplementing the backend in a different language.

    Remember, Lemmy had 4 years of development to iron out bugs, and this is essentially promising to make something in months that has a fully compatible backend to support all the third party apps, while adding features on top of what Lemmy has, and with a better front end with better mod tools to boot, with a complete rewrite of everything.

    The scope of this project has planned for is already unviable. Suppose that Sublinks does reach feature parity to the current version of Lemmy, congratulations, the backend or mod tools is not something a regular user is going to notice or care about at all, all they will know is that suddenly, there are weird bugs that wasn’t there before, and that causes frustration.

    And this project is going to get more developer traction because… Java?

    I’d like to be proven wrong, but I’m very sceptical about the success of Sublinks, because it look like a project that was started out of tech arrogance to prove a point than out of a real need, I don’t work in tech, but the general trajectory of these kind of projects is that “enthusiasm from frustration” can only take you so far before the annoyance of dealing with mundane problems piles up, and the project fizzles out and ends with a whimper.

      • Fudoshin ️🏳️‍🌈
        link
        fedilink
        English
        214 months ago

        Java is a corporate language that most devs hate. Rust (Lemmy) is more popular as a hobby language that devs enjoy hacking in for fun.

      • @[email protected]
        link
        fedilink
        English
        9
        edit-2
        4 months ago

        Just peeking at the source code and it all looks like pretty standard stuff. Looks just like apps I’ve worked on at several jobs.

        Is it sexy? No. But a lot of people have experience with this and could help develop.

        Only time will tell if this project pays off though

      • Margot Robbie
        link
        English
        54 months ago

        I’m pretty sure Nutomic was a Java dev before starting work on Lemmy and learning Rust from scratch. That by itself should already speak volumes.

        One-Up projects like this rarely ever turn out well, that’s from my own experiences. Even though this isn’t a popular view, I still think I’m right on this one, we can circle back in say, 6 months, to see if my predictions are right.

        • @[email protected]
          link
          fedilink
          English
          74 months ago

          I’m pretty sure Nutomic was a Java dev before starting work on Lemmy and learning Rust from scratch.

          That is true, I used to be an Android developer and then learned Rust by writing code for Lemmy. Are you by any chance my new stalker?

          And if we’re comparing the languages, the fact alone that there are no Nullpointerexceptions makes Rust infinitely better than Java for me. I also agree that this sort of copycat project will soon be forgotten. For example have you ever heard of Rustodon?

          • Margot Robbie
            link
            English
            154 months ago

            Are you by any chance my new stalker?

            No, it was on that AMA you guys did months ago, and I remember things about people.

          • @[email protected]
            link
            fedilink
            English
            14 months ago

            there are no Nullpointerexceptions makes Rust infinitely better than Java for me.

            what’s wrong with having null pointer exception?

            • Tom
              link
              fedilink
              English
              2
              edit-2
              4 months ago

              Null is terrible.

              A lot of languages have it available as a valid return value for most things, implicitly. This also means you have to do extra checking or something like this will blow up with an exception:

              // java example
              // can throw exception
              String address = person.getAddress().toUpperCase();
              
              // safe
              String address = "";
              if (person.getAddress() != null) {
                  person.getAddress().toUpperCase();
              }
              

              There are a ton of solutions out there. Many languages have added null-coalescing and null-conditional operators – which are a shorthand for things like the above solutions. Some languages have removed the implicit nulls (like Kotlin), requiring them to be explicitly marked in their type. Some languages have a wrapper around nullable values, an Option type. Some languages remove null entirely from the language (I believe Rust falls into this, using an option type in place of).

              Not having null isn’t particularly common yet, and isn’t something languages can just change due to breaking backwards compatibility. However, languages have been adding features over time to make nulls less painful, and most have some subset of the above as options to help.

              I do think Option types are fantastic solutions, making you deal with the issue that a none/empty type can exist in a particular place. Java has had them for basically 10 years now (since Java 8).

              // optional example
              
              Class Person {
                  private String address;
                  
                  //prefer this if a null could ever be returned
                  public Optional getAddress() {
                      return Optional.ofNullable(address);
                  }
                  
                  // not this
                  public String getAddress() {
                      return address;
                  }
              

              When consuming, it makes you have to handle the null case, which you can do a variety of ways.

              // set a default
              String address = person.getAddress().orElse("default value");
              
              // explicitly throw an exception instead of an implicit NullPointerException as before
              String address = person.getAddress().orElseThrow(SomeException::new);
              
              // use in a closure only if it exists
              person.getAddress().ifPresent(addr -> logger.debug("Address {}", addr));
              
              // first example, map to modify, and returning default if no value
              String address = person.getAddress().map(String::toUpperCase).orElse("");
              
        • Dessalines
          link
          fedilink
          English
          6
          edit-2
          4 months ago

          I also was a professional java dev, and also had to use spring boot in most corporate environments.

          I don’t wanna knock anyone’s re-write, because I know how difficult it is to dissuade someone when they’re excited about a project. But to me, starting a new project or doing a rewrite, is the best opportunity to learn a newer, better language. We taught ourself Rust by coding lemmy, and I recently learned Kotlin / jetpack compose because I wanted to learn android development. Learning new languages is not an issue for most programmers; we have to learn new frameworks and languages every year or so if we want to keep up.

          This is potentially hundreds of hours of wasted time that could be spent on other things. Even if someone absolutely hates Rust and doesn’t want to contribute to the massive amount of open issues on Lemmy, there are still a lot of front-ends that could use more contributors.

        • originalucifer
          link
          fedilink
          04 months ago

          it it common to announce a ‘major rewrite’ without having it complete?

          i mean, at the moment, theres little to discern it from lemmy at the moment… why make a big public proclamation about it before you even touch the front end?

    • @[email protected]
      link
      fedilink
      English
      154 months ago

      Lemmy had 4 years of development to iron out bugs

      Lemmy had 4 years to accrue technical debt and make foot-guns first-class features. A rewrite is probably exactly what it needs.

      • @[email protected]
        link
        fedilink
        English
        12
        edit-2
        4 months ago

        Have you read the source code? I’m not trying to be a smartass, I’m genuinely curious.

        • @[email protected]
          link
          fedilink
          English
          104 months ago

          I have and if I’m honest I’m probably a little bit too harsh. I think the bigger issue is honestly the priorities of the dev team. There’s good reason that this project is focussing on moderation tooling.

            • @[email protected]
              link
              fedilink
              English
              9
              edit-2
              4 months ago

              Some things that seem hard to argue with:

              • A mod panel with things like ‘add moderator’ (maybe this could be attached to the new moderator view?)
              • Targeted reports (choose who receives it; admin/moderator)
              • Moderation actions on jerboa
              • Moderator edits. There’s a fine line here and I can understand why you wouldn’t want total edit capabilities but it’d be nice to at least be able to do things like mark as nsfw and add content warnings. This sort of feature should also probably target megathreads
              • Private communities (I know local only communities are in the works but there’s a whole mess of other criteria that would be useful)

              My own personal wishlist:

              • Karma requirements
              • First class wikis
              • Hashtags (I actually think a super simple stopgap solution here is to just have them link to the appropriate search page)
              • Flairs

              There’s some other stuff that I have seen PRs for and I do understand y’all are working hard. I appreciate the work you’ve done so far and the communities you’ve helped build. The Internet is undoubtedly a better place for it.

              • @[email protected]
                link
                fedilink
                English
                64 months ago

                Dessalines is currently working on mod actions for Jerbia. Someone recently made a PR for moderator edits but it seems there was not enough interest and it was closed by the author. Better reports handling would be nice, but if you read the issue its not really clear how this should work. Private communities are on the roadmap for this year.

                Karma is intentionally left out of Lemmy because it has many negative effects. Wikis make more sense as a standalone project, in fact Im working on something. Flairs are also potentially on the roadmap. For hashtags I dont really see the benefit as they would serve a very similar purpose to communities.

                • @[email protected]
                  link
                  fedilink
                  English
                  24 months ago

                  With regards to hashtags I think the utility is mostly in searching among similar things within a community. Suppose there’s a community that serves a purpose like r/askhistorians, stackexchange, or like what I’m trying to do over at [email protected]. In each of those cases, it is enormously useful to be able to search the community by subtopic. Obviously, this could be solved in other ways, but hashtags are probably the simplest to understand and implement.

                  Very excited to see the outcome of your Ibis project, but I think Lemmy native wikis would see significantly more activity. The easiest implementation I can imagine is a slightly altered frontend for communities marked wikis that also handle some well known syntax (like [[link]] popularized by pkm systems) for internal links. That is links to posts by the same name within a community.

                  Currently, I’m working on a lemmy bot that handles exactly this internal linking, and hashtag functionality, then builds a static site with support for github pages (so the end result is both a linked community and a seperate site), but I’d much rather have this functionality built into lemmy. To be frank, I’d much rather be trying to build this functionality into lemmy and if I wasn’t nearly certain it’d get shot down as out-of-scope, I’d probably be doing that.

                  I know you’re not particularly fond of growth based arguments for new features, but I sincerely believe that the thing that made reddit great in those early days was the tendency for communities to compile resources (particularly for niche and hobby communities). This gave the communities a certain depth that is nearly impossible with posts alone. If that were a first-class feature of Lemmy, I think you’d very quickly see Lemmy fill the niche that federated wiki projects and supplementary wiki services have so far failed to.

              • @[email protected]
                link
                fedilink
                English
                24 months ago

                karma requirements and hashtags doesn’t seem right since the former will make people to farm karma for the requirements which is one of the reasons why newbies on reddit always dump post until they get a decent karma. lemmy is not a microblogging site, hashtags have better use in platforms like mastadon. post flairs should be implemented though.

                • @[email protected]
                  link
                  fedilink
                  English
                  3
                  edit-2
                  4 months ago

                  hashtags have better use in platforms like mastadon

                  Says who? Because that’s how the old platforms used it? I think we should really be moving past the direct influence of these corporate platforms and on the fediverse that probably means something of a well understood common language (like @user@instance or !group@instance). Hashtags were only ever a thing on twitter because the users just started using them and full text search was sufficient to handle it (this is more or less the position we’re in on lemmy). Direct support didn’t come till much later.

            • @[email protected]
              link
              fedilink
              English
              4
              edit-2
              4 months ago

              The ones on the Sublinks roadmap are interesting, for instance the warning system: https://github.com/orgs/sublinks/projects/1/views/7

              Create a way to create a warning system for users. For example, a user gets a warning for posting a broken link multiple times. We don’t want to ban them for that. Or a admin gives a user a Warning with a reason. Create a rules system for auto actions like banning for some time or forever. Consider adding types of warnings. This should also track bans from communities for admin-level auto actions. The profile page shows strikes similar to Mastodon for Mods/Admins only and the user that owns the profile. Examples, warnings in each community, and bans. Rules will be applied to counts of warning types or total warnings over time. 3 warnings within a month is a ban for a month, for example.

              There was also this list from a few months ago: https://discuss.online/post/12787?scrollToComments=true

      • @Sir_Simon_Spamalot
        link
        English
        34 months ago

        And you think that a rewrite would magically solve all those technical debts?

        • @[email protected]
          link
          fedilink
          English
          54 months ago

          Magically no, but sometimes a clean slate is easier than a refactor. I’m speaking generally though, I’ve never looked at Lemmy’s code, and I’m not even who you originally replied to.

    • @laughterlaughter
      link
      English
      64 months ago

      There are some projects that start because of “tech arrogance” as you describe the current situation. MariaDB, Git, LibreOffice are some of the most famous ones, but I’m sure there are more.

    • Ann Archy
      link
      English
      24 months ago

      But does it have blockchain AI integration?

  • katy ✨
    link
    fedilink
    English
    394 months ago

    an alternative Java-based backend

    kill it with fire

    • @MashedTech
      link
      English
      224 months ago

      Next step, is to remake Lemmy in JavaScript. Pure JavaScript, no typescript, only express, nothing else

      • katy ✨
        link
        fedilink
        English
        134 months ago

        rewrite it in perl with a flat file database.

    • P03 Locke
      link
      fedilink
      English
      13
      edit-2
      4 months ago

      an alternative Java-based backend to Lemmy’s Rust-based one

      Going from a modern well-designed language to an old-and-busted, kitschy, memory-hogging, bloated language. This is literally a step backwards.

      Rust, Go… hell, even Ruby-on-Rails or whatever Python is offering nowadays would be a better choice.

      • Dandroid
        link
        fedilink
        English
        104 months ago

        I’m a long time Java developer who was recently moved to a project written in Go. All I can say is: What. The. Fuck. I swear, the people who designed the syntax must have been trying to make every wrong decision possible on purpose as a joke. The only think I can think of is that they only made design decisions on the syntax while high on shrooms or something.

        Like, why in the actual fuck does the capitalization of a function change the scope??? Who thought that was a good idea? It’s not intuitive AT ALL. Just have a public/private keyword.

        • @kaffiene
          link
          English
          24 months ago

          I did a lot of Java prior to doing Go. I think they’re both good. I don’t like the Go privacy/scope thing and I genuinely hate it’s error handling but it’s pretty much 90% good pragmatic choices IMO. That said, I still think Java is a fantastic language and it makes a lot of sense for something like Lemmy

      • @[email protected]
        link
        fedilink
        English
        104 months ago

        Modern Java isn’t that bad, and with new developments like the graalvm and cloud native builds, or what they are called, the footprint of a modern Java app can be comparable to an golang app.

        Modern Java kinda has the same image problem as modern PHP. Not saying is all great, but it sure has seen quite the improvements in the last years

        • @[email protected]
          link
          fedilink
          English
          34 months ago

          they are also working to make developers have less boiler plate. java might be an old language but the development has not stopped but only going better these days.

      • @[email protected]
        link
        fedilink
        English
        94 months ago

        Nah, Java is alright. All the old complicated “enterprise” community and frameworks gave it a bad reputation. It was designed to be an easier, less bloated C++ (in terms of features/programming paradigms). It’s also executed fairly efficiently. Last time I checked, the same program written in C would typically take 2x the time to complete in Java; whereas it would take 200x the time to complete in Python. Here’s some recent benchmarks: https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/python3-java.html

        I haven’t had a chance to try Rust yet, but want to. Interestingly, Rust scores poorly on source-code complexity: https://benchmarksgame-team.pages.debian.net/benchmarksgame/how-programs-are-measured.html#source-code

      • @beefcat
        link
        English
        94 months ago

        Or C#, it’s literally “Java, but good”.

        The only time I would choose Java for a new project is if I had a hard dependency on something that only works with Java…

          • @beefcat
            link
            English
            3
            edit-2
            4 months ago

            I understand that being a problem for Rust, but not for many of the other “better than Java” languages on this list. Like, I dunno…C#?

            If I’m being honest though, I just really hate Oracle, and that’s enough to give me pause over anything they dip their fingers in.

              • P03 Locke
                link
                fedilink
                English
                34 months ago

                I think C# is probably more popular than it advertises here, but not on GitHub.

                • @beefcat
                  link
                  English
                  1
                  edit-2
                  4 months ago

                  C# is regularly under-represented in OSS, in part because for most of it’s existence, the primary implementation (.NET Framework) was not open source or cross platform. It is also very popular in fields where open source is not the norm (game development, bespoke backend infrastructure, embedded apps).

              • @beefcat
                link
                English
                0
                edit-2
                4 months ago

                I said it was easy to find C# developers, not that there were more of them on Github.

                If the number of possible contributors on github is the big factor here then Python is the obvious choice at 18%.

        • Aatube
          link
          fedilink
          14 months ago

          Or Kotlin, which is much more “Java but good” as it even runs on the JVM

          • @beefcat
            link
            English
            1
            edit-2
            4 months ago

            Yeah, but then you still have an Oracle dependency in your stack 🤮

            • Aatube
              link
              fedilink
              14 months ago

              You can switch to Kotlin Native, which depends on C libraries, or Kotlin JS, which depends on whatever libraries your JS runner has. No matter whatever Oracle has done, they produce a pretty good library, API spec and OpenJDK.

        • @[email protected]
          link
          fedilink
          English
          44 months ago

          There’s a user made OpenAPI spec: https://github.com/MV-GH/lemmy_openapi_spec - You probably mean that one

          I’ve had similar issues as you mentioned that the dev did fix - but yea, Typescript has less precision than Rust (the source) or the openapi spec. And the Typescript client is build for Lemmy-JS and not build an example for other language client libraries…

          Though the OpenAPI Documents in C# and Java are based on reflection of the source itself, and Rust doesn’t have Reflection like that… So it’s probably difficult for them to add without manually maintaining the OpenAPI specs

        • db0
          link
          fedilink
          English
          24 months ago

          Same. When making pythorhead, I had to dig into the rust code to understand things.

  • hamid
    link
    English
    314 months ago

    Based on all the other threads and cross posts it just seems like this software is being created because Jason Grim doesn’t like the lemmy devs or their politics. I guess that’s as good of a reason to fork as any. I’m happy with the way lemmy is and how its being created so I have been doing monthly donations to them for its development.

    • @hansl
      link
      English
      224 months ago

      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.

      • hamid
        link
        English
        64 months ago

        I’m not sure I believe “faster” progress really means anything when two communists are creating a hobby software that isn’t really for business or necessarily targeting growth at all costs.

  • lionkoy5555
    link
    English
    28
    edit-2
    4 months ago

    a missed opportunity to name it Jemmy

    I’m just here for the joke

    EDIT: sentence structure

  • @kameecoding
    link
    English
    204 months ago

    I like this, I will contribute to this, I think a lot of Java haters in this thread fail to realize just how massive Java is compared to everything else.

    Rust might be the latest, hottest, bestest Java killer out there and it might be a completely superior language to Java, doesn’t matter, it’s dwarfed in terms of how many people actually use it for real projects, projects that should run for years and years. Even if Rust is the true Java killer, it’s gonna take a good few more years for it to kill java, measured in decades, there is just way too many projects and critical stuff out there that is running on Java, that means lots of jobs out there for java, still and still more.

    This means there are a lot of senior Java programmers out there with lots of years of experience to contribute to this project.

    Plus Lemmy itself having alternatives and choices is just a good thing.

    • @CAVOK
      link
      English
      104 months ago

      Agreed. I mean COBOL is still a thing, and that’s a language that’s been dead for 30+ years.

    • nickwitha_k (he/him)
      link
      fedilink
      English
      84 months ago

      I am not a fan of Java. However, I think that you are 100% correct. This is a potentially very useful stack to have available and I hope that the two projects track together well.

      This project has potential for high velocity development that Lemmy will never be able to match, purely because of the languages. Rust is, factually, slower to develop in than Java, even for experienced devs. Add to that the greater population that is comfortable with Java, and you have a recipe for really pushing interesting things and innovating quickly. Possibly establishing a relationship somewhat like Debian Sid to Debian Stable. It could also be interesting to have some low-level, Rust modules that are shared between the two when Lemmy gets to 1.0 (API stability), if there is something that is more optimally implemented in Rust but that would introduce more coupling.

    • @thedeadwalking4242
      link
      English
      44 months ago

      Languages won’t grow if you ditch them for other ones. There’s lots of reasons to use rust, outside of the size of the project

      • @kameecoding
        link
        English
        94 months ago

        I think you will find that the biggest reason to use a language is to get paid for it and there Java is very well positioned

        • @thedeadwalking4242
          link
          English
          34 months ago

          That’s the reason for for hire devs yeah, but if you are starting a new project ( especially a community one like lemmy where the profit motive is different) choosing your tech stack is a complex decision

    • Aatube
      link
      fedilink
      14 months ago

      Rust is as much of a Java killer as C++ is. You could say Rust is the C++ killer, but I really don’t see how Rust would be that comparable to Java, which operates at a higher level instead of memory and pointer management. IMO, Kotlin is the Java killer.

  • Stamets
    link
    English
    184 months ago

    I’ve been hearing a lot of good things for a while. Lookin forward to it.

    • @[email protected]
      link
      fedilink
      English
      04 months ago

      I’m hearing hype from the people making it… dunno why anyone else would have anything positive or negative to say yet