In my view it seems like F# has the potential to become one of the most versatile programming languages out there while also being one of the biggest productivity boosters.
it would also be an idea if the proxy generator would generate both the class and the interface as partial, in some cases there can be a need for more constructors because of some extra dependencies
I think Xaml has served its purpose. It is high time Microsoft moved over to writing the UIs in code e.g. Comet C# MVU or MauiReactor. Just like Flutter
Idk about pattern matching, just seems like it will simply make it harder to read code to me. I'm already avoiding using ?? since it can be more confusing sometimes. Readable code isn't just about the code being short, it's about the steps being in a logical and understandable sequence.
This talk was amazing! And the UI was so polished and nice! Can you please do another talk on doing proper authentication/ authorization, containerization, deployment etc.?
Nice talk! I think, your shooting function may have an error. If that's a TimeSpan, than TotalSeconds is the right property for the time difference. If you wait exactly one minute with your input, .Seconds is zero again, not 60. I confuse them all the time...
I just tested Console.WriteLine("\a"). There will be a sound if your sound schema has it enabled (I always use "no sounds" so no "bell"). I don't know which of the sound setting it actually is... With the default schema there's some noise.
OK third and last attempt to share this info, it keeps getting nuked for some reason. Maybe posting as a reply rather than a top-level comment , it won't get nuked ? (I'm replacing dots with spaces between the quoted words, maybe it thinks i'm spamming links ?) Must-have entries in "settings json" for C# + VS Code: "omnisharp enableRoslynAnalyzers": true, "omnisharp enableImportCompletion": true, "omnisharp enableEditorConfigSupport": true And export Visual Studio Code Styles data to an editorconfig file in the root of solutions or projects - this is way more than vanilla editorconfig, search microsoft docs for more info. Doing these four things will bring the VS Code + C# editing experience much closer to that of Visual Studio.
Can you please clarify a bit. I assume that you will run your integration tests somewhere in your CI, right. How would the CI specify the configuration for the integration testing? Is it usually done via env varilables? In production, do people usually have docker-compose in ther CI tool as well, or do they create some database instance which is a bit more real to production? And in case you know, can we also write integration tests for queue events (for message-broker, e.g, RMQ)? Does anyone know good resource on that? Thanks!
Sorry for the slow reply - only just seen this comment. The config (eg. connection string) can be hardcoded. It's the same locally vs in CI. It's just localhost. Yep, you'd do docker-compose up as part of the pipeline, then docker compose down afterwards. Yep - you can do the same concept if you're using a message broker that can be run in Docker.
Generally, yes. I didn't do that in this talk as I was showing a lot of the nuts and bolts of how things work. But all that the CascadingAuthenticationState component does is provide a Task<AuthenticationState> cascading value that components in the app can receive as a cascading parameter and then use to get the current authentication state of the user.
Sorry, guys. But is that real that I should in 2021 write “while not a.endOfStream” and not “f.readlines()”? Or this line of code have very special meaning?
Firstly, thank you for watching the video and for your comment. Since I don't read data from files very often, I wasn't aware that there were better ways of doing it. The primary reason for choosing that style, other than the obvious getting data from the file, was to show how to use IDisposible classes in F# with use and new.
Thanks for this video. The website feels really dense and too abstract to understand what the project is about. I found this video and your demos helpful to understand what Reaqtor does and could be used for 👍.
Nice talk! I feel integration test for APIs (specifically using a real sql server running in docker) does not get the spotlight it deserves. Seeing these direct assertions from the test project on the database using dapper now, it seems like the way to go.
The content is great, but even with monitor brightness turned down to 10%, everything is just too bright for me. In future videos, might you consider at least a medium/darker grey for the slides/IDE theme? I had to pop the video out in a window and made it smaller to make it bearable to the old retinas.
I was so happy to see him using a high contrast as that medium and darker grey are exhausting as one needs to gaze and squeeze the eyes to see what's actually happening (or press your nose against the screen). I really don't understand why people work on a dark theme as, apart from experience, it is already scientifically proven it is harder for your brain to process the text.
Hi Chris, I have a follow-up question regarding security. I've always built apps using ASP.Net Core Identity user management to secure my web Apps/API's(jwt). Are you recommending developers to start using cloud providers such as Azure AD, Auth0, Okta and etc?
I am. I don't think most developers need to role their own auth and with the costs being so high of getting it wrong, I'd always leave it to the experts. Services like Auth0 and Azure B2C are free for a crazy number of users, 5000+.
