Which front end technology will ESRI follow?

[baohuachu7]

Now there are :

•      Web app builder(WAB) based on Jimu js library which is private;
•     Calcite maps, extension of bootstrap, created by one ESRI front end guy. It's UI is better than WAB; 
•      CLI for vue,react etc;

For the js developers of us, would like to know in the end which one ESRI will prefer? 

The last two, only basci framwork available, not any shared widgets avialable such as print, legend, scalebar and so on.

Just as at the beginning , the web API have silverlight, flex and javascript, in the end the silverlight and flex are not supported.

[ReneRubalcava · Accepted solution]

There really isn't a preference on the ArcGIS JSAPI front. The widgets in the API are based off a vdom implementation. 

We have a guide page on using various frameworks. Those are just a few of the more popular frameworks, but we've seen implementations with Svelte, Riot, some enterprise stuff. We also have a cli that can output a few different options.

Teams in Esri use various frameworks as well. We use Ember, React, Angular, even Elm.

My point is, there really isn't a preference. That decision is up to you and your teams. Our goal is to try to make that integration easier for you, and we are looking to improve on that upcoming releases.

[baohuachu7]

These days I played around Calcite maps.  In the end found editor widget can't be used(as the screenshot below) because of the conflicts of css styles.

It will be challege for ordinary developers to create this widget from scratch. It is better to provide some basic widgets in the popular frameworks.