You can now launch the standalone dashboard using the aspire cli, without containers:
aspire dashboard run
#run-the-dashboard-standalone" target="_blank" rel="nofollow noopener">aspire.dev/dashboard/#run…
Est-ce que c'est parce que le réchauffement climatique est censé transformer le Québec en Floride du Nord qu'à chaque fois que TVA Nouvelles fait un Vox pop sur l'hiver, on a l'impression qu'il n'a pas neigé depuis 400 ans?🌨️❄️
"J'aimerais venir d'ailleurs" 🤣🤣🤣
@taviso My understanding was that the goal is to make it expensive to switch your browser's "identity" around to bypass regular rate limiting. You either stick to the same and get rate limited, or get slowed by the hashes, targeted website gets some breathing room either way.
Policies (and enumerated exceptions to policies, and exceptions to exceptions) are a piss-poor substitute for judgment. Rules are blunt instruments that stunt your engineers' development and critical thinking skills.
Allow me to illustrate.
Docker is a game changer for software acquisition (like vagrant before it). That ability to encapsulate the instructions, package and consume the software is brilliant. You that tried getting a proper python development environment setup ?? 🤣
@theprincessxena Huh, I would have expected at least something from the exit code. 0 is sad :( I'd make sure you have the redistributables if you haven't checked that yet:
#latest-microsoft-visual-c-redistributable-version" target="_blank" rel="nofollow noopener">learn.microsoft.com/en-us/cpp/wind…
@theprincessxena That's part of the sysinternals tools. You can retrieve them from #sysinternals-live" target="_blank" rel="nofollow noopener">learn.microsoft.com/en-us/sysinter…
Both procdump & procmon are there
@theprincessxena Beyond that, I would try launching it through "procdump -ma -e Dolphin.exe" so see if any early exception get caught. Or filtering procmon on that process and checking the events if something rings a bell, but it is a lot of guesswork from there
@theprincessxena I'd check $LASTEXITCODE in powershell to see if it's one of the well knowns. First guess would be a missing external dependencies like VC redistributables which can break relatively silently at startup I think.
This strange tweet got >25k retweets. The author sounds confident, and he uses lots of hex and jargon. There are red flags though... like what's up with the DEI stuff, and who says "stack trace dump"? Let's take a closer look... 🧵1/n
@davidfowl And to be clear, everyone of our devs has a VS license, and we are building .NET software, largely on Azure. We are closely tied to Microsoft already... But the stability of our production software being tied to an IDE release is a very discomforting feeling...
@davidfowl To release known miscompilations and code-breaking bugs because they are not a big enough impact in the context of VS is a huge red flag to anyone trying to build on .NET. It must be bigger than one of its IDEs
It’s evident that there’s still a lot of work on our side and education around our tooling story for .NET. Doesn’t matter how free and open the runtime is, people point at the tools (even when they are free to use). The stigma is so strong that any sniff of “I have to pay” drives people away (even when you don’t have to pay).
On top of that, people want the “most native” tooling experience that a language ecosystem provides. This is why people want cross platform visual studio. Rider and VS Code are excellent options but not as feature rich as VS. The incumbent .NET developers will always recommend the tools they grew up on, Windows and Visual Studio.
Even if the tooling in another ecosystem is less rich, it might be what developers in the ecosystem expect.
We spend lots of time making sure .NET works well on the command line but it’s not enough…
@jaredpar@kevin_chalet@tannergooding To me, the reach of the C# compiler (and the dotnet SDK) is much, much greater, than the latest update of Visual Studio. It's all editors, it's release pipelines, it's production applications. Feels weird that it gets treated as a subcomponent of VS
@kevin_chalet@tannergooding You're making the assertion though that compiler bugs are special here. I disagree. Any part of the VS stack that has a bug can make the product unusable.
Unpopular opinion: .NET's release cadence sucks: it's too fast for those who want real LTS support (3 years of support is not enough for many applications) but also too slow to fix critical bugs/regressions like github.com/dotnet/roslyn/….