Java library to provide an API for beans and properties. (by JodaOrg)

Joda-Beans Alternatives

Similar projects and alternatives to Joda-Beans

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better Joda-Beans alternative or higher similarity.

Joda-Beans discussion

Log in or Post with

Joda-Beans reviews and mentions

Posts with mentions or reviews of Joda-Beans. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-09.
  • Don’t call it a comeback: Why Java is still champ
    17 projects | | 9 Aug 2022
    That means I don't forget about fields (as can happen if you're just doing `person.setX()` all the time). It's easy to see what is what when reading it. I can delete fields I don't want to initialize at the time. Yes, maybe immutable objects are the One True Way, but C# lets me choose (I can label properties with an initializer `init` rather than a setter `set` and then they're immutable).

    Kotlin offers stuff like this too because it's really useful toward creating code that's easy to create and maintain. Go also lets you initialize structs in a similar fashion.

    Java has come back to us a decade or more late with records. They're not bad, but they're only offering one thing. They don't cover what C#, Kotlin, Go, and other languages have offered for so long.

    The annoying thing about Java is that it doesn't feel pragmatic a lot of the time. It feels like the language hates stealing ideas from others. It's Java: people steal ideas from Java, not the other way around. People do crazy things just to get POJOs including Immutables (, AutoValue (, Lombok (, Joda Beans (, and maybe more. They generate lots of code at compile time or do funky runtime stuff.

    It just feels like Java misses the pragmatic stuff and still kinda doesn't want to handle that. I feel a bit silly harping on things like POJOs and setting data on a new object, but that's a big part of day-to-day stuff and it definitely pushes users away from Java towards languages that seem "better" simply because they don't have Java's oddly strong attachment to not offering simple value objects. Yes, again, records do something - but it feels like Java ignored how people are using Kotlin, Go, C#, and more and didn't go for something that would have been as widely applicable and pragmatic as it could have been.

    Java has a lot of great stuff like great GCs (yes), lots of cool research, great performance, and Project Loom is really exciting. I just wish the language would lean a little more practical.

  • With the recent changes to Discord's branding, here's a proposition for a new tagline for C#. Thoughts?
    4 projects | /r/csharp | 14 May 2021
    I know I've been talking about properties a bunch, but let's look at Java. Java Beans are terrible - so terrible that the community has a number of workarounds. Immutables ( lets you generate builders, Lombok ( has their annotations that do runtime and IDE magic, there's Joda-Beans (, there's the new Java Records if you want immutable-only and non-compatibility with lots of libraries, there are people using Kotlin for their data classes and Java for other things... Properties are this simple thing that lets C# work with the whole getter/setter pattern without being horribly annoying - there's just this weird { get; set; } thing that I can ignore because I don't care.


Basic Joda-Beans repo stats
8 days ago

Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.