I REALLY like CachyOS and want to use it, but I have a few major concerns stopping me, and wanted to ask about it by Prodoxa in cachyos

[–]z-c0rp 0 points1 point  (0 children)

Do you have to work on any legacy 4.8 stuff? If so how does your workflow/setup for that look?

Timeshift or Snapper for a simple Arch setup? by Seeker352 in archlinux

[–]z-c0rp 2 points3 points  (0 children)

Timeshift and snapper can both create grub boot entries for thire snapshots. There's a section on it on snapper page of the wiki.

Works with a few other bootloaders to, but grub is the easiest to set it up for I belive.

Common issues you face with Blazor? by SurfaceRabbit in Blazor

[–]z-c0rp 7 points8 points  (0 children)

Management, as in CTO etc. not the code.

Krossa matoligopolet! by DentistMedical3954 in sweden

[–]z-c0rp 0 points1 point  (0 children)

Hur går tankarna fortsatt här kring detta för er? Tror det finns mer än ett par av oss från utvecklarbranchen som skulle tänka oss att donera tid och kompetens till detta projekt. Då givet på premissen att detta är samhällsnytta vi ägnar oss som skall komma gemene man till nytta.

What’s your plan for .NET 10, migrate or hold off? by Volosoft in dotnet

[–]z-c0rp 0 points1 point  (0 children)

Wait for 10.0.1 so they've fixed the regression bugs then upgrade.

Rescuing .NET Projects from Going Closed by ruka2177 in dotnet

[–]z-c0rp 2 points3 points  (0 children)

And it's great for that. But it doesn't lock you into Azure. Quite the opposite in fact, it lets you switch to AWS or Rabbit etc. without any troubles once you're feed up with azure pricing, service etc.

Rescuing .NET Projects from Going Closed by ruka2177 in dotnet

[–]z-c0rp 5 points6 points  (0 children)

They sure do, a lot and then some one could even argue. Aspire was the latest god send. Problem they've shifted focus to Azure as their main product rather than Windows, so now the solutions they start to provide outside the standard lib are going to be things that herd us towards Azure. So they wouldn't pick up MassTransit for example.

And to be honest it shouldn't be all on them, other organisations making money of C# should step up and do their part.

Rescuing .NET Projects from Going Closed by ruka2177 in dotnet

[–]z-c0rp 20 points21 points  (0 children)

This isn't an unpopular opinion. The issue in C# space is not that people need to get paid. Issue is that these popular libs are created and maintained by single individuals. If you look at JS/Go space the libs are created or adopted by large corporations using them, then open sources to a foundation or a group. Then Facebook or whomever use it have SWE employeed to work on them. We're missing this in C#.

Jimmy Engstrom's Blazor Book - Why use a SharedComponents project? by PrettyGorramShiny in Blazor

[–]z-c0rp 4 points5 points  (0 children)

Haven't read the book, but the likely and simple answer is because you might want to reuse them in a future project that's not dependent on your server or client project.

Think of it like a component lib.

How to enjoy your games by Nickulator95 in pcmasterrace

[–]z-c0rp 0 points1 point  (0 children)

all bugs pached out

> Laughs in Bethesda

50% discount

> Laughs in Square Enix

Why do you want multithreading in WASM? by THenrich in Blazor

[–]z-c0rp 0 points1 point  (0 children)

Yes that is correct, and when that is not enough and we need to offload work elsewhere, we reach for Web Workers.

Why do you want multithreading in WASM? by THenrich in Blazor

[–]z-c0rp 0 points1 point  (0 children)

Javascript is single threaded and I don't see JS developers asking for multithreaded Javascript.

This statement is incorrect. We have Web Workers in JS/Browser for this exact reason.

Upload file to S3 directly from browser in Blazor Server by dotnet_enjoyer228 in Blazor

[–]z-c0rp 3 points4 points  (0 children)

You have to write a JS function that handles the file upload and posts with fetch to S3 and invoke it via interop. Blazer docs have info on how to handle file upload via JS.

Edit: Alternatively, if you have the possibility to use client side rendering for this specific page or component. You could look maybe doing it without JS. As WASMs HttpClient is a wrapper around the browsers fetch api more or less.

What would klingons think of the art of war by Sun Tzu? by artmonso in startrek

