Are these quotes the reason we end up with bloated rarely optimized or respectful for memory, CPU, or other resources software systems nowadays? https://www.te

Are these quotes the reason we end up with bloated rarely optimized or respectful for memory, CPU, or other resources software systems nowadays? https://www.techradar.com/news/move-over-chrome-macos-monterey-is-the-new-ram-eating-monster-in-town https://www.techradar.com/news/move-over-chrome-macos-monter... https://www.tomsguide.com/news/google-chrome-reportedly-destroys-mac-performance-heres-how-to-fix-it https://www.tomsguide.com/news/google-chrome-reportedly-dest... A great majority using these quotes act like no engineering design work is allowed whatsoever. I have seen that mentality permeate everything even hitting concurrency decisions for obvious things. (E.g. We need to respond to HTTP requests while doing stuff in the background, and accessing IO and run multiple server state syncing but let us have purely synchronous, single threaded code and we will figure it all out later. That went well.) And for some reason there is a subgroup that thinks security architecture is "optimizations." It depends on the product but when you have https://news.ycombinator.com/item?id=38029479 https://news.ycombinator.com/item?id=38029479 or https://news.ycombinator.com/item?id=38076636 https://news.ycombinator.com/item?id=38076636 it is not over-engineering: it is management and business forcing poor product.