The end of Framework Churn

Re:The end of Framework Churn by aargh_aargh on Monday September 18, 2017 @12:38PM (#15277335)

The reason for the churn is not lack of a standard for components. It's that the ecosystem is both new and large, so many experiments are going on, some of which become popular until the next best thing comes along. This won't be solved by components. It will be solved slowly over time as innovation levels off.

[ Parent | on HN ]

Re:The end of Framework Churn by sydd on Monday September 18, 2017 @03:02PM (#15278549)

Its not new, JavaScript has been around almost as much as Java which has a mature ecosystem since 10+ years.

JS world has had this "We're almost there" attitude since the announcement of HTML 5 ten years ago.

[ Parent | on HN ]

Re:The end of Framework Churn by Sujan on Monday September 18, 2017 @01:45PM (#15277927)

To me custom components feel like one of the "innovations" that bring us more to a state where one part of the equation will be "solved" and there won't need to be any more experiments. It will just work. With all frameworks. And that is great.

[ Parent | on HN ]

Re:The end of Framework Churn by pjmlp on Monday September 18, 2017 @02:07PM (#15278094)

I look forward to see the Web finally catch up with 90's.

Maybe in a couple of years we get our Delphi and VB component designers and toolboxes for the Web.

[ Parent | on HN ]