I think the author confuses frameworks as commonly understood, and the more general idea of an abstraction. The example of keeping the power to the server on describes a problem getting abstracted away, or taken over by someone else to become part of the background. That doesn't really compare to a developer raised on Bootstrap or React who doesn't know CSS, HTML, HTTP, Javasript, etc.
A person may choose to keep training wheels on their bicycle forever, or have their mom chauffer them around because they never learn to drive a car. Pointing out that staying with those easy "frameworks" means foregoing mastering the underlying (and more valuable) skills -- and possibly burdening other people with your shortcomings -- doesn't equate to "toxic" or "gatekeeping" behavior, it just states a fact.
Right now tens of thousands of junior developers who never advanced beyond using a framework by copy/paste can't find jobs. A limited and shallow set of skills exacerbates the other problems in the job market. Frameworks can help by abstracting and backgrounding unnecessary details, but they can also turn into permanent training wheels that obscure the useful and valuable skills a serious developer eventually has to master.
Calling someone's opinion "toxic" and "gatekeeping" attempts to shift responsibility for one's emotional reactions and feelings to another person: What you wrote triggered me. An adult takes responsibility for their feelings and reactions and doesn't get "triggered" or interpret the opinions of strangers as personal attacks or judgments.
> Calling someone's opinion "toxic" and "gatekeeping" attempts to shift responsibility for one's emotional reactions and feelings to another person: What you wrote triggered me. An adult takes responsibility for their feelings and reactions and doesn't get "triggered" or interpret the opinions of strangers as personal attacks or judgments.
The delightful irony here is that the reason you wrote this paragraph is because of the emotional reaction you had to the choice of words!
A person may choose to keep training wheels on their bicycle forever, or have their mom chauffer them around because they never learn to drive a car. Pointing out that staying with those easy "frameworks" means foregoing mastering the underlying (and more valuable) skills -- and possibly burdening other people with your shortcomings -- doesn't equate to "toxic" or "gatekeeping" behavior, it just states a fact.
Right now tens of thousands of junior developers who never advanced beyond using a framework by copy/paste can't find jobs. A limited and shallow set of skills exacerbates the other problems in the job market. Frameworks can help by abstracting and backgrounding unnecessary details, but they can also turn into permanent training wheels that obscure the useful and valuable skills a serious developer eventually has to master.
Calling someone's opinion "toxic" and "gatekeeping" attempts to shift responsibility for one's emotional reactions and feelings to another person: What you wrote triggered me. An adult takes responsibility for their feelings and reactions and doesn't get "triggered" or interpret the opinions of strangers as personal attacks or judgments.