Comments (10)
What about MicroProfile Reactive Operations. I know Operators as a term has been associated to at least Kubernetes and Kafka and might be confusing if you add MicroProfile to that list. Just a thought.
from microprofile-reactive-streams-operators.
-1 on Operators
from microprofile-reactive-streams-operators.
I think I do like "Reactive Operations"
from microprofile-reactive-streams-operators.
They are "operators" not "operations". It's a library of operators. I agree that "operators" is an overloaded term, but "operations" does not really work here.
from microprofile-reactive-streams-operators.
Combinators is another word that fits, but that has a few problems, it's quite a long word, and also it's possibly unfamiliar to a lot of people - combinators is a term commonly used in functional programming and could even scare off developers who are not familiar with functional programming.
from microprofile-reactive-streams-operators.
from microprofile-reactive-streams-operators.
We could consider acronyms - not sure whether there are any naming guidelines for MicroProfile, so far all the names are boring descriptive full names. But...
MPRC - MicroProfile Reactive Combinators
MROC/MPROC - MicroProfile Reactive Operators and Combinators
JRC - Java Reactive Combinators
JARC - JAva Reactive Combinators
JRSC - Java Reactive Streams Combinators
from microprofile-reactive-streams-operators.
MPRSC - MicroProfile Reactive Streams Combinators
Give the last suggestions are all a mouthful, I now wonder, if, in the context of reactive streams, the "operator" term does work ?
MPRSO - MicroProfile Reactive Stream(s) Operators ?
from microprofile-reactive-streams-operators.
From @venkats:
The motivation to get the implementation into the JDK for MicroProfile is convincing. Will the implementation be available for non-MicroProfile applications as well? From what I know so far talking to many developers, that will truly be welcome. From that point of view, calling it "MicroProfile Reactive Streams" may be rather limiting, but a more general name may be desirable.
I'm not sure whether the MicroProfile community would generally be for against having a MicroProfile project that didn't have "MicroProfile" in the name, but this is a good point, the library will be useful for more than just MicroProfile and if it gets broader uptake than just MicroProfile this will help adoption by the JDK, so perhaps consider leaving MicroProfile out of the name?
An argument against this though would be that it would be some excellent marketing for the awarewness of MicroProfile (and potentially Jakarta EE assuming MicroProfile becomes part of it) if the library was used outside of MicroProfile but had the MicroProfile name.
from microprofile-reactive-streams-operators.
As decided in the Reactive hangout today, "MicroProfile Reactive Streams Operators" is what we'll go with.
from microprofile-reactive-streams-operators.
Related Issues (20)
- FlatMapStageVerification.InnerSubscriberVerification rule 2.9 HOT 3
- ReactiveStreamsFactory.fromSubscriber is defined as Subscriber<? extends T> HOT 1
- Null expectation of flatMapCompletionStage & Stage.FlatMapCompletionStage HOT 3
- Stage type for collect(Supplier, BiConsumer) missing HOT 1
- Which to use for inner Publishers: buildRs or buildRs(ReactiveStreamsEngine)? HOT 2
- How to turn Builder.flatMap into a Stage.FlatMap? HOT 1
- Missing Stage types HOT 1
- ToGraphable not implemented by the interfaces its docs say they should HOT 1
- SubscriberBuilderVerification implicitly expects all SubscriberBuilder.build to return an instance of CompletionSubscriber.of
- PublisherBuilder and ProcessorBuilder doesn't document the requirement of immutability HOT 1
- mvn clean install broken as the javadoc does not build with recent JDKs (modules related)
- package-info.java contains the wrong package name
- Enable bnd baseline plugin and set package versions correctly
- Prepare for the 1.1 release
- SmallRye Mutiny - MicroProfile Reactive Streams Operator 2.0 Compatible Certification Request HOT 3
- Build error HOT 1
- MicroProfile Reactive Streams Operator implementation to version 2.0 HOT 2
- Jakarta EE 9.1 Alignment HOT 1
- Helidon - MicroProfile Reactive Streams Operator 3.0 Compatible Certification Request
- Upgrade to reactive-streams 1.0.4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from microprofile-reactive-streams-operators.