It’s like going to a mathematics forum and declaring “Guyz I forgot to carry a 1, screw Maths.

You may think you’re joking, but as a Maths teacher I can tell you I have seen a lot of posts where someone makes a mistake with their signs, then uses their wrong answer to declare “The rules of Maths are wrong! Look - different answer!”. Yeah umm, try working on getting your arithmetic right first before claiming to have “proved” something. 😂

Personally, I dislike the way the UI is declared and bound though (XAML)

You can write the MAUI UI in C#. No need to use XAML anywhere.

Creating MAUI UI’s in C#

He works at Microsoft

@[email protected] @[email protected]

The rules and the acronyms describe different things.

No, they don’t.

If you have to make more rules to say M and D are the same,

I didn’t make more rules - that’s the existing rules. Here’s one of many graphics on the topic which are easy to find on the internet…

…that’s one of the two examples you used?

Yes. Did you try looking for one and ramping it up to the most difficult level? I’m guessing not.

IT IS AMBIGUOUS IN THIS POST

No, it isn’t. Division before subtraction, always.

ALL EXAMPLES I HAVE SHOWN

None of those have been ambiguous either, as I have pointed out.

That is the problem at hand.

The problem is people not obeying the rules of Maths.

There is no real problem solving in trying to decipher poorly written shit

It’s not poorly written. It’s written the exact way you’d find it in any Maths textbook.

You are adding more rules

I’m stating the existing rules.

If all that matters is higher orders first

I don’t even know what you mean by that. We have the acronyms as a reminder of the rules, as I already said.

I know operators apply to the numbers to their right.

If you know that then how did you get 2-2+2=-2?

With 2/22, you don’t know if it is 22/2, or 2/(2*2)

Yes you do - left associativity. i.e. there’s no brackets.

When you are dividing by numbers, you put them all in the denominator

Only the first term following a division goes in the denominator - left associativity.

BY CONVENTION, as I said. You don’t have to repeat what I said a second time.

I didn’t. You said it was a convention, and I corrected you that it’s a rule.

It’s not like you could have tried in your head different orders to combine 3 numbers.

addition first

2-2+2=4-2=2

subtraction first

2-2+2=-2+2+2=-2+4=2

left to right

2-2+2=0+2=2

3 different orders, all the same answer

Who’s on first? :-)

Still not quite sure what the different design ideas behind Xamarin and Maui is

Xamarin had separate projects for each platform, whereas they’re all together in MAUI. Also Xamarin was tied to .NET Standard 2.1, whereas MAUI uses the latest .NET releases (starting with 5 or 6 - I’m now on 8). MAUI major releases now come out at the same time as Visual Studio updates. Also, as mentioned, MAUI uses handlers, but I’m still trying to work out how you actually use one to create a property (sigh). There was a few, annoying, breaking changes too. e.g. in Xamarin I could define the span and height of an element in a Grid with a single command, but now I have to use two (for some bizarre reason setting the column span is now entirely separate. I ended up writing my own function so I could do it all in 1 line again).

I had someone say that to me, a Maths teacher, when I was trying to tell them where they were going wrong with their Maths! 😂And they were a programmer - no wonder all the e-calcs are wrong… (sigh)

Multiplication comes before division in some forms, like PEMDAS. In the example I use, this changes the answer

If you have both multiplication and division then you do them left to right. PEMDAS doesn’t mean multiplication first, nor does BEDMAS mean division first. It’s PE(MD)(AS) and BE(DM)(AS) where the bracketed parts are done left to right.

you should specify what it is operating on

Left associativity means it always operates on the following term. i.e. terms are associated with the sign on their left.

The minus sign only applies to the middle term, by convention

By the rule of left associativity.

But if you use one of these acronyms, you end with this expression evaluating to -2

No it doesn’t. How on Earth did you manage to get -2?

all these acronyms end up being useless waste of time

No they’re not, but I don’t know yet where you’re going wrong with them without seeing your working out.

