ripley12

42 ms·

391.
by ripley12 5y ago
Are you using PSFzf or something else? https://github.com/kelleyma49/PSFzf
392.
by ripley12 6y ago
Some high level info: https://www.onmsft.com/news/heres-an-early-first-look-at-mic... An internal binary leaked a while ago, someone confirmed the WebView2 aspect: https://twitter.com/teroalhonen/s
393.
by ripley12 6y ago
New Outlook is being written with a web UI, using WebView2 on Windows. MAUI lets you do something similar (embed a web view, do your UI in that with Blazor or any other web tech).
394.
by ripley12 6y ago
I think you might need to wait for that, MAUI’s still being worked on for the upcoming .NET 6 release. My understanding (based on talks and blog articles) is that it’s basically Xamarin brought up to speed with .NET 6. So it can use the SDK
395.
by ripley12 6y ago
FWIW, this will be supporting Blazor in addition to XAML. So you can have a MAUI app that just handles native hosting etc. and shows your actual UI in a web view. It's admittedly confusing and not all that well explained.
396.
by ripley12 6y ago
This is very foreign to me, and I'm not a VB hater. I spent a long time working in a codebase that was half C# and half VB.NET, and after a couple years I could switch between the two without thinking. VB has slightly more verbose synt
397.
by ripley12 6y ago
Agreed, I really think Blazor is the way forward for .NET UI. It's bittersweet, but: the Windows and .NET teams have failed to deliver a compelling alternative to web UI, and I'm impressed with how well Blazor integrates web UI wi
398.
by ripley12 6y ago
FWIW, I'm in the same bucket and I'm leaning toward Blazor. There's a big push in .NET 6 to deliver "Blazor Desktop", which is essentially more native wrappers around Blazor Server: https://github.com&#x2
399.
by ripley12 6y ago
Not sure but this upcoming (Friday April 23) talk by Mads Kristensen should have the answer: https://www.youtube.com/watch?v=L8b3kFriwCs
400.
by ripley12 6y ago
Amen. Latest related issue I've run into: Visual Studio ships its own 32-bit Git binary, and getting that to play nicely with the native Windows OpenSSH for Git authentication is... not fun. https://developercommunity.visual
401.
by ripley12 6y ago
Out of curiosity, which generation? My spouse had a nightmarish experience with a Surface Book 1 (blue screens, mechanical failure on the base-screen connector) but I've been generally happy with a 2.
402.
by ripley12 6y ago
UI for the automatic brightness adjustment setting is finally coming soon: https://twitter.com/DirectX12/status/1379911777849237508?s=2... I agree that it’s incredibly bad (and I generally like Surface devices oth
403.
by ripley12 6y ago
That caught my eye too, super exciting. Seems like this is where most of the detailed design discussion is taking place: https://github.com/dotnet/runtime/issues/45689
404.
by ripley12 6y ago
FWIW, fixes/improvements for some of those fundamental issues are coming and/or available in preview releases. Like new+custom data types: https://www.microsoft.com/en-us/microsoft-365/blog/2020&#x2F
405.
by ripley12 6y ago
My understanding is the opposite; now that they're planning to merge Mono and CoreCLR, there is significantly more pressure on the .NET team to have a proper AOT solution. "Early adopters can experiment with native AOT form factor
406.
by ripley12 6y ago
Have you seen the Blazor work planned for .NET 6? Hot reload and desktop apps with Blazor UI are both priority-0 (ultra-high priority) epics, I'm really looking forward to it. https://themesof.net/
407.
by ripley12 6y ago
> And you end up with a console app that is 20-100MB. FWIW, this is sort of a legacy of .NET's "enterprisey" history. Code size and trimming wasn't really a priority when most .NET code ran server-side or inside enter
408.
by ripley12 6y ago
Ugh, true. I'm pretty annoyed by how many features are missing from 3.0, I won't be able to use it in my hobby app because I depend on MediaPlayerElement for audio.
409.
by ripley12 6y ago
Aesthetic differentiation is an interesting consideration, but even aside from that the native UI framework options are currently not practical for applications like Office. Like, their options are: - Wait for WinUI 3, hope it’s good+stable
410.
by ripley12 6y ago
Yes, I know. My point was that it’s not like Electron where they ship Chromium with every app, it’s more like a browser tab in terms of resource consumption.
411.
by ripley12 6y ago
The WebView2 runtime is going to be shipping with Windows soon. I imagine an app using it will be about as resource-hungry as a browser tab.
412.
by ripley12 6y ago
It's unlikely that they'll be bundling Chromium with the individual apps, at least on Windows: "In the future, the Evergreen WebView2 Runtime plans to ship with future releases of Windows." https://docs.micros
413.
by ripley12 6y ago
Yeah that wasn't the best example on my part. But I have tried it and confirmed that calling lambdas defined in another grid cell doesn't work. Specifically: 1) Put =LAMBDA(x, x+1) in A1 2) Try calling =A1(1) from any other cell -
414.
by ripley12 6y ago
You can, but you can't (currently?) do =A1(x) where A1 is a LAMBDA function. I think LAMBDA(...)(x) is only useful for testing/development, but maybe I'm missing some good use cases.
415.
by ripley12 6y ago
Huh, are you sure? I don’t think you can (currently) define a lambda in a cell without also calling it in that cell (which means the cell now evaluates to the function’s return value, not a function). The LAMBDA docs: “If you create a LAMBD
416.
by ripley12 6y ago
Yeah, that’s why I added a qualifier. I can’t see that being much use outside of testing/debugging functions, since it would usually be simpler to just write that without the LAMBDA call.
417.
by ripley12 6y ago
=LAMBDA(...) does return an anonymous function - and then you use the Names Manager to name it. It is a bit weird and confusing because you currently can’t really use the anonymous functions without naming them, but maybe they’re going to r
418.
by ripley12 6y ago
Ah yeah, the Rudy you’re thinking of is Rudy Huyn - he’s now working at MS on first-party native Windows apps.
419.
by ripley12 6y ago
A few interesting points: - The Simple Apps epic should greatly simplify writing tiny standalone programs. Feels like a natural evolution of the recent top-level statements feature: https://github.com/dotnet/core/i
420.
Themes of .NET: High-level plans for .NET 6(themesof.net)
2 points by ripley12 6y ago|2 comments

More ›