Pull to refresh

Comments 8

Your insightful critique of technology's growing complexity echoes my own thoughts on the matter.

I mean, you seem to be well versed in React. You know that what started as a web framework ebded up a machine that no one can use due to its complexity.

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

function 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

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.

Too bad for you, I have a screen cap of writing this. AI age make you think of such accusations.

Nest in the frontend, Next in the backend. One project. Damn too many frameworks. It turned out to be a mess in the backend and in the frontend likewise.

DI turns code into an unreadable mess, where you don't know what follows what.

Check this one out:




  1. A finite set of unambiguous instructions that, given some set of initial conditions, can be performed in a prescribed sequence to achieve a certain goal and that has a recognizable set of end conditions.

You see, this is a definition of an algorithm. Unambiguous instructions. DI is nothing less than abiguity in extreme. Suddenly somehting happens somewhere in the different part of your code, and uless you have written the project yourself, you would never know how that thing happened. I beg you.

Open the main folder. Find main.go, click "go to definition" be happy, seeing the code it is running. This is something that I can call a readable program. Otherwise it turns into a mess of tangled instructions where not a single person can figure out what have happened. Whoops, your favorite framework just pushed out a new version (like the third time this year)? Well, too bad for you, pal. You have to sit there and upgrade your codebase, to match their ambiguous rules. Done that? Whait! Here is a new version, match that now.

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.

I agreed right up until you tried replacing React, and then killing Typescript, and I knew for certain you were an idiot when you said Nest ran on React. Good job.

For future readers: You don't need CRA to run React. Nest is a backend framework. Typescript is a godsend for large development teams building with Express/React. Everything else in this article (up to the Postman section) is largely accurate.

Ok, mistyped. And what is changed? See my comment above.

Only those users with full accounts are able to leave comments. Log in, please.