Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Developers are not happy with .NET MAUI, but nobody in the team cares about it

github.com

Post reply on HN
Print view View original

41–50 of 123 posts

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#41

Post by cristeigabriel »

jiggawatts wrote: post #5

Three decades of experience talking here: If you don't see a vendor like Microsoft using a GUI framework for at least 50% of their new applications, then you've made a terrible mistake in adopting it yourself. Microsoft uses Google's framework for their own applications: Electron. Yes, you heard me right. Microsoft, a nearly 3 trillion dollar company, uses the framework of a competitor for their own desktop applicati…

> Teams: Electron.

Not as simple with Preview versions on Windows. I don't think they use Electron whatsoever anymore, and old versions weren't fully Electron either (I remember seeing Chakra [their old JS engine] in the stacktraces, doing some elementary logic), I think it's XAML with UWP + WebView2.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#42

Post by thenerdhead »

Title should be "Developer yells at .NET MAUI team and expects to talk to the manager because their bug hasn't been fixed in two years".

I hope people can see the hostile working conditions that many in open source have to experience daily. There is no possible way for a small team to scale with the thousands of issues they get and give every single one the same amount of attention. That is why it is so important for people to upvote and engage in issues. It gives the product and engineering teams a way to gauge priority.

There are much better ways to go about ranting about product defects though. Doing it in this way just encourages people to pitchfork. We all know that pitchforking isn't productive at all. In fact, it hurts more than you think it helps.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#43

Post by xrd »

I tried to use the MSTeams API in the last year. It (the example GitHub repo) was obviously basically abandoned by MS except for some third world subcontractors that I'm sure a PM at Microsoft was managing while she managed her 401k and coasting into retirement. What a mess.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#44

Post by rightbyte »

thenerdhead wrote: post #42

Title should be "Developer yells at .NET MAUI team and expects to talk to the manager because their bug hasn't been fixed in two years". I hope people can see the hostile working conditions that many in open source have to experience daily. There is no possible way for a small team to scale with the thousands of issues they get and give every single one the same amount of attention. That is why it is so important for…

Oh it is very much possible to scale. Just drop the agile process, give the devs agency and fix the bugs.

Easely like 100x the efficiency fixing small bugs.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#45

Post by my123 »

hhh wrote: post #35
Ecstatify wrote: post #24

We decommissioned all our mobile apps built with Xamarin. Some of the Microsoft teams don't listen to user feedback. We use Azure DevOps, feedback from years ago for basic features still not developed. https://developercommunity.visualstudio.com/AzureDevOps

MS running two major code repo platforms, one that is hated, and one that’s widely loved, leads me to believe ADO is not going to make it.

Azure DevOps gets wide internal use at least: Windows source code is hosted on it.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#46

Post by Mountain_Skies »

Glad I dodged that bullet. I really wanted to build a portfolio project with MAUI to have something cross-platform but was already wary because of Microsoft's non-stop parade of overlapping, half working, UI frameworks. I experimented with MAUI for a couple of days but kept running into issues on the most basic of things, only to find out it was a known issue that had been left unaddressed for an extended period of time.

From the outside, it seems crazy that a multi-trillion dollar company would put out a product this broken and leave it that way for a long time but anyone familiar with the internal workings of Microsoft sees this as another case of a team having lost some insider battle and banished to nether reaches of the company, starved of anything more than token resources, to slowly decay to death.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#47

Post by deafpolygon »

rightbyte wrote: post #44
thenerdhead wrote: post #42

Title should be "Developer yells at .NET MAUI team and expects to talk to the manager because their bug hasn't been fixed in two years". I hope people can see the hostile working conditions that many in open source have to experience daily. There is no possible way for a small team to scale with the thousands of issues they get and give every single one the same amount of attention. That is why it is so important for…

Oh it is very much possible to scale. Just drop the agile process, give the devs agency and fix the bugs. Easely like 100x the efficiency fixing small bugs.

But 0x efficiency developing new features.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#48

Post by christophilus »

ChrisMarshallNY wrote: post #32
jiggawatts wrote: post #5

Three decades of experience talking here: If you don't see a vendor like Microsoft using a GUI framework for at least 50% of their new applications, then you've made a terrible mistake in adopting it yourself. Microsoft uses Google's framework for their own applications: Electron. Yes, you heard me right. Microsoft, a nearly 3 trillion dollar company, uses the framework of a competitor for their own desktop applicati…

I remember a similar argument against Visual SourceSafe[0]. We had been using SS since it was done by OneTree (borged by MS). MS used an internal tool, instead. VSS did do one cool trick, which I have yet to see replicated elsewhere: You could construct "artificial workspaces," composed of elements (down to individual files) in other workspaces, so, when you checked out (it was all checkout/checkin, back then), you a…

Is git worktree close enough? In the past, I’ve used it roughly the way you describe.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#49

Post by ecshafer »

hu3 wrote: post #18
MyFirstSass wrote: post #8

Earlier quoted context omitted.

This is bizarre to me. What applications are they actually using the framework for? Is it because it's easier to make cross platform? Reminds a bit of when i used Angular back in the day and it seemed Google of all people didn't use it for any of their many web services.

Angular is prime example. From my consulting experience, Angular (Google tech), is most used today along with .NET backends (Microsoft tech). I don't think I ever saw a client using Angular + Go, for example.

Ive seen angular with c#, java, python and node backends. Angular though is mostly popular with big enterprise non tech companies, more industry differences than tech differences.

Re: Developers are not happy with .NET MAUI, but nobody in the team cares about it

#50

Post by MrGilbert »

thenerdhead wrote: post #42

Title should be "Developer yells at .NET MAUI team and expects to talk to the manager because their bug hasn't been fixed in two years". I hope people can see the hostile working conditions that many in open source have to experience daily. There is no possible way for a small team to scale with the thousands of issues they get and give every single one the same amount of attention. That is why it is so important for…

I agree that it is usually useless to rant about an issue in the first place.

In this case, I can see that they were really neutral and understanding in the very first issue. After two years with little to no progress, I'd say it is natural to vent. Especially if they cannot get out of the situation they are in.

It looks like the original poster needs to use MAUI in their production environment. So they are already dependent on it. Which is to be expected, because MAUI already comes with a go-live license.

Also, I'd like to point out that this is not the pet-peeve of a small indie team. It is the future UI framework of a multi-billion company. If the team is understaffed, there should be something done about. The resources should be available in this case.

Post reply on HN