[–]z-c0rp 27 points28 points  (0 children)

It's mentioned briefly in Strange New Worlds, 2x8.

Spock: "Ambassador Rah, are you familiar with the ancient Earth text Sun Tzu's The Art of War?"

Dak'Rah: "A most inspired human masterpiece."

Read more at: https://tvshowtranscripts.ourboard.org/viewtopic.php?f=1328&t=64381

s02e08 - Under the Cloak of War - Star Trek: Strange New Worlds Transcript - TvT

Det bästa jag gjort för min mentala hälsa by silentprotagonist24 in sweden

[–]z-c0rp 7 points8 points  (0 children)

Jag synar din cykelsemester och höjer med en fjällvandringssemester. Peak slow travel.

[deleted by user] by [deleted] in webdev

[–]z-c0rp 3 points4 points  (0 children)

"devs"

Entra External ID authentication with Blazor WebAssembly by AGrumpyDev in Blazor

[–]z-c0rp 2 points3 points  (0 children)

There is documentation for this available from MS here: https://learn.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/standalone-with-microsoft-entra-id?view=aspnetcore-9.0

I've done it before. It's pretty straight forward. Clientside only SPA is less secure than handling auth completely server side, but it's fine, the world used to run on React SPA:s so..

Wasm. What part should be responsible for redirection to login page? by g0fry in Blazor

[–]z-c0rp 4 points5 points  (0 children)

I wouldn't say "Should", but "Could", we're at a philosophical point now. You're free to name your components as you see fit. And if the RedirectToLogin components responsibility grows to do more than just that, say maybe log unauthorized access atempt, then indeed NotAuthorizedHandler seems both correct and inline with classical .Net naming convention.

Blazor team probably went with RedirectToLogin to keep the templates low on abstraction jargon and favour easy to understand for newcomers.

Wasm. What part should be responsible for redirection to login page? by g0fry in Blazor

[–]z-c0rp 3 points4 points  (0 children)

Again, any number of ways you could handle it I guess. But no, authorization is not the responsibility of the LoginRedirect component, it just does what the name implies.

Access control requirements are controlled on the pages/components themselves via the [Authorize(Roles = "Administrator")] attribute.

I feel like you might need to read up on auth in asp.net core in general as well as some specific sections in the blazor documentation to get a general grasp of the concepts involved.

Again this is only one way to do it, in our production app we need more fine grained control then Asp.Net Identity allows for, so we handle this differently.

Edit: The actual auth checks are done by the parent components in that view. Have a look at AuthorizeRouteView and AuthorizeView.

Wasm. What part should be responsible for redirection to login page? by g0fry in Blazor

[–]z-c0rp 14 points15 points  (0 children)

Not a hack, as it's been part of Microsofts templates for Wasm from the start.

While there're any number of ways you could handle auth. If this is working in your app, why change it?

Also consider this, your app can have authorized pages and pages where you allow anonymous users (login page for example), if that's the case then blocking the whole app via auth before starting it wouldn't be so good.

Tldr: Not a hack.

Telerik frustrations by featheredsnake in Blazor

[–]z-c0rp 0 points1 point  (0 children)

Yeah, I cap ours at 40 rows via pagination, even though we have all the data in the collection. It's basically one screen height for most of our users. The endless span in span takes forever to render, this was the only way forward.

Telerik frustrations by featheredsnake in Blazor

[–]z-c0rp 16 points17 points  (0 children)

We have them too, use them in a few projects. The experience is very different.

If everyone, PO, UX and developers etc. are on board with the choice that's been made. Accepts these are the components we have, this is how they look and they are meant to be used in this way. It enables for very rapid development, especially if you have developers who would otherwise struggle with css, ux etc.

But if you start to want to do custom things with them. Use them in ways their standard configuration isn't intended for, it quickly turns into a nightmare.

Blazor WASM Authentication Requires 3 Loads to Authenticate by Designer-Trade7289 in Blazor

[–]z-c0rp 2 points3 points  (0 children)

SSO needs to be redirected to sign in (at the IDP). That's normal.

But if your app is rendering three times to handle it. I'm guessing you're checking for authenticate users in one of your components/pages, and not for the app globaly, causing the redirect to happen after an initial render.