MudBlazor VS react-nodegui

Our website is updated as well: MudBlazor - Blazor Component Library

Though I can't develop beautiful UI and good UX even if my life depended on it. I can write a functional front-end, but don't expect it to be pretty. I usually ask for assistance regarding that from our UX designers instead where they essentially layout the whole UI (either on figma or Photoshop) so I just need to make it functional. Component based frameworks these days (JS, and Blazor) really helps at least. The UX guys usually make sharable base components that the company needs (buttons, grids, etc...), which includes all the styling and animations and we use those instead to create decent looking UI. For personal stuff I use MudBlazor which kinda does the same, but I do know a bit of css to customize when needed.

There are a ton of component libraries out there. I like the mudblazor library. https://mudblazor.com

There are grid controls from the usual commercial vendors like Radzen and Telerik. I used them briefly during a free trial. It has a funny name, but MudBlazor [1] has been the MIT licensed library I have been using lately. I have been using their Table control, which may be what you are looking for in a data grid. [2] Check it out and see.

[1] https://mudblazor.com/

[2] https://mudblazor.com/components/table#api

It seems to be a known issue a known issue. By default, external libraries such as MudBlazor are not trimmed

I recommend Mud blazor if you're going for Material design. For other design languages Andt Blazor's pretty polished and there's Blazorise as well if you want to be flexible (it supports Antd, Bulma, Bootstrap and Material via configuration).

The ones I've used that's pretty good are MudBlazor (Material Design), Antd blazor (Antd), and Blazorise (Multi design support via configuration). There's also the newly announced Fluent UI for Blazor at MS build that's from MS themselves but I haven't tried it yet.

There's Uno that's been talked about by MS community standups if you wanna use UWP XAML to do the Job. If you wanted to use Blazor though, you'll have to at least learn a bit of CSS and Html. Luckily you can find really nice component libraries like mudblazor that does a lot of the nitty gritty html + styling for you. So you'll just have to use their components most of the time and with little to no JS required (depending in your usecase).

In fact, there's a version with a React wrapper, pretty much similar to React Native

If you are strictly looking to make a desktop app, I would suggest looking at https://react.nodegui.org/ it is really easy to use and develop.

I have to use Discord and Element on a regular basis (which both use Electron). They both use an unreasonable amount of RAM, and I feel this even more as my laptop is quite old and has 4GB of RAM.

I keep looking for alternatives to Electron, which wouldn't require such heavy resources to run, but my searches always seem to come up short. There are a number of solutions that are either dead or are not ready for production yet, such as React NodeGUI[0], Proton Native[1] or react-native-desktop-qt[2].

There's react-native-windows, but I'm not running Windows, and even if that did gain Linux compatibility it seems that they're quite focused on Microsoft-owned platforms.

Is "just stick Chromium into all your apps" seriously the best we can do as an industry? It's resource-inefficient to high heaven, not to mention that it's slow and doesn't integrate with the native platform styles at all. As a JavaScript developer, I'm quite surprised this is the best there is for cross-platform JavaScript development.

[0]: https://github.com/nodegui/react-nodegui

React NodeGUI is slowly gaining popularity for bringing react directly to the desktop development experience, powered by Qt5.

Also, for React desktop apps, have a look on React NodeGUI, you will notice Qt 😉

On the React and Vue github repos the README contains this disclaimer:

I was going to name this piece by piece or the building blocks of, but I want that sweet, sweet SEO. In my last post I kind of brushed on NodeGUI and one of the negatives I listed was it was a bit light on examples so I since decided to remedy that by contributing to the project here and here thus far. I also got involved with the Vue version of NodeGUI, it’s not as polished or production ready as the react one yet but I hope to help with that.