hi: Thanks for starting this discussion, in the streampark project, except for the streampark-console module is written in java, the rest of the total 40 modules are written in scala. rewrite the project using java is not a simple yes or no, it will involve refactor the project, and the migration of many core modules, in addition to the core contributors in the early days of the project, How many developers understand the implementation details of the project? And to be able to commit to this work? So I am pessimistic about this,
many modules(scala) is very stable, we have to consider the risk of refactor and RIO, at least in my opinion, at this stage, this point is not the reason that hinders the development of the project. If there is a new module, I think it can be implemented using java, e.g: https://github.com/apache/incubator-streampark/pull/2267 BTW, @Zhuoyu Chen, I think you can rewrite k8s-mode using java, We can start with a module and try this. Best, Huajie Wang Yuepeng Pan <[email protected]> 于2023年3月12日周日 20:36写道： > Nice proposal~ > I also agree with this suggestion. > > This has nothing to do with the language itself. Scala is a very excellent > language, but in the current situation, we need to lower the threshold of > contributors. Just as we have done a good job in user use, users can easily > control our products. > > Similarly, if we use Java in a unified way, we have taken an important > step in lowering the threshold for developers. > > Of course, I would also like to hear your ideas. Thank you~! > > Best, > Yuepeng Pan > > At 2023-03-12 14:44:47, "Lucifer Tyrant" <[email protected]> wrote: > >Hi developers, > > > >With the release of StreamPark's inaugural Apache version, our platform is > >becoming increasingly familiar to the public eye and an ever-growing > number > >of developers are also joining the StreamPark community. > > > >In order to promote the overall development of the project and reduce the > >barrier to contribution, It is necessary for us to standardize the > >programming language used in the entire project. > > > >In my opinion, standardizing the programming language would bring the > >following benefits: > > > >1. Uniformity in code style and interface. > >2. Enhanced cohesion among project modules, eliminating any sense of > >disconnection. > >3. Attracting more contributors to join the project. > >4. Better compatibility with Flink. > > > >What do you think about this? If your guys has some advice, please let me > >know and reply this email. > > > >Best wishes! > >Chao Tian >
