You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Bruno Baptista <br...@gmail.com> on 2019/04/01 07:22:26 UTC
Re: microprofile reactive streams
Hi Romain,
Do you have your doubts about the spec whiten somewhere?
Can you please explain the problem?
Cheers
Bruno Baptista
http://twitter.com/brunobat_
> On 31 Mar 2019, at 21:24, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> Hi guys
>
> From what I saw it got released and i guess api will not change much and spec will sadly not be dropped without actions.
>
> Wonder if anyone else had a look, share or notmy view and wonder if we want to cover it or not @geronimo.
>
> I had some PoC when it was still a beta, can try to push it forward later this week or next one if you think it makes sense or we can also be vocal that it is inconsistent with the jvm and useless at platform level if we agree on that to try to make it removed from microprofile - guess it makes sense in se until j11 is mainstream?
>
> Wdyt?
>
>> Le mer. 21 nov. 2018 à 08:52, Romain Manni-Bucau <rm...@gmail.com> a écrit :
>> Hi guys,
>>
>> Seems MP insists to creates this spec even if it is risky and likely to be dropped after so I think we have to impl, any objection to create a repo for it?
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book
Re: microprofile reactive streams
Posted by Bruno Baptista <br...@gmail.com>.
Thanks Romain
Bruno Baptista
https://twitter.com/brunobat_
On 01/04/19 08:55, Romain Manni-Bucau wrote:
> Hi Bruno,
>
> Yes, in https://github.com/eclipse/microprofile/issues/57
>
> Long story short this API just duplicates what is already there. I
> agree the API can be better but it is the worse solution to introduce
> yet another API for that, and the disaster is to corrupt other coming
> specs with this API instead of relying on standards and JVM ones. It
> is really the kind of "bad good" idea - it looks great but when you
> start using it you are just locked so you need a bridge....so you
> didn't gain anything except adding some noise in user land.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le lun. 1 avr. 2019 à 09:22, Bruno Baptista <brunobat@gmail.com
> <ma...@gmail.com>> a écrit :
>
> Hi Romain,
>
> Do you have your doubts about the spec whiten somewhere?
> Can you please explain the problem?
> Cheers
>
> Bruno Baptista
> http://twitter.com/brunobat_
>
> On 31 Mar 2019, at 21:24, Romain Manni-Bucau
> <rmannibucau@gmail.com <ma...@gmail.com>> wrote:
>
>> Hi guys
>>
>> From what I saw it got released and i guess api will not change
>> much and spec will sadly not be dropped without actions.
>>
>> Wonder if anyone else had a look, share or notmy view and wonder
>> if we want to cover it or not @geronimo.
>>
>> I had some PoC when it was still a beta, can try to push it
>> forward later this week or next one if you think it makes sense
>> or we can also be vocal that it is inconsistent with the jvm and
>> useless at platform level if we agree on that to try to make it
>> removed from microprofile - guess it makes sense in se until j11
>> is mainstream?
>>
>> Wdyt?
>>
>> Le mer. 21 nov. 2018 à 08:52, Romain Manni-Bucau
>> <rmannibucau@gmail.com <ma...@gmail.com>> a écrit :
>>
>> Hi guys,
>>
>> Seems MP insists to creates this spec even if it is risky and
>> likely to be dropped after so I think we have to impl, any
>> objection to create a repo for it?
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
Re: microprofile reactive streams
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi Bruno,
Yes, in https://github.com/eclipse/microprofile/issues/57
Long story short this API just duplicates what is already there. I agree
the API can be better but it is the worse solution to introduce yet another
API for that, and the disaster is to corrupt other coming specs with this
API instead of relying on standards and JVM ones. It is really the kind of
"bad good" idea - it looks great but when you start using it you are just
locked so you need a bridge....so you didn't gain anything except adding
some noise in user land.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le lun. 1 avr. 2019 à 09:22, Bruno Baptista <br...@gmail.com> a écrit :
> Hi Romain,
>
> Do you have your doubts about the spec whiten somewhere?
> Can you please explain the problem?
> Cheers
>
> Bruno Baptista
> http://twitter.com/brunobat_
>
> On 31 Mar 2019, at 21:24, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> Hi guys
>
> From what I saw it got released and i guess api will not change much and
> spec will sadly not be dropped without actions.
>
> Wonder if anyone else had a look, share or notmy view and wonder if we
> want to cover it or not @geronimo.
>
> I had some PoC when it was still a beta, can try to push it forward later
> this week or next one if you think it makes sense or we can also be vocal
> that it is inconsistent with the jvm and useless at platform level if we
> agree on that to try to make it removed from microprofile - guess it makes
> sense in se until j11 is mainstream?
>
> Wdyt?
>
> Le mer. 21 nov. 2018 à 08:52, Romain Manni-Bucau <rm...@gmail.com>
> a écrit :
>
>> Hi guys,
>>
>> Seems MP insists to creates this spec even if it is risky and likely to
>> be dropped after so I think we have to impl, any objection to create a repo
>> for it?
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
>