Even your “BODMAS” isn’t universal, lots of people learn “PEMDAS” or “BEDMAS”

The rules are universal, only the mnemonics used to remember the rules are different

except for facebook and twitter

… and high school Maths textbooks, and order of operations worksheet generators, and…

2/2*2 It is 0.5 or 2 depending on order.

It’s always 2. #MathsIsNeverAmbiguous

No, it isn’t. Division before subtraction.

1/2x is also unambiguous. 2a=(2xa) by definition. Has done for at least 180 years. Terms

Nothing wrong with the way it’s written - division before subtraction.

And a bunch of those bugs are for shell, which nobody wants anyway, but for some unknown reason they want people to use it. And newbies don’t know the difference and will raise an issue for “shell” when in actual fact it’s not an issue with shell but with the root MAUI control. The bug I mentioned before about ToolbarItems was initially raised as being a bug in shell, but the bug is actually in ToolbarItems. They should just kill off shell and focus on fixing the actual MAUI bugs.

Well, it depends how you want to look at it. The TL;DR is the number of outstanding bugs has grown.

I remember in the early MAUI days when people were commenting about there being 2000 open issues - there’s now nearly 3,500 open issues. A lot of issues have been closed - there was a period where several I was waiting for got fixed - but even more new ones are getting reported as people transition from Xamarin. A lot of them aren’t “reliability bugs” in the sense that it makes the app crash, but there’s a whole bunch more missing functionality.

Quite frankly I’m surprised they sunsetted Xamarin as planned. All along I was thinking “there’s no way that’s gonna happen on that date with this amount of bugs still open”, but yep, they went ahead and did it anyway. If it were up to me I’d still be using Xamarin, but I don’t have that choice (hence starting up this community to try and reassemble everyone from the Xamarin forum days, and let’s get to helping each other out with our bugs and workarounds - I already got 1 solution to a problem from someone here).

To give an idea of the missing functionality (which was working in Xamarin) you still can’t bind to properties in your ToolbarItems, cause there’s no properties there to bind to! The issue for that is now 2 years old. We were told that we can use handlers for that, but there’s no documentation on how to do that (I raised an issue for that too a few weeks ago). As I said, that’s not one that causes your app to crash, but you still can’t do what you could do in Xamarin yet, so the ToolbarItems look out of place with the rest of your app. FlyoutMenu still has issues too.

“The improvements they’ve incorporated into .NET MAUI indicate that it’s more reliable than Xamarin”

BWAHAHAHA! 🤣🤣🤣 😡😡😡 I don’t know who this guy is, but he doesn’t seem to know much about MAUI/Xamarin other than a blurb someone has given him.

It is just that here, in this situation, I didn’t get it

I scrolled back to see, and I think that initial one was just someone who disagreed with your suggestion, for whatever reason (like I downvote incorrect responses to order of operations questions. i.e. hearsay which contradicts what’s actually in textbooks and taught), but then yeah, there was some piling on when you asked for an explanation, and I just write them off as “I don’t want to see this” types. At first it bothered me, but in the end I just take out of it that I got more upvotes than downvotes, so just proceed with business as usual then. :-)

Remember the human, and all of that

Yeah, there’s some keyboard-warriors who forget that. You learn to just ignore the downvoters unless, like in your situation, you’d like an explanation as to why your particular suggestion was downvoted by someone. e.g. maybe they know something that you don’t. There was a whole side-discussion about Kagi like that (someone had seen something on a blog, and someone else pointed out the CEO’s response to the blog, etc. - I didn’t read the whole thing… but I didn’t downvote it either ;-) ).

I can’t even recall the last time I downvoted something

I’ve downvoted things which I know are wrong (people love expressing opinions on things they have no expertise on - just check out the threads on order of operations! 😂), and upvote correct things (the whole point to up/downvote is to push relevant things to the top), otherwise neither usually. Sometimes I use upvote to indicate I liked something someone said.

just seems so… lazy

Yep.