Hi there so today I wanted to talk about the merits of a framework I get

this question quite often like when do I decide to bring in a framework oreven just bringing in libraries versus just build it yourself. And so firston like the framework side of things if you're building something that'slike basically a HTML page or you're doing some surveyor server templatething and you just need to enhance your app a little bit with someJavaScript so therefore it's more of a website than an app.

Then yeah, you probably don't need a framework the browser differences are

pretty.Smooth to over by now and yeah you may not need a framework in thatcase, but like my audience of the the people that I'm working with mostlyare very primarily focused on building web applications and for that if youdon't want to build or use a framework and and they're legitimate reasonsto not want to use a framework, but if you don't what is going to happen isyou're going to build a framework for yourself.

Eventually, you'll build abstractions for everything. And the difference

between your framework and one of the more popular andTry to trueframeworks is your framework is used by only you and it is not battletested. It is also maybe not even tested. It hasn't gone through the rigorof being deployed to production by lots of other people and so there are alot of bugs that you just don't know about.

And so I would really strongly advise against building your own framework

unless you have just some very particular needs that none of the otherframeworks can satisfy. And I would suggest that 99.9% of applicationsthe,That you would build for the web there's a framework that is wellsuited for the task And in fact most frameworks can cover 90% of the needsof most web applications today.

I'm sure. So even deciding between which framework is less of an important

point at this point, they can all pretty much do what you want them to do.And so as far as like libraries when should it just bring in libraries? Imean, there's always the risk of you know, some security vulnerability.

There's there's this article a while ago about somebody who's been stealing

credit card credentials because they published something to.NPM which ofcourse that was not true they'd hadn't actually done that but they weresaying this is a thing that I could have done and it absolutely is and it'sterrifying but do you want to build a product or do you want to build abunch of libraries.

Because ultimately if you don't use libraries to do things you're going to

build your own and there's nothing wrong with that. You can like copy somecode and and put it into your vendor directory or something like that. Likethere's nothing wrong with that. You can totally do that.

But it is a trade-off and you just need to acknowledge that fact. So, I

can't give you a solid answer on that but hopefully that was at leastthought provoking for you. Have a nice day.