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

51–60 of 123 posts

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

#51

Post by ChrisMarshallNY »

christophilus wrote: post #48
ChrisMarshallNY wrote: post #32

Earlier quoted context omitted.

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.

I don't think I've tried that.

Thanks for the heads-up.

[UPDATE] Ah. Now I remember [0]

It does roughly that, but it still insists on bringing in the entire repo (as does all Git).

The thing that SS did, was allow you to create a "chimera" workspace, composed of just tiny parts of other workspaces.

It was a great way to share sample and SDK stuff, without, for example, sending over a ton of testing code.

Many of my repos have more testing code than implementation code; not to mention a ton of documentation.

[0] https://git-scm.com/docs/git-worktree

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

#52

Post by malodyets »

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…

Svn externals provide similar capabilities, though I don’t remember if an external can be an individual file. TortoiseSvn on windows made it not to painful to use.

https://svnbook.red-bean.com/en/1.7/svn.advanced.externals.h...

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

#53

Post by MrGilbert »

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.

Dev with agency here. There is clearly an issue, but "agile" is not it. "Agile" doesn’t mean "ship unfinished products and never care for issues".

In fact, it means quite the opposite: Start with as little as possible, as polished as possible and improve from there. It's actually quite nice to work with, if every role is on the same page.

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

#54

Post by rightbyte »

deafpolygon wrote: post #47
rightbyte wrote: post #44

Earlier quoted context omitted.

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.

That is debatable.

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

#55

Post by thenerdhead »

MrGilbert wrote: post #50
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 d…

The latter part should really be looked closer at. You cannot simply attach a company’s market capitalization to how funded a team actually is. People constantly overlook that. That’s true at many big tech companies too. The assumption harms just as much as pitchforking.

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

#56

Post by jwells89 »

WoodenChair wrote: post #33

We tried building a greenfield mobile app using Maui because my development partner is a Microsoft tools aficionado. We ran into a big memory leak that was so hard to debug using the primitive tools that it set us back a month. Eventually, we discovered it was internal to Maui (leak caused by a Maui component, not our code) and decided to program native apps instead for the project. Ultimately I think rebuilding as n…

It’s counterintuitive, but yes, depending on the project cross-platform frameworks can actually be harder for small teams or one-person operations to manage well because they increase the number of layers in which bugs and quirks can show up in — instead of just e.g. Mac AppKit and Windows Win32 bugs, you’ve now got to deal with those plus whatever bugs the cross platform framework has.

This is particularly true for projects where the UI is not overly complex (and thus, not where most of your energy is going), in which case it can make more sense to do code sharing in a library that’s pure business logic (no UI) and platform independent.

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

#57

Post by lopatin »

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 think the developer is justified in his self-described rant. He has gone through other channels and engaged with the project leaders directly. He has waited years for the bugs to be addressed.

Microsoft is in the wrong here for selling this as the future and not dedicating the resources necessary to fulfill that promise.

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

#58

Post by lawgimenez »

npteljes wrote: post #39
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 completely agree. Evaluating a decision like this, one needs to look at it from a business perspective, in order to reach the correct conclusion. Looking at it like this, what I cannot see is Microsoft's commitment to this technology. Instead, we see a consistent commitment to an alternative technology, even if historical reasons also take place.

Not long ago someone from Maui posted here about the “momentum” within Microsoft.

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

#59

Post by [deleted] »

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…

[deleted]

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

#60

Post by biorach »

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…

This is not a typical open source project. The developers are all Microsoft employees who, in theory, are paid to work on MAUI
Post reply on HN