mvc VS React

I don't mind how the view part of react works, but I don't like how it gets so complicated managing state. With a lot of state libraries for it now just providing lots of hooks you end up with so much in the view. Like you'll have more than half the comment be hook code managing state. While I prefer functional view components, there was something said for the encapsulation class components gave you.

We've got our own state framework for react that adds controller classes: it makes it easier to write imperative code, but with ours for the business logic rather than the view. It works a lot like mobx but class based. https://github.com/aha-app/mvc unfortunately we haven't put as much love into the oss library as we should have. We use it extensively in our apps.

I find it makes writing react code much more like writing classical UI desktop UI code, with wired up controllers and models.

> React was originally designed to be the V in MVC.

So much this. As we built more sophisticated apps using React we were constantly frustrated with how much code was ending up in the views, and how difficult controller frameworks were to work with (looking at you Redux). So we built our own mini-framework that explicitly separates the view from the controller. Seems like a simply change but it is amazing how much more productive it makes developers, especially with large complex applications that need refactoring as they evolve.

Unfortunately our skills are in writing code, not marketing, so we don't have a fancy website like most frameworks. But the details are here: https://github.com/aha-app/mvc

React Documentation

支持 React、ReactNative 和 TypeScript。

Supports React, ReactNative, and TypeScript.

React Community Discussions on GitHub

* Read the [React documentation](https://react.dev). * Check out [Intermediate React, v5](https://frontendmasters.com/courses/intermediate-react-v5/). * Grab my free e-book with **101 React Tips & Tricks** [here](https://www.frontendjoy.com/p/download-my-free-101-react-tips-tricks-book). * (Bonus): I highly recommend the [Advanced React](https://www.advanced-react.com/) book.

Choosing the right UI library can significantly impact your React.JS or Next.JS project's development speed, maintainability, and overall aesthetic.

When the user hovers over the “About Us” link, the component will start preloading the data for the /about page, ensuring an almost instant transition. Genius idea, isn’t it? Inspired by the react.dev documentation.

🔗 Tools We’ll Use: ReactJS: https://react.dev/ TailwindCSS: https://tailwindcss.com/ Appwrite: https://appwrite.io/ Gemini: https://ai.google.dev/ Framer motion: https://motion.dev/

Navigation: Built using React, this microfrontend is responsible for rendering the main navigation bar across the application.