←back to thread

367 points lemonberry | 1 comments | | HN request time: 0.208s | source
Show context
ChrisMarshallNY ◴[] No.24641703[source]
I love her description of using a dependency-laden component:

> Using a custom element from the directory often needs to be preceded by a ritual of npm flugelhorn, import clownshoes, build quux, all completely unapologetically because “here is my truckload of dependencies, yeah, what”. Many steps are even omitted, likely because they are “obvious”. Often, you wade through the maze only to find the component doesn’t work anymore, or is not fit for your purpose.

That is so true. The "unapologetically" thing is important. I see this all the time. There's often a fair bit of 'tude, where I am looked at with condescension, for not knowing something "obvious."

The fig tree pic is perfect.

EDIT: Removed phrase that was possibly corrosive to the narrative.

replies(7): >>24641798 #>>24641833 #>>24641876 #>>24642200 #>>24642654 #>>24644698 #>>24651062 #
1. dejavuagain ◴[] No.24641833[source]
I see this too and is very frustrating in modern Web learning.

It might take 8 files and 15 dependencies to make one example work. Only 3 files are partially provided. 5 dependencies are deprecated or no longer supported.

The informative websites aren't designed to help you learn, they are designed to help the helper: get views, get cred, get employed, get ad revenue, get an ego boost.