Using a framework will harm the maintenance of your software
Every time I see anti framework posts I am forced to frusteratedly chime in. This mentality makes me fume... not all of us work on massive teams where building stuff without a framework is even an option.<p>And even then, whats really a &quot;framework&quot;? You could argue it&#x27;s even the language itself. Android apps used to be written in Java, and now they are pushing Kotlin way harder (and it may even be the default soon). Everyone who wrote those JavaScript apps back in the 1990s without TypeScript, are they still just as maintainable as their TypeScript counterparts? Such a shortsided and ignorant view IMO.<p>I think what bugs me the most is any sort of purist mentality (about anything) in software engineering. WE ARE ENGINEEERS. ENGINEERS USE THE RIGHT TOOL FOR THE RIGHT JOB! It should NEVER be &quot;always use X&quot;, &quot;never use Y&quot;. Both X and Y exist for a reason, so they are both useful for some reason.<p>And again, because I&#x27;m an engineer, I&#x27;ve also built my fair share of apps in just &quot;purist&quot; languages, the classic HTML &#x2F; CSS &#x2F; JavaScript, so I&#x27;m not against the purist approach either. Again, right tool for the right job.