projects are synonymous with changes, codes change for N reasons, scopes change, frameworks change, techniques change.
DI exists to facilitate all these changes with little work. If you still don't have this vision, I recommend studying more before giving your opinion publicly about one of the important patterns that exist for efficient projects.
about clicking and going to the definition, every substitution made by DI, a base class and a concrete one are required, you just go to the base class using your "go to definition" technique and then use the "go to reference" technique and there will be who is looking.
what the hell is this here? are you throwing shit at the fan?
I made a point of creating an account just so I could reply to you.
is talking bad about a back-end framework with an enviable architecture, which reuses many open community projects, unifying everything to be used following an existing pattern.
Exactly how Doug McIlroy encourages... : )
NestJS does apply Design Patterns to reduce the amount of cognitive load required if we were to use the same resources (libraries) in a separate way that we can use with it...
Each library follows a different way of configuring and adding to our project. Nest simplifies all of this, and of course allows you to replace one feature with another.
If that's possible, thank the DEPENDENCY INJECTION pattern!!!
Now the last and worst confusion of all, you were talking bad about NestJS and suddenly started showing CSS code and Front-end components?
Seriously you had the ability to confuse Nest JS, the excellent Back-end framework and that's all. JUST IT. With Ne*x**tJS, horrible Framework that made us go back in time mixing Back-end with Front-end with SQL with HTML with CSS?
Whoops, you really don't know what you're writing, assume it was an A.I. which is less bad for you...
Ah, I almost forgot... about Postman, I agree with the A.I.
React has always been a library, and it's always been shit, since the beginning hahahah
one more thing, here is a suggestion to improve your ugly code
```tsfunction createElement<K extends keyof HTMLElementTagNameMap>(
tag: K, props: Partial<HTMLElementTagNameMap[K]>, ...children: Element[]
) {
const el = Object.assign(document.createElement(tag), props);
el.append(...children.map((child) => typeof child === "string" ? new Text(child) : child));
return el;
}
```
learn HTML, JavaScript and TypeScript before complaining about what's on top
projects are synonymous with changes, codes change for N reasons, scopes change, frameworks change, techniques change.
DI exists to facilitate all these changes with little work. If you still don't have this vision, I recommend studying more before giving your opinion publicly about one of the important patterns that exist for efficient projects.
about clicking and going to the definition, every substitution made by DI, a base class and a concrete one are required, you just go to the base class using your "go to definition" technique and then use the "go to reference" technique and there will be who is looking.
what the hell is this here? are you throwing shit at the fan?
I made a point of creating an account just so I could reply to you.
is talking bad about a back-end framework with an enviable architecture, which reuses many open community projects, unifying everything to be used following an existing pattern.
Exactly how Doug McIlroy encourages... : )
NestJS does apply Design Patterns to reduce the amount of cognitive load required if we were to use the same resources (libraries) in a separate way that we can use with it...
Each library follows a different way of configuring and adding to our project. Nest simplifies all of this, and of course allows you to replace one feature with another.
If that's possible, thank the DEPENDENCY INJECTION pattern!!!
Now the last and worst confusion of all, you were talking bad about NestJS and suddenly started showing CSS code and Front-end components?
Seriously you had the ability to confuse Nest JS, the excellent Back-end framework and that's all. JUST IT. With Ne*x**tJS, horrible Framework that made us go back in time mixing Back-end with Front-end with SQL with HTML with CSS?
Whoops, you really don't know what you're writing, assume it was an A.I. which is less bad for you...
Ah, I almost forgot... about Postman, I agree with the A.I.