Fav. thing I've worked on recently?

Blazor and creating our framework around authentication/authorization.

wait, someone actually had a *good* experience with blazor?

@Wisecrack > "a *good* experience with blazor?"

So far, very good. We're not writing games or anything crazy. We're starting out with migrating SharePoint 'apps' into the modern world.

Security (authentication and authorization) has been the biggest hurdle. Nothing specific to Blazor, just soooo many different ways to do it. Of course, the 'company way' of doing things does not fit in the current security standards, so we wrote our own. Makers of rube goldberg machines would be proud.

@PaperTrail the makers of rube goldberg machines are in hell. in another life they made boobytraps like maniacal evil gnomes in santas little workshop of horrors.

Look I love mouse trap. I love me some RGMs.

But you're telling me you really do enjoy blazor? I'm still a little in disbelief, because this is legit the first time I've heard anyone say anything good about it.

And isn't rolling your own security considered a red flag?

@Wisecrack > "And isn't rolling your own security considered a red flag?"

Yes, but it is the 'company way'. Recently found out there was a decision that not every employee would be getting an Active Directory account and those hourly employees were logging in via a backup method of SQLServer authentication (employee # and a 4 digit passcode, TL;DR).

DBAs brought it to our attention ('guys, we're not going to maintain your security') and in a couple of days our in-house genius developed his own encryption of storing end-user passwords and full stack authentication and authorization (look up AzMan).

Even has an internal message framework that notifies any+all logged in apps (client side, web app, etc) when a password changes/expires. Ex. I change my password, if I'm logged in to a web app, it auto-logs me out (forces re-authentication).

Again, he did this all within a couple of days (testing, deploy-able docker containers, and hooks into nomad container orchestration).

@Wisecrack > "But you're telling me you really do enjoy blazor?"

Yes, for our internal apps and as compared to my experience with React and Angular. Nothing wrong with either, I liked those too, but being able to have a single code base (C#) has been a big productivity boost.

Had to do some workarounds for 'Platform not supported' exceptions, but I'd say 90% of our core library works in Blazor (logging, security, and various utilities). Having an in-house GUI genius helps (not me!).

Our public website however will likely always be 'normal'. React, lots and lots of javascript, etc. Our web devs are biased and territorial with their toolset.

Ex. We were on Angular 1...not kidding...up until a few years ago when the "Angular now and forever!!" devs quit and we hired fresh folks.