Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET Blazor

dusted.codes

Post reply on HN
Print view View original

181–190 of 302 posts

Re: .NET Blazor

#181

Post by SantiagoElf »

kumarvvr wrote: post #113

All the dis-advantages are not relevant for enterprise LOB apps, which Blazor is best suited for. Millions of .NET developers across the enterprise world are heaving a sigh of relief to never have to touch JS and be cozy and comfortable in their .NET ecosystem. With the latest addition of fully SSR, Blazor is also well suited for CMS, Blogs, Content Mills, small web apps, portfolio sites, etc. But, as a developer who…

BBBBBBBBBBBBBBINGOOOOOOOOOOOOOOOOOO!

Yes, at the end of the day, businesses use software in LOB apps.

Period.

Get shit done.

WebForms/ASP.NET MVC/.NET Core MVC/Blazor will outlive ANY js framework.

Re: .NET Blazor

#182

Post by skrowl »

kumarvvr wrote: post #113

All the dis-advantages are not relevant for enterprise LOB apps, which Blazor is best suited for. Millions of .NET developers across the enterprise world are heaving a sigh of relief to never have to touch JS and be cozy and comfortable in their .NET ecosystem. With the latest addition of fully SSR, Blazor is also well suited for CMS, Blogs, Content Mills, small web apps, portfolio sites, etc. But, as a developer who…

[dead]

Re: .NET Blazor

#183

Post by password4321 »

osigurdson wrote: post #140
kumarvvr wrote: post #113

All the dis-advantages are not relevant for enterprise LOB apps, which Blazor is best suited for. Millions of .NET developers across the enterprise world are heaving a sigh of relief to never have to touch JS and be cozy and comfortable in their .NET ecosystem. With the latest addition of fully SSR, Blazor is also well suited for CMS, Blogs, Content Mills, small web apps, portfolio sites, etc. But, as a developer who…

The problem is, all of this stuff will probably be dead in a few years. I think they would be better off working within established paradigms rather than trying to do something completely new. How about, for example, making it as easy as possible to use React with a C# backend?

Web Forms ("I'm not dead"), Silverlight, etc.

Re: .NET Blazor

#184

Post by skrowl »

LaGrange wrote: post #118
kumarvvr wrote: post #113

All the dis-advantages are not relevant for enterprise LOB apps, which Blazor is best suited for. Millions of .NET developers across the enterprise world are heaving a sigh of relief to never have to touch JS and be cozy and comfortable in their .NET ecosystem. With the latest addition of fully SSR, Blazor is also well suited for CMS, Blogs, Content Mills, small web apps, portfolio sites, etc. But, as a developer who…

> All the dis-advantages are not relevant for enterprise LOB apps, which Blazor is best suited for. The disadvantages: the _actual user_ is going to have a horrible time with the application. It will load slowly, work slowly, probably break the moment you inevitably will have to touch JS, and if the browser the user hates anyway is out of sync with the forced updates, the entire thing will blow up. But enterprise LOB…

[dead]

Re: .NET Blazor

#185

Post by kittoes »

andsoitis wrote: post #130
bsuvc wrote: post #125

Here is my personal experience. I've been working on a large-ish Blazor (Server) application for about a year. The choice to use Blazor was not mine, but I went into it with an open mind. For context, I have used React and Angular in the past. I will never used Blazor again. Performance is not good, with CPU always at some base level, even when idle. My machines fan is always cranking while developing it. Hot reload…

> a proper front end framework Do you think a WASM approach has merit or do you think it is doomed?

Am using Blazor WASM in our shop and absolutely loving it once deployed. The hot reload and other development headaches are -really- painful, but just being able to use our existing C# libraries everywhere has been a game-changer for us.

Re: .NET Blazor

#186

Post by _5hxt »

kumarvvr wrote: post #113

All the dis-advantages are not relevant for enterprise LOB apps, which Blazor is best suited for. Millions of .NET developers across the enterprise world are heaving a sigh of relief to never have to touch JS and be cozy and comfortable in their .NET ecosystem. With the latest addition of fully SSR, Blazor is also well suited for CMS, Blogs, Content Mills, small web apps, portfolio sites, etc. But, as a developer who…

This may help if you'd like to keep front and backend(s) separated: https://quicktype.io/

Re: .NET Blazor

#187

Post by avgDev »

bsuvc wrote: post #125

Here is my personal experience. I've been working on a large-ish Blazor (Server) application for about a year. The choice to use Blazor was not mine, but I went into it with an open mind. For context, I have used React and Angular in the past. I will never used Blazor again. Performance is not good, with CPU always at some base level, even when idle. My machines fan is always cranking while developing it. Hot reload…

I have a large blazor project and do not have fan cranking at all. Hot reload is VS issue.

I have a completely difference experience but then again I'm creating business apps and do not anything 'new'.

Re: .NET Blazor

#189

Post by withinrafael »

I find it hard to justify/invest the time needed to really dig into Blazor. Everywhere I go/look, buisnesses are stuck on mature solutions utilizing ASP.NET MVC 4 or 5 + Entity Framework (non-core). Just upgrading beyond that requires a lot of migration work, let alone rearchitecting for the new and shiny Blazor.

Re: .NET Blazor

#190

Post by CharlieDigital »

JackMorgan wrote: post #170
kumarvvr wrote: post #113

All the dis-advantages are not relevant for enterprise LOB apps, which Blazor is best suited for. Millions of .NET developers across the enterprise world are heaving a sigh of relief to never have to touch JS and be cozy and comfortable in their .NET ecosystem. With the latest addition of fully SSR, Blazor is also well suited for CMS, Blogs, Content Mills, small web apps, portfolio sites, etc. But, as a developer who…

I use swashbuckle and swagger-typescript-api to automatically scrape my controllers and generate API calls and TS types every time I rebuild. No hassle or overhead at all. No need for converters or anything. I've been using this now for several projects, it's a great way to have all the power of TS for client side and C# for server side. https://www.npmjs.com/package/swagger-typescript-api https://www.nuget.org/packa…

I do the same.

I have a small write-up here: https://chrlschn.dev/blog/2023/10/end-to-end-type-safety-wit...

You get end-to-end type safety (even better once you connect it to EF Core since you get it all ways to your DB).

With this setup with hot-reload (currently broken in .NET 8 [0]), productivity is really, really good. Like tRPC but with one of the most powerful ORMs out there right now.

[0] https://github.com/dotnet/sdk/issues/36918

Post reply on HN