Mike James

@AvaloniaUI. Formerly @Microsoft + @XamarinHQ. Views are my own, as are the ViewModels. Neurodiverse | Him/He

[Mike James @MikeCodesDotNET]

There is something incredibly special about Techorama!

What @gillcleeren and the team have created is truly unique ❤️🔥

[Avalonia UI @AvaloniaUI]

The team successfully conquered @TechoramaNL Medieval Edition, talking cross-platform .NET development and crowning plenty of new developers at the booth.

Huge thanks to everyone who stopped by to chat 👑 🏰

#Techorama #AvaloniaUI #DotNet

[Avalonia UI @AvaloniaUI]

Building apps with Avalonia is about to get a whole lot easier.

#dotnet #AvaloniaUI

[Mike James @MikeCodesDotNET]

@James_M_South Take a break and remember that arguing with folks spreading nonsense will only waste your time.

Many developers are entitled. I recently spent the day poking at an entitled dev, but it just went in circles.

They won't admit entitlement, but it's precisely what it is...

[Mike James @MikeCodesDotNET]

@jsuarezruiz @awakecoding I’m using it for my memry app, and it’s great! ❤️

[Mike James @MikeCodesDotNET]

@Ikryanov @AvaloniaUI Fixed. Was an easy one to solve.

[Mike James @MikeCodesDotNET]

Can you tell this isn't a native Mac app?

It's Avalonia. I spent a few days seeing how close I could get to a SwiftUI macOS feel, and I think it's pretty damn close.

Mac users, I'd love your honest verdict.
https://t.co/M51bTkVJEw

[Mike James @MikeCodesDotNET]

@Ikryanov @AvaloniaUI Looks like the screen recording software lagging on the replacement cursor animation. Unless you’re pointing out something else other than the hover state looking like it’s activated early?

[Mike James @MikeCodesDotNET]

@fexdev @AvaloniaUI Not sure what we’ll do with it yet. It might become a sample app.

[Mike James @MikeCodesDotNET]

@Aguilar_2077 @AvaloniaUI Its named Memry but only because I needed a name for the solution 🫣

[Mike James @MikeCodesDotNET]

@awakecoding @unixterminal @burkeholland I’m adding this format to my repertoire! 😂

[Mike James @MikeCodesDotNET]

@ICooper I welcome this! Long form will be a much better format.

My interest isn’t in catching you out. I’m trying to understand how the principles you’re invoking actually produce the very strong conclusions you’ve reached.

A written argument would be much easier to analyse fairly.

[Mike James @MikeCodesDotNET]

@ICooper @Aaronontheweb If sufficiently serious maintainer harm can outweigh fidelity, say that.

But we have to be able to test the principle against both cases.

[Mike James @MikeCodesDotNET]

@ICooper @Aaronontheweb You can’t refuse the counterfactual because you disagree with its stipulated outcome, then claim the principle passes the reasonable-rejection test.

If fidelity always defeats the maintainer’s objection, say that.

[Mike James @MikeCodesDotNET]

@ICooper @Aaronontheweb If you now want to say that where maintainer harm is genuinely greater, the maintainer’s objection wins, then say that.

But that’s a different answer…

[Mike James @MikeCodesDotNET]

@ICooper @Aaronontheweb You answered: “Still the consumer, because you broke the principle of fidelity.”

So under a hypothetical in which maintainer harm is greater, you still give the consumer priority because of fidelity.

That’s not my characterisation of your position. That’s the answer you gave.

[Mike James @MikeCodesDotNET]

@ICooper @Aaronontheweb And it means we’re back to the question I’ve been asking from the beginning: why can’t the maintainer reasonably reject a principle that gives that promise such overriding force over their future choices?

[Mike James @MikeCodesDotNET]

@ICooper @Aaronontheweb So comparative harm isn’t actually determining the outcome.

The consumer’s objection has priority because you believe publishing OSS creates a promise of fidelity that overrides the maintainer’s greater harm.

That’s a much clearer statement of your position.