Mike James

@wieslawsoltes @ScoutMW @jinekLESNIK TreeDataGrid was almost exclusively developed by Steven (88% of all LOCs). If we look at all @AvaloniaUI staff contributions, they account for 92.1% of the code. Yes, you contributed some code, but let's not pretend you were the driving force behind this component.

@ScoutMW @jinekLESNIK And here where they took OSS library to commercial product and I was contributing too github.com/wieslawsoltes/…

The end of OSS for Avalonia is here #discussioncomment-16222358" target="_blank" rel="nofollow noopener">github.com/AvaloniaUI/Ava… beware, time to find new UI framework I guess

@wieslawsoltes @ScoutMW @jinekLESNIK It's been explained countless times what happened. It was a side effect of leaving the .NET Foundation. We tried repeatedly to sort it out with you, but you didn't engage.

@ScoutMW @jinekLESNIK I was removed from Avalonia UI organization without any notice and lost access to my owner repositories, who is badly looking here

@wieslawsoltes @kekekeks Understood. The repository is archived. Thank you for contributing it to the project back in 2022. It served the community well.

@MikeCodesDotNET @kekekeks I have forked my repo long time ago, you can archive

@wieslawsoltes @kekekeks I've removed the link from our website and updated the DNS record to point to our docs. Would you like me to transfer the repo to you? Otherwise, I'll archive it.

@MikeCodesDotNET @kekekeks I know when it was developed, as I did it , do with it whatever you want

@wieslawsoltes @kekekeks The playground isn't used for any commercial purposes. The playground was also developed in early 2022, months before ChatGPT was even released. If you'd like, I'll be happy to remove it.

@kekekeks yes you keep using my AI slop on you commercial project play.avaloniaui.net #L3" target="_blank" rel="nofollow noopener">github.com/AvaloniaUI/Xam…

@wieslawsoltes @Kruwed The first commit to our MAUI backend was in Sept. We announced at .NET Conf as planned from the outset.

@MikeCodesDotNET @Kruwed No I am just showing timeline of events. Nothing else.

@wieslawsoltes @Kruwed I'm not sure what you're trying to show here. Are you suggesting we created the MAUI backend in a few days as a direct response to your tweet?

@MikeCodesDotNET @Kruwed

@wieslawsoltes @Kruwed We announced our MAUI backend to line up with .NET conf, after several months of development.

@MikeCodesDotNET @Kruwed Very big coincident isn't

@wieslawsoltes @Kruwed We're about to ship v12, which is entirely open-source. Last week, we released the MAUI backend as FOSS and made one of our commercial components open-source as well. The idea that we only focus on the commercial side simply doesn't hold up.

@Kruwed They don't share roadmap, they focus only on commercial part, contributing to it is basically pointless, the remove many parts like dev tools a critical part and make it commercial and so on, data grid is basically useless. Had to fork many libraries to even keep development.

@Kruwed @wieslawsoltes All contributions must meet our quality bar, which includes proper testing and validation, especially for changes that affect the rendering pipeline. A PR opened 1 month before a major release that changes fundamental behaviour isn't something we'll ever rush to merge.

@Kruwed @wieslawsoltes It's not the end of OSS for Avalonia; your PR just hadn't been reviewed yet. We're busy working on shipping v12. Avalonia remains open-source, and we continue to use our existing PR review process.

@Aaronontheweb The dotnet subreddit rule is utterly moronic IMO. I’ve stopped posting content because I don’t want to have it deleted as self-promotion. Thankfully, it looks like our community is sharing the news instead, but the rule change just makes creators engage less.

Adjacent point: not a lot of good places to share things you're doing any more. - Reddit aggressively penalizes self-promotion in most subs - X / LinkedIn downboost and penalize posts with links - SEO generally revolves more around link authority and smaller sites suffer

Huge kudos to Tim and Javier, whose work made this happen. Supporting the broader .NET ecosystem through initiatives like this is a great example of what we’re building Avalonia to do. A stronger ecosystem benefits everyone.

It was a really interesting conversation! At some point I’ll share more about why I think the term ‘native’ is meaningless 😬

I wanted to see how difficult it would be to update MonoDevelop to use Avalonia. Turns out, it's easier than I imagined! Hugely boosted by using @Actipro, NetCoreDbg, and the existing code we've written for Accelerate.

@manunumanux @AvaloniaUI @OpenRouter Not yet. I’ll make it available once I’ve finished adding all the features I’ve got planned.

@MikeCodesDotNET @AvaloniaUI @OpenRouter Nice! It’s available somewhere ?

I've been building an AI chess coach using @AvaloniaUI, powered by @OpenRouter. I can swap between different LLMs for gameplay and coaching advice, and it's already helping me improve!

This was a ton of fun. I spent more time tweaking the banner animation than anything else! It's wild how productive you can be when you lean into the tools available today.

@edandersen @fjzeit @robmen For context, I had a large ($65B in revenue) company want to buy ~€5K worth of product from us. They sent over a 3 page procurement form, with 90+ questions. To complete would have meant writing, publishing and maintaining bespoke policies just for them. I refused the sale.

@edandersen @fjzeit @robmen I’d be surprised if any maintainers will jump through procurement hoops for the tiny amount the maintainer fee generates. I already refuse lengthy vendor onboarding if it’s not a 5 figure deal. I can’t imagine doing it for $50 a year!

PSA: json-everything went commercial with 2 weeks notice. I don't mind supporting OSS but it needs to be months of notice not a 2 week rug pull. We'll be building from source. 9.0.0 nuget = new EULA. 8.0.5 = old. @robmen this gives the Open Source Maint. Fee a seriously bad rep

@edandersen @fjzeit @robmen Just had a read of the maintenance fee website. The recommendation is to use GitHub sponsorships. In that case, the invoice is raised by GitHub, which means the procurement should be treating GitHub as the vendor and not the maintainer.

@fjzeit @robmen Literally could not sponsor this guys project without running sanctions checks on his name. Stripe as an intermediary doesn't make a difference