@MattParkerDev@wieslawsoltes Love it! Tons and tons of work of course to do in the language. Is there a csharplang thread yet? Btw I'm not on Twitter often
I'm excited to be joining Microsoft Fabric as a senior software engineer! I'm grateful for this opportunity to tackle new challenges together with an amazing team, stretching the limits of .NET build technology. I'll also continue as a member of the C# language design team.
Today was my last day at Technology Solutions Associates, after nearly thirteen years total and seven years as a partner. Signing out for the last time is quite a feeling. I'm grateful for the opportunities I had with them, and ready for the next adventure in 2026. Stay tuned!
I've added a 360° node viewer to my Myst IV Asset Explorer (https://t.co/UeFXYiHkRv)!
Rendering a skybox with SkiaSharp in Avalonia, from 3D projection first principles, was satisfying. Looking around at the final result with its layer transparency is surreal.
I made an app to browse and extract #Myst IV game assets, and play audio assets with gapless looping using #dotnet and #AvaloniaUI: https://t.co/UeFXYiHkRv
It hits a nostalgic spot to have original game music instead of the soundtrack's remix; I grew up playing the Myst games.
I think that a fairly reliable mark of high intelligence is the capacity to recognize the signal within the noise of someone's 'wrong' take.
Pseudo-intelligence gleefully pours out the bathwater, raw intelligence finds & nurtures the baby.
The future of AI-assisted programming isn’t “prompt-to-app.”
That’s a short-term phase.
The real shift is much bigger:
• Humans write only specs
• AI handles all implementation
• Code becomes completely disposable
Let me explain 👇
@controlflow If LLMs will continue to be more and more able to understand context as humans do, then maybe continuing to design languages for humans *is* designing for LLMs? I'm curious too.
@Aella_Girl is refreshing. She writes from an unusual place: a deep acceptance of herself and what the world is, and the freedom and playfulness which this entails. She "gets it" on a rare level. Her writing provides that same opportunity for open minds. A very cool human.
I'm losing the feeling of "what's happening is bad" that used to pop up for me when facing difficulties. Difficulties are the pathway to heart and soul and life and flow.
@RickStrahl I'm pretty sure it's the second problem: you have two IRawString interfaces. One is unused at the moment, but it's probably getting used in the screenshot that you shared. It's also declared outside of a namespace which is probably a mistake.
https://t.co/a336gsGBzX
@RickStrahl I checked out https://t.co/jxO4gvCihX and your code sample in your screenshot does not repro the issue. I'm assuming that in the progress of work, RawString is either not implementing IRawString, or is not implementing _the same_ IRawString.
@RickStrahl What type does RawString.Raw return? All interface casts are allowed even if the class doesn't implement the interface, but that squiggle under "as IRawString" looks like ReSharper's "suspicious cast" warning, when you're casting to an interface that isn't currently implemented.
We merged a C# 14 feature into VS 17.13 (preview 2): Unbound generic types in `nameof`.
For example, it allows `nameof(List<>)`.
Spec: https://t.co/G0Tx2zAm1v
Have you ever run 'dotnet nuget why' and gotten a ridiculous or impossible amount of output to wade through? Would you be interested in a --depth parameter, or something similar?
https://t.co/b2WXI3recO