Conversation

Notices

1. ZachSCARY Leatherman :11ty: (zachleat@fediverse.zachleat.com)'s status on Monday, 06-Feb-2023 07:44:00 JST ZachSCARY Leatherman :11ty:

   If we moved on from React with even half of the enthusiasm level we used to move from CommonJS to ESM, the web (and the folks using the things we build) would be better off for it.

   • xangoh (xangoh@kolektiva.social)'s status on Monday, 06-Feb-2023 07:43:51 JST xangoh

     in reply to

     • Luci for Chai Tea
     • Scott Feeney

     @zens @graue @zachleat React is like, I tell you I want to make myself a burger but don't have any ground beef, and you lead a cow into the kitchen, and tell me that all I have to do is learn cow anatomy and how to butcher a cow and safe meat handling techniques and before long I'll have the best and freshest burger I've ever tasted

     I don't want a framework that scales to complexity by making everything complex, that seems like an antipattern to me

   • Luci for Chai Tea (zens@merveilles.town)'s status on Monday, 06-Feb-2023 07:43:52 JST Luci for Chai Tea

     in reply to

     • Scott Feeney

     @graue @zachleat for 99% of what react.js gets used for, plain static html and css would be vastly better. and ESM pretty much obviates the need for the build tools we were using to use common js modules

     Adrian Cochrane repeated this.
   • Luci for Chai Tea (zens@merveilles.town)'s status on Monday, 06-Feb-2023 07:43:54 JST Luci for Chai Tea

     in reply to

     • Scott Feeney

     @graue @zachleat because React.js is already worse than what it replaced. by a lot. for both users and developers

   • Scott Feeney (graue@social.coop)'s status on Monday, 06-Feb-2023 07:43:58 JST Scott Feeney

     in reply to

     @zachleat Okay I'll bite: move on to what? And what makes you confident it's better (beyond specific use-cases/personal preferences)?