0:37 Ah! The penny drops! NOW I understand why you're sidelining WASM rendering in Blazor in favor of the inferior Server-based experience. You feel the need (pressure from the corporate overlords perhaps?) to force us to go down the AI route even if it means pushing us to use a mediocre product.
You can also of course also access AI services from the client running on WebAssembly - it's just more work. Whatever credential you're using to access the AI service will typically need to be handled securely on the server, so it's super convenient that Blazor allows you to also handle interactivity from the server as well. If you go with WebAssembly instead, then you need some sort of API endpoint that exposes the AI functionality to the client and you need to work out some sort of security model for that endpoint.
Dan, as usual, you have done a great job. This is the only tutorial I need is to integrate the semantic kernel with my Blazor application. Thanks!
very cool adjusting themes!
Nice and precise!
Does anyone know where can i get the code of Dan's demo? I didn't find it in repo
how do you "get github copilot up"?
Great application, thanks you
I downloaded the sample code and the chat works, but colors doesn't change, Did I miss something?
where did you download the code from?
Where did you get the code?
do it using azure cognitive services for human speech. something like apple siri or alexis
0:37 Ah! The penny drops! NOW I understand why you're sidelining WASM rendering in Blazor in favor of the inferior Server-based experience. You feel the need (pressure from the corporate overlords perhaps?) to force us to go down the AI route even if it means pushing us to use a mediocre product.
You can also of course also access AI services from the client running on WebAssembly - it's just more work. Whatever credential you're using to access the AI service will typically need to be handled securely on the server, so it's super convenient that Blazor allows you to also handle interactivity from the server as well. If you go with WebAssembly instead, then you need some sort of API endpoint that exposes the AI functionality to the client and you need to work out some sort of security model for that endpoint.
@marklnz Interesting point.
What would you prefer. I wanna know your opinion on what to do?
It doesn't know what ChatHistory is...