I have to agree with you. The shiny stuff syndrome is spreading like cancer in the front-end world.
The only way to set this right is: when you create something, don’t sell it as a one size fit for all solution. State the tradeoffs as loud and clear as possible. Guide the users on what point you necessarily need the library and point them to simpler alternatives when needed.
This is something I deeply respect about Dan Abramov. He did this with Redux. Now that he’s in React, I see a lot of this culture in React docs as well these days.
Bottomline: The responsibility is on the creators to stop spreading this shiny stuff syndrome.
I will say that as a current Redux maintainer, I _hate_ that I seem to have to spend more time cautioning people about when it's appropriate to use Redux, than I do actually promoting its use. :( I can't think of any other lib off the top of my head where the maintainers have had to do that.
That said, yeah, we've got a Redux FAQ entry that discusses when you should use Redux [0], and some other "caveat"-type sections scattered throughout the docs.
We're currently planning a revamp of the Redux docs structure and content [1], and we'll see if we can improve some of the messaging as part of that. Would appreciate any suggestions you can offer.
When you program even a little bit, you already think like a computer. C is more about thinking a lot closer to the hardware, to the very low-level components of the computer. That's really an amazing universe.
Different generation. Couldn't afford a computer until 2008. Got a celeron clocked at 1.2 Ghz with a 128mb physical memory and 20Gb HDD running a win98. This was when everybody in the neighbourhood was playing Assasin's Creed in their core2duo.
If only my machine ran all those amazing games, I wouldn't have been a coder now ;-)
Anything - simple or complex, can be explained. If you are not able to explain something to a child, then you probably don't know about it well enough.
One of the most depressing moments was when I got a high-paid and very desirable job at Dell. I was even upfront about my history with my interviewer (I've never hidden or lied about it before) who assured me that it wasn't an issue.
I was working for 3 days and was nice and comfortable in my office and made lots of friends when security arrived and escorted me to my car and told me I wasn't allowed back on Dell property because I failed my background check.
I went through enough depression at the time that I gave up on the tech sector for a few years and worked food industry.
The only way to set this right is: when you create something, don’t sell it as a one size fit for all solution. State the tradeoffs as loud and clear as possible. Guide the users on what point you necessarily need the library and point them to simpler alternatives when needed.
This is something I deeply respect about Dan Abramov. He did this with Redux. Now that he’s in React, I see a lot of this culture in React docs as well these days.
Bottomline: The responsibility is on the creators to stop spreading this shiny stuff syndrome.