We do want our individual communities to thrive as well. While it may not be urgent, if you have ideas to improve a community, please do reach out.

It’s tiered pricing. All the chains are doing it now. Jump through hoops or pay double.

I’d rather add more Jira stories.

For what? To keep track of who’s drinking coffee? Are you charging for coffee?

I don’t think Google Podcasts required that much maintenance. However it didn’t have the ads that YouTube Music does.

AntennaPod has been a perfect, free replacement.

They did allow users to upgrade once first.

Grabbed AntennaPod from the Play Store. It’s been a perfect replacement.

The entire scalping/resale market arguably shouldn’t exist, instead tickets should be refundable within reason, at which point the organiser can issue and sell new tickets.

I had to think about this for a minute, but this is exactly the way to handle it. Don’t allow direct transfers at all. You don’t get to pick who gets your tickets (and therefore scalping can’t exist.). But you still can refund your tickets (maybe with a SMALL fee) up to a couple hours before the event. I hope we don’t need legislation to say they have to be sold for the same price they were originally offered for. We don’t want an incentive for Ticketmaster to steal people’s tickets when a venue sells out.

And it can be in any language, but typically comes from someone who started with Java.

Okay, here we go. I’m going to spit out some bullshit and home someone corrects me if I’m wrong. I’ve looked for some explanations and this is what I’ve gotten.

Are you ready?

The Factory Pattern.

My understanding is that the purpose is a function to return any of several types of objects, but a specific type, not just an interface or whatever they might all inherit from.

I think most languages now have something like a “dynamic” keyword to solve this issue by allowing determination of the type only at runtime. (To be used with extreme caution.)

But most of the time I see the Factory pattern, it’s used unnecessarily and can only return one specific type. Why they would use a Factory pattern here and not just a plain old constructor confounds me.

Am I off base?

Seems like he’s worried you’ll Java everything up, which can be valid.

I think a good, easy example is whether your application should allow a selection of databases or be tied to one database.

You can make arguments for either, often (but not always) regardless of your use case.

Criticizing China in any way.

Out of all those languages, I wouldn’t choose C++, COBOL, or Java. Go, C#, and Rust all have benefits.

But regardless, the project exists and it’s generally better to contribute to the existing project than to rewrite it from scratch. We didn’t need two dozen Lemmy clients only for most of them to be abandoned, either. Our effort is limited, and fracturing it isn’t going to do anyone any favors.

Lemmy works pretty well at a large scale. It’s easier and more productive to bug fix and improve on the existing project in a new language than to reinvent the demonstrably working wheel in Java (of all things) that’ll bring its own, brand new set of distinct issues.

But hey, at least it’s not PHP.

You know what’s easier (and more productive) than starting a new project from scratch? Learning Rust. It’s the future anyway.

Think of it like email, which is also federated. You’ve chosen, say, Yahoo, but your email still works with Gmail, Apple, Hotmail, AOL, and whatever else people use these days.

Don’t tempt me. I’ve been meaning to put together a simple Rust API for ages and just haven’t gotten around to it. AI was still bad at Rust when I last tried, making up crates, etc.

I’ve read, uh, half the Rust book. So I get the basic concepts.

in case the developers of Lemmy decide to pull the plug

They literally can’t. It’s open source and publicly licensed. If they abandon the project (or even if we don’t like their direction), it can be forked (copied) and maintained by someone else.

In normal use cases I’d agree about performance. But on the scale of Lemmy it’s absolutely likely to make a difference long term.

And if you’re going to use a managed language, why not something that has less baggage and a brighter future, like C#? It’s as open and multiplatform as Java these days with less of the overzealous, Java-specific OOP culture.

If I’m looking to build skills in a new language, that language is probably going to be Rust and not Java. One of those languages has a bright future. The other is going to look a lot like Fortran in 15 years.

I expect real performance issues with Java at some point, especially compared to Rust. The initial difficulty in picking up the language is worth it if I never have to see another Factory pattern that only returns one type. Why just use a constructor when you can use idiopathic idiomatic java?

Everyone’s an idiot sometimes.