The Failed Promise of Web Components

Re:The Failed Promise of Web Components by ricksharp on Wednesday September 30, 2020 @11:39PM (#24647103)

MVC - because spending 50% Of your time looking for the other file with the almost identical name is fun... wait now we need the view... nope back to the controller again... why can’t these files be next to each other...

It’s ironic that this is done in the name of “Separation of concerns“ -

You know what separates concerns: having everything that affects this component - in one place. That’s true separation of concerns.

I’ve worked in multiple frameworks in multiple languages and nothing does it better than modern react (especially with webhooks).

[ Parent | on HN ]

Re:The Failed Promise of Web Components by vitalyx on Thursday October 01, 2020 @07:01PM (#24657065)

Could you give a few examples of those languages and frameworks just to understand what you are comparing React to?

[ Parent | on HN ]

Re:The Failed Promise of Web Components by ricksharp on Thursday October 01, 2020 @10:57PM (#24658324)

Here’s a decent list through time for JavaScript frameworks: http://todomvc.com/

For my own experience with things that were specifically MVC or MVVM:

In C#: Asp.net MVC, WPF (with/without Prism)

In Typescript: Knockout, Angular 2.0+ (I guess it wasn’t mvc really - I disliked it for other reasons)

React (with hooks) on the other hand is the embodiment of a pure Functional Programming UI.

I can literally write a component with a single import and a single function.

For every reason functional patterns beats OOP patterns, react beats mvc - and achieves true separation of concerns (feature aligned concerns).

[ Parent | on HN ]

Re:The Failed Promise of Web Components by vitalyx on Sunday October 04, 2020 @11:06PM (#24684196)

Thanks, that helps.

[ Parent | on HN ]