• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle




  • That’s the thing though, because it’s kind of a paradox. If you had a single team working on it, then sure, it might be easier to just learn Rust. However, on an open source project, especially a volunteer driven one, that isn’t necessarylily the case. Your average enterprise dev probably isn’t even considering rust as an option yet, because it’s still in early stages in terms of tooling and support infrastructure.

    I made another comment in this post, but as it is right now languages like Java and C# make up significantly more projects/job positions than rust. If you want to get more contribution from volunteer devs, it needs to be in a language that devs are comfortable with. Most people won’t want to learn a whole new programming language for a volunteer project when they’re already working a full-time job in a different language. I explained this in the other post, but that’s why I think having both projects is still beneficial. Sublinks and Lemmy can (hopefully) continue to exist at the same time and benefit from each other’s development, especially if they stay API compatible. Sublinks will have a lower barrier to entry (thus maybe a quicker development cycle with more people involved), while Lemmy will help contribute to the validation of rust as a language for production code.

    Also “rust is the future” implies that’s the only programming language that is worth learning, which is simply not the case. Different languages are better at different things. There will never be a single language that’s best at everything. Even for a specific task, multiple languages are good at doing the same thing. For example, Go, Rust, C#/any .NET, and Java/any JRE can all do REST services like Lemmy pretty well. Of those, I wouldn’t even say Rust is the best choice, because its frameworks are all still pretty new.

    Other languages are growing and evolving as well. Even old languages like Java and C++ have had significant improvements in their modern standards (Java records, C++ smart pointers, etc.). Hell, even COBOL got a new standard version as of 2023 (if I had to guess, this didn’t do much for it though). Just because certain languages are bad right now doesn’t mean they will stay bad forever.




  • Sorry for being unclear, I wasn’t trying to say language doesn’t make a difference (e.g. static vs. dynamic typing would make a big difference). I also personally like the error handling of rust a lot more, even if it does take a bit getting used to when my education has mostly been in languages with Java-style exception handling.

    I mostly meant that the language-level performance and features aren’t necessarily holding the codebase back in a debate between Java and Rust for a lemmy-like REST API. As long as the developers are aware of the pitfalls of Java (null, mutation, error-handling, etc.), it’s possible to have good code.

    I just think that from a maintainability standpoint, a Java-style codebase is much easier for most people to read, understand, and maintain because that’s what most people are familiar with. Especially when many of the developers are volunteer contributors, that type of thing could make a big difference.

    The main problem with Rust is that it’s only starting to get adoption now, it isn’t taught in most education curriculums, and it’s industry use is pretty small at the moment. It’s kind of a catch-22, because rust adoption won’t increase unless large projects like lemmy exist. But that’s also why I think having more options is also fine. Sublinks might get more developers short term because of its language, but that also doesn’t mean it’ll completely replace Lemmy. Both projects can exist at the same time, and hopefully benefit from each other’s development.


  • A lot of people here seem to think that Java code is awful and disgusting and no projects should ever use it. The thing about popular languages is that more code existing in a language inevitably means a lot of it ends up being bad. The same thing will likely happen to rust as it gets popular, but that isn’t exactly a problem. It’s possible to have a well-maintained Java codebase.

    Debate between functionality of the actual programming languages at this point is pretty meaningless, if they have good development standards then a Java program could end up just as well maintained as rust. Any time saved by compiler enforcement of specific standards (like no using null) would be lost by the fact that the devs don’t know rust tooling. You could just have a requirement in PRs that null isn’t used. Both Java and Rust have usable frameworks for REST API development, so using one or the other comes down to familiarity.

    The idea that programming languages make code suddenly good or bad is pretty silly. Different languages have different language-level guarantees which can help produce good or working code. That being said, it’s not like it’s impossible to write good Java code, just like it’s not impossible to write bad rust code. Most people seem to be conflating guaranteed functionality and safety with maintainability, stability, and readability. Rust is still a new language, so although it’s great, Java will probably be the better choice for the latter 3 qualities.

    That being said, something like Kotlin would probably have been a better starting point since it can interact with Java (and works like Java in most cases) but also has some nice improvements like stricter null checking (Kotlin nulls are treated similarly to rust’s Option<T>, it’s just described as T? instead and the syntax is generally a lot more concise). There’s also the benefit of being able to write some code in Kotlin and some in Java since they are mostly cross-compatible.




  • Your sample size is 1. Sure, you can get a phone that won’t have battery swelling after 5-10 years. My old Samsung S9+ doesn’t have any swelling yet, and I’ve had it since around when it came out in 2018. Whether or not swelling happens to any given phone is more or less down to luck. You might want to avoid Samsung phones to be safe though because there was that whole battery swelling issue with almost every phone from the S20 downwards a few years ago. Other than that I don’t think there’s much of a difference*

    *Probably something to look for reports/statistics on though





  • The problem with chat apps is that as much as I would like to switch to other ones, I don’t really have a choice. The people I know use text, so even whatsapp is a stretch, let alone signal, xmpp, or matrix. When it isn’t text it’s normally Discord for my friend group, and I’m not going to attempt to explain Matrix to a bunch of non-technical people who just want to play games.


  • Unfortunately depending on the level of extremism they have a point. When you can’t even agree on what’s reality and what isn’t, it’s pretty hard to change someone’s mind.

    I originally heard this quote about using the Internet but the general sentiment applies to any extremist politics as well.

    Generally, people don’t log onto internet platforms to be proven wrong

    Extremists don’t talk about politics to change their viewpoints, they do it to rant and convince others (IMO)

    (At least this is often the case for US extremism, not sure about elsewhere)




  • My family’s cat just got diagnosed about a month ago :( He’s doing well so far with his insulin shots but it likely went unnoticed for a week or two because he’s a pretty reserved cat and normally hides from us. He’s been having trouble walking/jumping recently which is probably related, hopefully the insulin along with a changed diet (we’re mostly feeding him wet food now) will help him improve