Github user shijinkui commented on the issue:

    https://github.com/apache/flink/pull/2459
  
    hi, @StephanEwen I have an idea in mind, If there are to much tricky bugs, 
and follow "don't change it unless it is broken", after two years can you image 
the code like? Full of tricky bugs fix.
    
    I think we should make the code robust, reasonable and readable.
    
    Can we make a long plan with many sub-tasks to reach the above purpose? 
    Such as reduce the unnecessary module, pom more simple and easy maintain 
the pom.xml
    
    Many people consider the Flink code confused and then give up Flink. I 
think Flink's features in whole are better, the detail of project need enhance.
    
    How do you think about that?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to