You can upvote this comment if you want them to provide a proper setting instead of having to edit the registry.
It’s NOT off by default. It’s on/off according to the setting you have for “Receive updates for other Microsoft products. Get Microsoft Office and other updates together with Windows updates”. If you have that on, then auto VS-updating will ALSO be on. The controversy is no developers want auto-VS updating on, even if they DO have that other setting on. Auto-updating Office and auto-updating VS aren’t the same thing at all. I for one never update Windows and VS at the same time, because if something breaks in your app, then how do you know which update broke it if you did them at the same time?
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.
He works at Microsoft
Hmmm, I got around it (eventually), but it wasn’t through any of the methods mentioned - don’t remember what I did. Very annoying as I hate 11 so much I was actually going to roll back to 10 this week, now I’m worried if I do that then when I eventually have to come back to 11 I’ll be stuck with having to use my MS account for it.
I’ve never used 8, but I liked 10. I especially liked the built-in anti-virus - there was noticeable performance improvement once I got rid of the 3rd party stuff. Absolutely hate 11 though - I’m planning on rolling back soon.
Yeah, the last time I posted about AI stuff I got my first-ever negative net votes here, but it was news and I posted it. Same here. Alvin Ashcraft also posted a link to it, and I said to him that from what I’ve seen so far, this isn’t going to work out any better for them than it did last time. Maybe next time they might learn to ask developers first, BEFORE saying “Hey developers - we need you!”.
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
Apparently someone did, and the ensuing chorus of “No, we don’t want that!” is being ignored.