@mattpocockuk Why do you tend to favour state-update-based architectures like Flux/MVU over signal-based reactivity? I know there’s no silver bullet, but I find the explicit, imperative style of signals quite intuitive. What trade-offs make you prefer Flux/MVU?
@StevenTCramer@stephentoub Jakby wybrał assemblera to też byś miał ból dupy czy przeszedłbys obok tego obojętnie? W jakim stopniu wybory innych odnoszą się do twoich caseow ? Skreslasz js mimo że istnieją szybsze języki?
@AntonMartyniuk@kristijan_kralj Your reaction is hilarious. :D
That’s why I’m moving away from .NET. This should be as natural as breathing.
How much time will you waste, and how many times will you reach for the mouse?
@SIRHAMY I see your road. I'm trying to move from C#, TS, and F# to Roc—you should check it out too, I'm very curious about your reaction. Start on YouTube with @rtfeldman.
@Dave_DotNet F# and C# DX in VSCode needs to improve:
- LSP needs restart lsp
- Go to Definition should work deeper, like in Visual Studio
- Jupyter Notebook support + syntax colorize
- WASI compilation
These would make the .NET experience in VS Code much better.
AD2026 - AI, Space, Foldable Phones and...
VS Code + C# + required VS Pro license
+ Go to Definition =
"No definition found for …"
F# is even worse...
@dotnet@code
Really? Why?
(It works correctly in VS)
I really have no patience left...
What are you doing right now?
AD2026 - AI, Space, Foldable Phones and...
VS Code + C# + required VS Pro license
+ Go to Definition =
"No definition found for …"
F# is even worse...
@dotnet@code
Really? Why?
(It works correctly in VS)
I really have no patience left...
What are you doing right now?
AD2026 - AI, Space, Foldable Phones and...
VS Code + C# + required VS Pro license
+ Go to Definition =
"No definition found for …"
F# is even worse...
@dotnet@code
Really? Why?
(It works correctly in VS)
I really have no patience left...
What are you doing right now?