Makes sense to me. Let's deprecate for the 2.52.0 release unless there is
some objection. You can also look at the maven central downloads (I believe
all PMC and maybe all committers can view this) compared to other Beam jars.
Kenn
On Mon, Oct 16, 2023 at 9:28 AM Jan Lukavský wrote:
> Sure,
Sure, that would be probably the preferred way to go. For now, I'm
trying to get some feedback, if there are some real-world users who
might miss the API. Currently, the only value I see is that Euphoria
adds an additional level of indirection for user code. The expansion
goes like this:
Can we just deprecate it for a while and then remove completely?
—
Alexey
> On 13 Oct 2023, at 18:59, Jan Lukavský wrote:
>
> Hi,
>
> it has been some time since Euphoria extension [1] has been adopted by Beam
> as a possible "Java 8 API". Beam has evolved from that time a lot, the
>
Hi,
it has been some time since Euphoria extension [1] has been adopted by
Beam as a possible "Java 8 API". Beam has evolved from that time a lot,
the current API seems actually more elegant than the original Euphoria's
and last but not least, it has no maintainers and no known users. If
