Marc-André Moreau

@WithinRafael @dxzdxz1 But questionable UX aside, the Bing search in the start menu must be totally worth it for Microsoft to sacrifice the quality and reliability of the most critically important feature, which will always remain to find and start your apps the quickest way possible. Not search Bing.

@WithinRafael @dxzdxz1 If they actually observed users through the entire loop, they'd realize that whenever you mistype an app and press enter, with the sluggish delay of the start menu, it's easy to launch Bing by mistake. The proper UX would be to return no results, or keep web results separate

Microsoft: Faster responsiveness in core Windows experiences like the Start menu, by moving more experiences to WinUI3 [...] Hot take: Good luck with MSIDC.

@dxzdxz1 @WithinRafael What's frustrating is that it's probably justified by vanity metrics internally. I'm sure there is an insane number of daily active "users" trying to launch apps that are unintentionally triggering Bing searches. Those same users most likely even launch "web apps" by mistake

@dxzdxz1 @WithinRafael The point is I should not have to write such a blog post in the first place. The Bing search in the start menu is a prime example of a "feature" that nobody asked for, yet degrades or sometimes *breaks* critical features that everyone needs. The start menu should start apps fast

@shanselman @davidfowl Can you help get the Start menu just be fast and stable at launching apps, which is arguably its primary critical feature? The Bing search in the start menu is known to make it sluggish and on occasion, completely unresponsive: awakecoding.com/posts/disable-…

Working on this is part of my new job! Even more to come blogs.windows.com/windows-inside…

Congrats to the @cursor_ai team on the launch of Composer 2! We are proud to see Kimi-k2.5 provide the foundation. Seeing our model integrated effectively through Cursor's continued pretraining & high-compute RL training is the open model ecosystem we love to support. Note: Cursor accesses Kimi-k2.5 via @FireworksAI_HQ ' hosted RL and inference platform as part of an authorized commercial partnership.

@PrzemyslawKlys @ryanyates1990 @SasStu @merill It just crossed my mind that I could implement automatic PowerShell module cleanup in multi-pwsh as well, since I've already had to hook PowerShellGet and PSResourceGet for the virtual environment overrides. I can extend Install-Module and Install-PSResource cmdlets

My main problem with this and other stuff is that a lot of us do the same thing and then there are 10 modules doing the same thing, 50 scripts doing similR thing. I know @merill has his stuff around entra updates, and few other people theirs. But as i use UniGetUI I would probably use it.

Why does Update-Module in #PowerShell install the newer version of the module without uninstalling the old one? If you frequently update the same module, you quickly end up with several leftover module versions, and no quick and easy way to clean things up

@PrzemyslawKlys @ryanyates1990 @SasStu I'd rather spend the energy and time I have fixing the problem from UniGetUI, and hopefully one day the PowerShell team will want to address this long-standing issue at the source. In the meantime - not worth most people's time and energy, unfortunately

@PrzemyslawKlys @ryanyates1990 @SasStu I hear you, there's a generalized sentiment that a pull request to fix long standing issues is such an uphill battle that it's not worth even trying anymore

@ryanyates1990 @SasStu @PrzemyslawKlys The truth is this usually goes unnoticed, and the first time someone notices that old modules just stay there, the reaction is usually that this is silly. Update-Module doesn't update a module, it's just Install-Module for the newer version, leaving the old one in place

@ryanyates1990 @SasStu @PrzemyslawKlys True, it would likely have a better chance of getting accepted in PSResourceGet now, but what are the chances this is going to be accepted given the potential edge cases to handle? The problem is most likely to remain unsolved, leaving it up to users to clean up the litter

@PrzemyslawKlys @AlexJPawlak But I agree about better module dependency handling

@PrzemyslawKlys @AlexJPawlak Uh, PowerShell relies heavily on JIT so I think we can forget about Native AOT

@ryanyates1990 @SasStu @PrzemyslawKlys I couldn't make it for yesterday's community call, but I'm hoping to meet and talk with Steve Lee for the first time at the MVP summit next week. Let's just say I need more than just acknowledgement, I want actions to be taken to make sure it never happens again

@awakecoding @SasStu @PrzemyslawKlys Steve did at least acknowledge your concerns kn the delay in Yesterday's community call

@SasStu @PrzemyslawKlys I know. I just don't know when we'll have PowerShell 7.7 given that 7.6 barely just became generally available

@awakecoding @PrzemyslawKlys That‘s something they are working on #psusercontentpath-relocation" target="_blank" rel="nofollow noopener">devblogs.microsoft.com/powershell/pow…

@PrzemyslawKlys @SasStu Why did they put it in My Documents in the first place. That's the first mistake that was done, really

@SasStu @awakecoding Anyways it's not all PowerShell fault, OneDrive is still a toy that you can't really control. Why can't you exclude folders? Specific files from sync and control it centrally.