Can Blazorise make web app development very easy?

[iwis]

TLDR: Developing web apps is difficult for beginners [1][2], but maybe it could be easy with Blazorise? What I'm missing is a template with user management (sign up, log in, log out, reset password, etc.)

Details

The template should:

• use WebAssembly, because it is the better option for web apps deployed on the Internet (as opposed to intranet);
• have a backend integrated with the frontend - so that the app works immediately after creating a new project and running it;
• work with PostgreSQL (and not only with SQL Server, because SQL Server isn't open-source, which would greatly limit popularity; SQLite isn't proper for larger databases; and PostgreSQL is a highly regarded RDBMS for being the closest to the SQL standard);
• allow communication with the database using Dapper (and not only EF, because Dapper is easier to learn than EF).

A junior developer should only need to know C# and SQL (with DDL and DML) to create a simple web app. For simple projects, knowledge of HTML, CSS, and JavaScript shouldn't be required (I think it might already not be required). Hopefully, knowledge of ASP.NET Core, Blazor, or Blazorise also won't be required - if some functionality is needed, it could be learned through contextual help while coding, just like we didn't have to know everything to start writing desktop apps in Borland Delphi 20 years ago.

There should also be a very simple way to:

• deploy the app to a cheap server (other than Azure, since it's expensive) - deployment shouldn't be much harder or much more costly than in PHP;
• implement basic CRUD operations - both in terms of required knowledge and the amount of code needed.

The tutorial should explain in a simple way:

• how to perform the mentioned CRUD operations,
• how to read the ID of the logged-in user, what are the login/logout/reset-password links, etc.,
• how to deploy to a server.

In my opinion, the tutorial examples shouldn't use data models, data repositories, or tests - they are useful in large apps, but not essential in small apps or prototypes, and they introduce additional complexity, for example because of the object–relational impedance mismatch.

The template should implement things that are difficult to create from scratch (like user management), so the programmer doesn't have to do it manually, and the tutorial doesn't need to explain it. It's better if the most difficult parts are done by the experienced template creator, rather than expecting beginner programmers to redo them from scratch each time. They don't have enough knowledge to handle such complex tasks at the early stages of learning, they lack the experience to choose the right technologies 3), and it doesn't make sense to do it separately by each programmer for a simple application.

The tutorial shouldn't describe trivial things a programmer can figure out on their own, while the rest (e.g. CRUD examples) should be described as simply as possible - to make programming easy again for beginners, just like 20 years ago when building web apps in PHP or desktop apps in Borland Delphi.

Uncertainties:

• I'm not sure whether Blazorise WebAssembly (or generally Blazor WebAssembly) is fast enough for simple apps, despite the lack of fast garbage collection [4] and direct DOM handling in Blazor.

What do you think?

[1] https://www.reddit.com/r/webdev/comments/vsomxr/web_dev_has_gotten_notoriously_complex_and_i_dont/
[2] perhaps except PHP
[3] for example, they may not know whether there is a free and scalable option for user management, or if there isn't one and they have to choose Auth0, which becomes paid with a larger number of users, or perhaps another provider
[4] https://www.reddit.com/r/Blazor/comments/12brl35/will_implementing_garbage_collection_in/?sort=top

[Alexander-JM-0224]

There are plenty of solutions in the world where you do not have to battle a cloud provider to keep your product on the web, where even a toddler can build a website (not saying anything about the quality of said site), there is an overflow of information about building websites, not even talking about AI. Which makes your life even easier for the simplest website a person might build.

These things you are asking here are IMO way outside of the scope of what Blazorise does. And while reading your text i was wondering out loud.
Why should a FrontEnd library make deployment ready templates? Just in general, why should there templates be CRUD ready, with Dapper?

You said "A junior developer should only need to know C# and SQL" well, how are they going to work with Dapper then? Still a library you have to get a bit of knowledge about, a template is not enough.

To me it sound a lot like a boatload of scopecreep for parties like Blazorise and friends..
And with current AI technology the stuff you are asking for is peanuts to build yourself.
If there was a market for templates like these, we would have seen more of them in roulation/use around the WWW, but we dont. At least i dont.

So my opinion is that Blazorise is doing everything THEY can do to make webdev easy-er. That was the whole point of Blazorise, to be able to do Frontend without stepping out of the C#/.Net comfort zone.
If you want to have a simple do not think about anything website, go build a Squarespace or something.
Want to be a webdev, it has never been easier than today.

Adding Blazorise to a template is like 5 clicks, could not be simpler.

(Not trying to be hatefull or anything, but if when i was starting developing would have the readymade stuff you are asking about, i would not have learned the stuff i needed to know. Yeah easy and ready to eat is nice, but is it healthy? Most of the times it is not..)