React vs. Backbone in 2025
https://backbonenotbad.hyperclay.com/
Ah, the perennial "React #vs. Backbone" #debate 😴, now dragged into 2025 so we can all marvel at how two sets of code that look eerily similar somehow symbolize "15 years of progress". 🤔🎉 It's like watching a snail race but with more abstraction and less excitement—who knew frameworks could be this thrilling? 🙄
https://backbonenotbad.hyperclay.com/ #React #Backbone #Framework #evolution #Coding #humor #Tech #trends #HackerNews #ngated
React vs. Backbone in 2025
https://backbonenotbad.hyperclay.com/
#HackerNews #React #Backbone #2025 #WebDevelopment #FrontendFrameworks #TechTrends
React and Remix Choose Different Futures
https://programming.dev/post/39641180
React and Remix Choose Different Futures, by (not on Mastodon or Bluesky):
https://laconicwit.com/react-and-remix-choose-different-futures/
#react #remix #simplicity #complexity #comparisons
habs rausgefunden #react
so doof bin ich also doch nicht :P
Figma Makeを使ってアプリ開発する
https://qiita.com/Static_Novice/items/594f5ab90191cbb7e3ac?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#qiita #React #Figma #FigmaMake
grlmu wie geht das bei #react nochmal.... grübelz
habe ich doch tatsächlich was vergessen und nie aufgeschrieben.... grlmz scheiss build
#react #reaction #viraliza #fyp #foryou
"the model doesn’t understand that the best way to build these things is to create an external service and integrate that using hooks with #React, instead of trying to cram all the business logic into React, which is what everybody in the world does" https://thenewstack.io/why-ai-is-generating-lowest-common-denominator-react-code/#:~:text=model%20doesn%E2%80%99t%20understand%20that%20the%20best%20way%20to%20build%20these%20things%20is%20to%20create%20an%20external%20service%20and%20integrate%20that%20using%20hooks%20with%20React%2C%20instead%20of%20trying%20to%20cram%20all%20the%20business%20logic%20into%20React%2C%20which%20is%20what%20everybody%20in%20the%20world%20does
#React folks, question:
I'm starting to dislike very much the fact that whenever one state var changes via its setter, the whole component is re-rendered. This is very annoying, as in other frameworks (namely Svelte), only the DOM that's related to this var is updated. Which is very convenient, much and more performant.
Is there any kind of tips you have to make sure only this portion of the component that's related to said state will reload?