Ask HN: Why do tutorial writers combine 10 technologies when 1 or 2 would do?

I can do way more(orders of magnitude more) with less resources in Lisp and C-python and very simple JS than most of those frameworks do. But it took me years of learning to be able to do that.

The alternative is just having frameworks that have everything that most people will need prefabricated. This way beginners could use them easily if they do not get out of the paved way.

When they want to get out of the paved way and do something else... well, there is another framework for that.

The fact is that from an economic point of view, if you market your courses for the general Public(in the millions) , those people(most of them, 90% or so) do not want to invest what it takes to become an expert in this particular area(or any other by the way).

Most of them just want a pill that fixes their problems as fast as possible, an instant gratification at the minimum possible cost(free). They want a job, they have heard this is the future, they want money to pay the rent.

Those people in the end spend way more time always following the new fashion, the new trend, the new bubble, instead of learning the fundamentals that never change.

If you market your courses for the General population at free prices, IMHO there is no other way. General population is not going to change, they consume porn(fast sex),fast food and fast education.

For me, it will be crazy if paid courses were like this. I spend my money on paid courses(some of them expensive) and certainly they are not like this.

For most techs the documentation or website for that tech explains the simplest use case. For graphql, from your example, the guide for graphql is really clean and thorough and doesn’t depend on you knowing anything else.

But it’s also completely useless when it comes to implemention for the average user, who probably doesn’t want to design a graphql server and frontend from scratch. Implementation is where the work is, and it can be very difficult to implement a working example in a real application (which often have more complicated things going on).

With graphql, you won’t be able to experiment with it without both a backend and a frontend. By necessity that means you need a server (express or tails or whatever) and you’re probably using React or something similar in the frontend.

JS in particular is also kind of a mess in terms of ecosystem. That’s a whole other can of worms.

This is being on the other end of the common internet career advice of "write blog posts to set yourself apart".