[ 
https://issues.apache.org/jira/browse/FLINK-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667056#comment-16667056
 ] 

Till Rohrmann commented on FLINK-10706:
---------------------------------------

Thanks for raising this point [~Zentol]. I think this discussion surfaced a bit 
in the overall discussion thread which you can find 
[here|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Flink-Cluster-Overview-Dashboard-Improvement-Proposal-td24531.html].
 I agree that changing the technology stack can be a challenging task and we 
should make a deliberate decision here. Thus, let's discuss it explicitly on 
the ML.

In general, my observation is that we don't have many people in the community 
who are super familiar with Angular. Given that Angular 1 is quite old I think 
we should at least consider switching to React. As a side effect, we might be 
able to attract more people helping with a React based web UI in the long run. 
But this is something we can maybe judge from the ML interactions with the 
discussion thread.

 

> Rewrite Flink Dashboard with React
> ----------------------------------
>
>                 Key: FLINK-10706
>                 URL: https://issues.apache.org/jira/browse/FLINK-10706
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Webfrontend
>    Affects Versions: 1.6.2
>            Reporter: Fabian Wollert
>            Assignee: Fabian Wollert
>            Priority: Major
>             Fix For: 1.8.0
>
>
> The Flink Dashboard uses currently Angular 1, which had its successor coming 
> out two years ago. Its expected that Angular 1 (or Angular.js how it is 
> called now) will ceise to exist in the future, due to its successor Angular 
> 2-7 and React being the more actively developed platforms.
> Due to my personal experience with React i will attempt to rewrite the 
> Dashboard in React. Additionally i will upgrade all used libs, which mostly 
> affects Bootstrap 4, hence the look will be slightly different.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to