Re:Web Components could replace frontend frameworks?
by madeofpalk on Friday April 12, 2019 @08:48AM
(#19644288)
this is just replacing framework a with framework b. It's not a "native, declarative DOM templating API yet"
[ Parent
| on HN ]
Re:Web Components could replace frontend frameworks?
by augustl on Friday April 12, 2019 @03:49PM
(#19648369)
Well, yes and no. They are implementing a rendering engine that supports things the web famously doesn't support, which includes fundamentals like UITableView from iOS. They are doing this by leveraging new APIs to access what browser layout engines do under the hood. So in that way, it generates native browser elements, and their API is declarative. So it's at least one abstraction layer below React and friends.
Re:Web Components could replace frontend frameworks?
by madeofpalk on Saturday April 13, 2019 @07:04AM
(#19652253)
....no and no. The call was for a declarative interface to the DOM, like React, built into the browser. Flutter, being not built into the browser, is not that.
Re:Web Components could replace frontend frameworks?
by _bxg1 on Saturday April 13, 2019 @04:43PM
(#19655594)
There are a million things that do this already - including Qt, which already works in WebGL. The point is to leverage the rest of the web's existing features while also getting declarative templates, not to create another Flash.