Minimalism in development is a forgotten virtue of our time that should gain more attention. A straightforward summary of some minimalism principles is available here. Briefly, the principles of minimalism in Software Engineering can be summarized as follows, based on the manifesto for minimalism.
I'm writing this post to react to one of the many articles and threads about the presumed death of this or that programming language, library, framework, or tool. What that article was about and who wrote it is secondary. I could synthesize my idea by citing a well-known joke by Mark Twain: "The rumors about my death are greatly exaggerated."
The planned obsolescence of computers and other IT electronic equipment is a well-known plague of our age. For years, I stopped buying new computers and prefer refurbished ones whenever possible. That includes all my personal ICT boxes, and even at work, I try to spin out the life cycle of the equipment in use under my direct management. Proprietary OSes often limit the lifespan of IT equipment, but in some cases, vendor-independent FOSS software can replace the original one at End of Life (EOL). This is beneficial because FOSS software is often more lightweight, customizable, and has a longer support life, thereby extending the usability of your equipment.