Lombok is a very divisive framework in Java, with strong opinions on both sides.
Given that, it's a bold choice to include Lombok in a library that other developers will pull into their stack - it's likely to make this a non-starter from those in the 'no' camp.
As Lombok is just compiler sugar, when building an SDK for other developers, it's probably less alienating to just write the boilerplate that Lombok saves you from.
I don’t get it. Why is this needed above and beyond the standard ways of configuring deployed services?
Martin Fowler about feature flags: https://martinfowler.com/articles/feature-toggles.html
Looks like an interesting project. Really cute logo. :)
How much does the flagd sidecar cost? Seems like that could be a lot of overhead for this one bit of functionality.
Where is the tldr? Anyone familiar…what does this do and why do we care about it being standards based?
This is a “standard” SDK for feature flags, allowing you to avoid vendor lock-in.
i.e., using feature flag SaaS ABC but want to try out XYZ? if you’re using ABC’s own DDK, refactor your codebase.
I appreciate that you can use the OpenFeature SDK with environment variables, and move into a SaaS (or custom) solution when you’re ready.
https://openfeature.dev/docs/reference/intro/
java version embeds lombok symbols lol
Forgive my ignorance, but what should it be doing instead?
Lombok is a very divisive framework in Java, with strong opinions on both sides.
Given that, it's a bold choice to include Lombok in a library that other developers will pull into their stack - it's likely to make this a non-starter from those in the 'no' camp.
As Lombok is just compiler sugar, when building an SDK for other developers, it's probably less alienating to just write the boilerplate that Lombok saves you from.