Hacker News Reader

Comment by austin-cheney | Hacker News Reader

In my experience the large frameworks tend to make things easier for developers by bundling things into partially isolated components. They also tend to make the code much larger and more complex. For me working with the DOM is just a matter of assigning references to variables and making use of events (functions).

View on HN

this comment is a non-programmers idea of a programmer's comment.

> For me working with the DOM is just a matter of assigning references to variables and making use of events (functions).

I loved this tech-coded business speak gibberish. "For me, managing business operations is just a matter of aligning strategic variables with organizational synergies and making use of scalable frameworks (processes)."

It's ok to say you can't do it. I wouldn't think less of you for your honesty.

Can you write your own standard library, browser and operating system?

Let me put it this way: Chrome, the Linux Kernel and Ubuntu combined are about 600-700 million lines of code. React core has 70k (150kb). You‘re using 0.0017% less library and framework code than the rest of us.

There are also implementation differences due to using the framework, so the actual difference is really quite a bit larger than 70k LOC depending upon the given application. There are also all the plugins, build tools, and all their dependencies as well.

My personal preference is to ship less code because it means less to maintain over time, less tech debt.

> There are also implementation differences due to using the framework, so the actual difference is really quite a bit larger than 70k LOC depending upon the given application

Not really.

Why would I do something manually that a computer can automate, that's literally the entire point of programming.

Reply on news.ycombinator.com