“So no, it’s not the dependency iceberg itself that is worrying me.
It’s the proliferation of configuration options.”
— Dan Abramov
When I started professional development in the early-90’s I only had a few software development languages and tools at my disposal. C++ was just gaining steam and available to me on my PC in MS/DOS via Borland Turbo C++ (which I bought at a student discount.) NCSU provided very nice Sun SPARCstations in their computer labs. I spent many-a-late-night in the labs, but for personal use no student could afford buying a SPARCstation. Microsoft Visual Studio was evolving in Windows and sometimes unstable. Linux was spanking new. Java was also new (and controlled by Sun), but didn’t start rolling hard until about 1995. The primary source of learning new development-related skills was via books (not yet the Internet). The pace of change was slow and controlled by companies who built the compilers, just as as Abramov indicates. When Microsoft rolled out .NET and Windows XP circa 2000 it took about 3 years for .NET to gain full uptake in the Windows ecosystem. Even I shied away from it until .NET hit 2.0. .NET’s growth required a huge advertising and educational push from Microsoft to encourage developers to adopt it and yet they still had to keep around older API’s like Microsoft Foundation Classes, COM, ATL, and WTL because of the massive quantity of legacy code and developer lock-in.
Does this globulous menagerie make you feel anxious?
Good Practice Make Good Play
Nowadays Was Yesterday
My most recent efforts have been using React dev environment with Inferno (because React’s patent clause freaked many folks out and causes confusion). But, wait, Facebook is dropping the patent clause for React. Maybe we can move to full React. Time to change…