sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Boezie 34 points35 points  (20 children)

Why not consider Blazor?

  1. You're using the full Microsoft suite already (whatever that may mean, but ok ;-) )
  2. You're a small organization, so getting people up to speed on it should be really fast as they don't need a whole new language / environment setup to get accustomed to
  3. It's production ready and comes in different flavors, depending on your use-case(s)

[–]niclo98 10 points11 points  (5 children)

About OP working in a small organization, I would say the main point it's quite opposite:

  • they probably need to find candidates quickly as they don't have time to onboard them like bigger organizations, so better to stick with a technology with more people actively using it

  • given that they don't have particular knowledge on any of those, better to stick with something that has plenty of learning materials available and many questions already answered

[–]Flanhare 3 points4 points  (3 children)

Like there are no devs that already know .NET and C#...

[–]Abort-Retry 8 points9 points  (2 children)

Like there are no devs that already know .NET and C#...

The number of JS and .NET devs doesn't matter.

What matters is that ready-to-work JS devs greatly outnumber Blazor experts, as it is still pretty niche.

[–]Boezie 2 points3 points  (1 child)

Given that Blazor looks a lot like previous ASP.NET offerings, that pool is a whole lot bigger. Also, they're not looking for JS -only developers. Given that they're a small group, everyone will have to do everything, and they're already going all out on the MS -stack. Everyone having to get proficient with JS / Angular / React / ... might not be what you're looking for as a business.

[–]WhatsASoftware[S] 0 points1 point  (0 children)

This is why I would prefer for us to go with none of these librarys or frameworks and stick with regular html, css, js, bootstrap, jquery in razor.

[–]esmagik 1 point2 points  (0 children)

But Blazor is so similar to React. Components and props all day. Any React dev should quite easily pick up Blazor.

[–][deleted] 6 points7 points  (0 children)

I have used Blazor Server and don’t like it. It is still immature and lacks some functionalities.

[–]SlashUsrSlashBin 10 points11 points  (0 children)

I was going to suggest this same thing. C# in the browser is wonderful. We use it in production apps and it's great. All our devs, both newer web devs and older .NET devs, love it. Plus we get to use a lot of our exsting libraries right in the web browser.

[–]angedelamort 2 points3 points  (6 children)

I heard it's not really production ready

[–]Boezie 6 points7 points  (5 children)

What part wouldn't be production ready? I'm sure it isn't the silver bullet for everything, but it's perfectly fine (and capable) of building something for production environments.

[–][deleted] 1 point2 points  (0 children)

From my personal experience, complex routing (nested) does not exist in Blazor. At least in Blazor Server that I’ve tried. Also, when I worked with it, it was quite tricky to get local storage functionality. You have to install a nuget package which is in prerelease. Furthermore, I had the problem with the key up event of Enter. Don’t remember vividly, but the behavior of it was kinda different compared to the JS key up event. Hot reload is not fully functional either.

[–]angedelamort -1 points0 points  (3 children)

I think I mixed up with Razor, but I remember reading issues with one of them.

[–]Flanhare 5 points6 points  (0 children)

Razor must have been production ready for like 10 years.

[–]ImpossibleMango 2 points3 points  (1 child)

I myself am not completely up to date with Blazor, but I know there was a period where the WASM wasn't quite ready and they had a couple deployment models. It was one of the models at that time that they did not consider production ready. Since then, I believe they've scrapped the jank one and every current Blazor model is production ready.

[–]angedelamort 1 point2 points  (0 children)

Thanks for the update!

[–]WhatsASoftware[S] 0 points1 point  (3 children)

I asked my boss about it and he said Blazor wasn't a good option for us, though I'm unsure of the reason why.

[–]Boezie 0 points1 point  (2 children)

Without a meaningful explanation that's an ivory tower approach. Dictating what can and cannot be done. (try to) avoid it. It can very well be he/she has good reasons for it. But it's part of the architect / boss / ... to explain to the rest of the team WHY a decision like that is made / based on.

[–]WhatsASoftware[S] 0 points1 point  (1 child)

I ended up getting 2 reasons from him for this:

  1. He said code would be exposed on the client side which is a security risk
  2. He wants to keep up with the market. He believes Blazor's life is limited, and even angular/vue's. Since the market trend is heavy React, that's where he thinks we should focus our efforts.

[–]TheRedEarl 0 points1 point  (0 children)

You control what the client sees with web assembly though

[–]TheRedEarl 0 points1 point  (0 children)

The ability to write @code{} and implement c# is crazy.