Hypothesis: Did the choice of React/JSX raise the barrier for DNN Community contributions?

[thienvc]

Hello community,
I’ve been reflecting on the frontend technology stack of DNN (specifically the PersonaBar) and wanted to open a discussion.
I am not a frontend expert, but as a long-time DNN developer transitioning from WebForms, I find Vue.js significantly more approachable than React.
Mindset Match: Most of us are .NET developers. We are used to separating logic (C#) from presentation (HTML/Razor). Vue respects this separation. React (JSX) forces a "JS-heavy" mindset that can be jarring.
The Knockout Connection: Since DNN has a history with Knockout.js, the transition to Vue seems almost seamless. The concepts map 1:1. Moving to React, however, requires unlearning old habits and learning a completely new philosophy (Immutable state, JSX, etc.).
I can’t help but wonder: If DNN used Vue instead of React, would the "average" DNN developer find it easier to contribute to the core?
Right now, looking at the PersonaBar source code with its complex React/Webpack setup feels daunting. If it were Vue, I genuinely believe more community members (myself included) would be confident enough to submit PRs.
Is React strictly necessary for our needs, or would a more "pragmatic" framework like Vue serve our specific community demographic better?

[mitchelsellers]

This one is a bit of an interesting discussion, and I think some of the history etc is important to understand.

First of all, the decision to use React was not a community decision; it was a DNN Corporation decision that contributed to the community platform. I'm not saying it was right or wrong, but it was done by Corp, and we have the contribution to maintain.

Over the years since the community has been doing all of the support of DNN Platform we have been cleaning up, updating, and maintaniing the existing code. Working to improve stability, maintance ability etc.

The concept of re-writing something as massive and integral to DNN Platform as the PersonaBar with a different UI Framework, in my opinion, is something that is mounted with a number of concerns:

• Who would actually contribute the time & effort to accomplish this - Remembering that DNN is purely open source with no developers being paid to do onging maintenance
• What other items that are more critical would be skipped over from getting the maintenance or contributions they need if this effort was to be taken.
• What would the testing and release stability impact be of a re-write of the PersonaBar to the future development and adoption of DNN Platform.

Along with this, it would then be prudent to ask

• How does the average user of DNN Platform benefit from this change?
• Does this open the door to more contributions? If so, by how many?
• Are there alternatives to get more contributions? Training or similar?

React isn't my personal preference at all, but I have a hard time without a substantial contribution from an external party even thinking of a route that we would be able to switch away at this point in time. Just my $0.02.

[donker]

In answer to the question: did it raise the bar for entry to contribute? I'd say that is a question that will be impossible to answer. I don't know how you'd measure this.

I know Vue developers, I know Angular developers and I know React developers within our community. I am part of the latter group. As a React developer I'd do 2 things differently: 1. use Typescript and 2. not use Flux. But like Mitch stated above: this ship has sailed. I can't see anyone taking on the job of reprogramming these parts as they are far from trivial projects.

[david-poindexter]

It would be GREAT if Typescript were used. I'd also say if there was a better alternative to Redux, that would be fantastic. It is quite complex and I have to think there are probably better ways to go about state management these days that perhaps wasn't an option back when Corp implemented this.