@J_aa_p I really like my #surface pro, because I travel a lot and am 6'5" (196cm), so a laptop isn't useful. The Surface is a dev level device that is also good for entertainment and other stuff.
Is there any way to create/maintain a unique user id value for #blazor that goes across server-static and server-interactive pages? Other than a cookie, because that's too broad - I want something that is more per-tab than per-browser.
I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.
A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.
@bradwilson Have you tried creating a physical partition for #devdrive or just a virtual disk? I’ve only tried a virtual drive, and am curious if a partition would help.
@khalidabuhakmeh@elan@redzimskidev@KirillOsenkov@bradwilson I think wasm in the browser is particularly useful for LOB app dev. When a user is going to spend the vast majority of their day in a single page that is usually highly complex and interactive, having all that processing run on the client is extremely beneficial to the user and the overall system.
For web scenarios it is a lot harder to justify for sure!
A wasm Blazor app is basically the same as a WPF app in many ways, and so scenarios where a smart-client app is beneficial due to reduced data transfer, reduced server load, etc. might be environmentally good too.
Or maybe not - maybe the point is we should still be using VT100s?
@dreamykeaver@wagemakers I am a #dotnet developer, and almost all of my server code targets #linux. Hard to show it to anyone, because the front end is all web.
@khalidabuhakmeh@dreamykeaver@wagemakers And maybe that's the thing. Desktop development for any OS has become quite a niche, because most corporate software targets the only true cross platform UI tech out there: the browser.
Why is it that almost 100% of the time when I go to create or use a #dotnet#dotnetmaui project in #visualstudio that it just fails to build for random reasons - like being unable to find the right #nuget packages or some other obscure b.s. that requires lengthy searching and trial-and-error to maybe fix?
Basically, my experience with #dotnetmaui almost always sucks.
@khalidabuhakmeh Actually, this might solve a different problem - where I can no longer build an older version of #cslanet because it multi-targets net6, net7, and net8 and #dotnetmaui can't find the net7 stuff it needs to build.
I'm guessing that global.json supports multi-targeting?