The principles equally apply to both static and dynamic type languages, OO and functional paradigms etc... TS is irrelevant for this part. In this case, the ports and adapters pattern (wepayService) replaces static types' interface implementation. Couple that with a proper unit test that's super easy to implement since you can do black box testing now, and you've got the enforcement of the interface as a side effect of a passing test.
It's not the interface that knows about the wepayAdapter but an adapter (that encapsulates usage of wepayAdapter) that knows about the interface. Look for "Ports and Adapters" pattern for better perspective
is it possible to decouple a webapp from libraries/frameworks like react/angular/vue? If so, can anyone please provide me with an example? github links appretiated
No, it is not possible to decouple the whole application from react. But you can decouple the core logic form it. If you application logic is mostly presentational then there is no much you can abstract from the library
@@deeplypresent He is not asking to build a web app without a library/framework. He is asking to decouple an app from libraries/frameworks such as react, angular, and vue, so the app can switch UI libraries easily or as much painless as possible.
You cannot have an entire application decouple from your library/framework. However, what you can do is have your core business logic in a separate folder/library/whatever and have your react, vue, or angular project import your business logic. Your business logic should know nothing about react, angular, vue, etc.. It should be pure javascript, and framework agnostic.
Excellent presentation. I hope the tough (disinterested) crowd didn't discourage him.
Love that picture : The Front End is the new Back End ! Thank you bro for this great conference :)
Excellent explanation !! The speaker is good !!
very good resume of the clean architecture book first part
Thanks, I will use this principle for our frontend.
Really appreciated the talk! Looking forward to apply these principles in the everyday work :)
Very good explanation of proper doing in FE things!
Gonna log to my second account to give this a second like. Thanks a lot 😊
Good job dude enjoyed your talk!
The talk is awesome :)
I got a little nervy when there was no .ts or .tsx extension.
The principles equally apply to both static and dynamic type languages, OO and functional paradigms etc... TS is irrelevant for this part. In this case, the ports and adapters pattern (wepayService) replaces static types' interface implementation. Couple that with a proper unit test that's super easy to implement since you can do black box testing now, and you've got the enforcement of the interface as a side effect of a passing test.
Thx for impressive speech!
dont understand why the interface knows about the wepayAdapter if it is meant to be agnostic
It's not the interface that knows about the wepayAdapter but an adapter (that encapsulates usage of wepayAdapter) that knows about the interface. Look for "Ports and Adapters" pattern for better perspective
great talk
is it possible to decouple a webapp from libraries/frameworks like react/angular/vue? If so, can anyone please provide me with an example? github links appretiated
Absolutely, you can build web apps without a framework. Check out Web Components!
No, it is not possible to decouple the whole application from react. But you can decouple the core logic form it. If you application logic is mostly presentational then there is no much you can abstract from the library
@@deeplypresent He is not asking to build a web app without a library/framework. He is asking to decouple an app from libraries/frameworks such as react, angular, and vue, so the app can switch UI libraries easily or as much painless as possible.
You cannot have an entire application decouple from your library/framework. However, what you can do is have your core business logic in a separate folder/library/whatever and have your react, vue, or angular project import your business logic. Your business logic should know nothing about react, angular, vue, etc.. It should be pure javascript, and framework agnostic.
It's called a micro frontend. In this you can have components in multiple frameworks in the same web app
The brad pitt of programming 8-)
tacos!
Frontend Elon Musk