Plain Wrong?

" summary

Examines the trade-offs between using frontend frameworks (React, Vue, Angular) and writing plain JavaScript, focusing on the costs of framework-provided environments (extra bytes to transmit, decompress, parse, compile) and whether worthwhile apps can still be built with straight-up JavaScript. Discusses the problems introduced by framework dependencies and argues that much JavaScript work uses more tooling than necessary.

AI-written summary · about

" related talks

• 32mMiss the forest for the trees: How frontend developers fail to be engineersGeorgios Diamantopoulos · Heapcon 2024
• 18mA framework author's case against frameworksAdrian Holovaty · dotJS 2017
• 49mFront Ends for Back End DevelopersMatt Raible · Spring I/O 2017
• 01h 00mArchitecture of Modern JS Applications: Three Frameworks, Three ApproachesNikita Isaev · HolyJS 2017 Piter
• 22mA brief introduction to JavaScript and ArchitectureTorsten Helmich · RuhrJS 2016
• 50mI Don’t Care About Your JavaScript FrameworkNéstor Salceda, Dani Latorre · Software Craftsmanship Barcelona 2017
• 01h 02mChoosing a JavaScript FrameworkRob Eisenberg · NDC Oslo 2016
• 39mReinventing the Wheel for Every New JS Framework, Is It Worth It?Fernanda Bernardo · QCon São Paulo 2018