The number of people in this thread not understanding the importance of not having any interference in live visuals makes me believe this won’t be fixed by Apple. Absolutely baffling.
(I'm assuming Apple still makes an effort for this segment, but I really have no idea how they do things these days.)
EDIT: As far as I know, the best long-term answer here is for apps that present visuals full screen to "capture" the external display for exclusive use using an API (https://developer.apple.com/documentation/coregraphics/14562...), but that's not super common right now.
It's not a complicated situation to grasp and it is seriously significant.
Yes, so you can go to the software vendor's "Ideas" or "Suggestions" page and ask for this, and post in forums asking people to upvote it, and hope the devs will do it. Not a great workaround. And sure, someone developed a script to get rid of this but no one is all that happy when Windows does something user-unfriendly that only a regedit hack will get rid of either.
I think they could do a better job (e.g., a simple setting in System Preferences that turns off recording notifications), but to pretend that they're doing this for no reason at all or that the orange dot is a show-stopper for a significant fraction of their user-base is just not making an argument in good faith.
Is anyone doing that...?
Well, look at the other person who replied to my comment:
"Every time this happens a small minority that is affected screams "this is interfering with my workflow" and the majority says "get over it"."
That's not technically untrue, but it fails to acknowledge that there is a tradeoff here. Again, I think Apple could be doing a better job of managing the tradeoffs, but this is not simply the majority saying "get over it". This is the majority saying "it sucks that this change interrupted your workflow, but look at the bigger picture"
It's getting safer and safer if all you want to do is watch Netflix and check your emails, but it's getting harder and harder to get your work done.
Every time this happens a small minority that is affected screams "this is interfering with my workflow" and the majority says "get over it".
As Apple keeps doing this, eventually they are going to break something you rely on.
I'm very much not surprised at saving the wrong pennies.
It doesn't have to be an all or nothing situation if Apple is even remotely interested in addressing this use case, which they should be.
I think the reality is that the set of people who want the feature and who would use it in a live professional environment with expensive hardware and who can't afford a $100 dongle from BlackMagic is so close to the null set that Apple is unlikely to care.
For goodness sake, Apple's own HDMI dongle costs $70. Just spend $30 more and buy the BM one instead.
I used to be.
> It's also a false choice
Yes, yes it is. It's been like this for decades. Entertainers are expected to buy the most expensive hardware available even when they're just getting started. Conform or be stigmatized for using inferior technology. We're talking about an industry in which AudioQuest has no trouble selling passive 3m HDMI cables for upwards of $1k.
Maybe this is the first time Apple has stepped on your toes, but it won't be the last. Be prepared to fork over the cash for a specialized dongle you wouldn't need on any other platform, lest that orange dot mar your reputation.
Let's be real: this isn't going to harm Apple's sales in the slightest, and they know it. The only way they could possibly harm their reputation in the entertainment industry is by lowering their prices, opening up their ecosystem, and eliminating $1k monitor stands.
They know you'll ultimately cough up the dough for an adapter, no matter how much you complain. They know you don't have a choice. They get money from me, a privacy-conscious end user with a choice, and they get money from you, a disgruntled professional without a choice.
It's not necessary to force that choice.
How is offering an option for it to ONLY be visible when the menu bar is also visible compromising the notification in any way?
There are software solutions like NDI that the hardware solution doesn't fix and why should I have to buy hardware to fix a problem that should have never existed in the first place?
It's asinine and really not that complicated - don't show UI shit on displays that aren't showing the menu bar. There is always one display that must have a menu bar - show crap like this there and only there.
Yes, there are workarounds. But artists shouldn't have to deal with that when it worked perfectly fine beforehand. In addition, the more stuff you add to your setup, the higher chance that something will go wrong.
The right call her for Apple is to allow users to give permission to specific apps to disable this but let's not start with the idea that pros are outputting directly from their computers without the right hardware.
Have you ever worked in this industry? Because yes they absolutely are.
The people building the video walls (renting them), and the people actually running the visuals are not the same people.
All anyone in this thread is implying is that, if this is important to you, you need to have the hardware to do it. If Microsoft tomorrow decided to put a Windows logo in the corner of the screen just to say "fuck you", you would still be unaffected with a hardware I/O device.
And without the orange dot issue, it wasn't necessary to have absolute perfect control. (Which could still go wrong anyway, because it's a computer.) Making it necessary all of a sudden is bad.
Or to put it another way, even without a hardware controller it was possible to have your macbook's use of an external output be one of the strongest links in the chain. Which is enough. Was enough.
Not if you need to be able to decide was is and isn't displayed. The I/O subsystem on Monterey is almost exactly the same as it has been since like Mavericks. If it was enough in the past because people were lucky, then that's awesome. There are ways to deal with the dot if people want to continue running these setups off of luck and ignorance. I'm only arguing against the people that say the dot makes their setup "unusable" and somehow ruins their livelihood.
> Just turn off whatever recording device is active
It seems you haven't considered that the most obvious scenario someone would be annoyed about this is during a multimedia presentation when they're running both a video output and recording audio over top, an extremely common use-case that performers I personally know take part in. Suggesting this clearly non-technical individual to turn off SIP and compile and run some arbitrary code from Github is laughable to me.
They're not, though. I only used notifications and the like because they were common things that people probably have experienced outside of this specific situation. It doesn't have to be that. It could have been a microphone icon or a speaker icon or literally whatever the OS wants to display. And I'm not even arguing that it's unreasonable to complain about the recording indicator. I'm arguing that people who claim that something being on screen that they didn't want makes their workflow "unusable". If that was the case, there are solutions for that and they've been around for years. Just because they weren't affected by their ignorance in the past doesn't excuse that.
>clearly non-technical individual
If this person is that non-technical, then something like this is definitely not a showstopper that makes it "unusable". They are not the people I'm directing these comments at.
Doesn't fix the orange dot, but it helps pretty much everything else.
Helps but doesn't solve. There is nothing that you can do to remove the OS's ability to put things on a secondary display outside of your control. The only option is to have a separate I/O controller.
Most will be using HDMI out as a second screen, so those won't show up
> Yes. I currently work in this industry
What do you use for video output? I'm a hobbyist and used iPad & TouchViz with HDMI plug. I just picked up Resolume and planned to use a Mac Mini M1 w/ Monterey and HDMI out. I'm livestreaming, so I'm only doing 1080.
To have this be a business blocker, they clearly not only don't have any other standard tools available to prevent this display issue, but they also upgraded their OS, can't roll back to an earlier backup (probably don't have backups), and did all this on the machine used for the presentations, without any alternatives.
That's a shocking lack of care and they deserve to receive flack for it. You test that kind of thing well before the event, and then you do not touch anything. Least of all upgrading the OS. I can't help but assume that these people are just using their personal laptops and hoping for the best on the day of an event. If they are, a small orange dot is the least of their concerns, and serves as a nice canary to their employer.
And, again, we are talking about situations where this orange dot would make the function "unusable". Those situations are not situations where a professional uses the built-in I/O and leaves things to chance.
It sounds like there’s something about all of these responses that isn’t resonating with you because I see a pattern of responding and letting us know our experiences are essentially invalid, for some reason. Are you able to speak to why that’s important to you? Why does this seem so far-fetched / unbelievable to you?
Someone spends a thousand, or two thousand dollars on a high-end device with state-of-the-art ports and graphics and processing, and because "OS notifications sometimes pop up if you don't disable them", real pros buy a piece of middleware hardware that does nothing but filter out a software issue?
OS notifications and alerts are just examples of any number of things that could be displayed that are unwanted. In situations where something like that makes the setup "unusable", you have to have a hardware I/O device. There's not another option.
If the dot makes their setup unusable, then the situation prior to Monterey should also have made their setup unusable because the OS could have popped up an alert dialog at any time (or any kind of OS chrome). Using built-in I/O is absolutely fine in professional settings but not for settings where you need complete control of what's being displayed and that's precisely what they're complaining about. They never had completely control of what was being displayed. They were just OK with it because it either didn't bother them often or it wasn't a dealbreaker for whatever they were doing. If you need to know that you're only going to see what you want to see, you have to use hardware I/O.
I've never said anyone's experiences are invalid. Stop talking down to me like a child and making things up.
This seems to be the crux of the disagreement in this thread. You're equating the effect of two quite different things:
1. A pop-up that's quite intrusive / potentially embarassing, but has (say) a 1/100 chance of happening any given show, and in any case would only be there for a few seconds; the rest of the show would be unaffected
2. A small but intentionally noticeable orange dot that's there 100% of the show for every show
Yes, if you want to be a top level professional, then you can afford to have neither. But I can certainly imagine people / venues where #1 would be considered a normal cost of doing business, but #2 would not.
That said, if fixing them both is as easy and inexpensive as people in this thread seem to think, then the small "nudge" by #2 to get them to fix #1 is probably beneficial for the ecosystem overall.
You're mis-framing what I'm saying. The effect is the same. There is something on the display that is unwanted. Regardless of what that thing is, the issue at hand is that people do not want things that they didn't choose to be on the display to actually be on the display. It doesn't matter what that is. In this case, it's a small dot but it could have been a little microphone icon or a camera icon or (like Windows) an orange border around the display or literally anything else.
The fact that it didn't affect some people before is great. They were lucky that they didn't have this happen. All I'm saying is that, for years before this change in Monterey, there have been things that pop-up like this on external displays because external displays do not have the ability to prevent the OS from using a display as a display (with a couple exceptions when used with APIs for exclusivity). That's a known problem with using extended displays and it's been known for a while, regardless of the OS you're using. There's also a solution to that problem that's pretty standard in the presentation/production industry.
That being said... there are now multiple solutions for people that both don't break the intention behind this change (they're slightly technical solutions that most people won't do) and allow for app developers themselves to fix the problem (using the APIs already provided to get screen exclusivity).
It's easy to imagine a pretty wide range of people for whom a tiny theoretical risk of the OS going crazy and showing some kind of notification even with notifications disabled is acceptable, but an orange dot that's 100% deterministically guaranteed to be there isn't.
No they didn't. That's literally the entire point. Just because people don't know that or weren't affected by it regularly doesn't change that fact. People are focusing on things like notifications because that was the initial example that I used for ease of understanding but there are literally thousands of things that the OS can display, on any OS, on top of a full-screen window or by kicking the display out of full-screen. Even on Windows, Virtual DJ has has a full-screen mode and errors will kick you out of full-screen and pop-up on that display. All of that is avoidable with an I/O box.
The fact is that if you're not ok with the OS choosing what shows up on your screen, there are ways to do that and they've been industry standard for years.
Thanks for explaining, I hear what you are saying about dedicated hardware giving much more control. In the case of this dot and an external monitor / display, and until the OS is updated, that definitely sounds like a great option.
Perhaps I was misreading what you are saying; regarding:
> If the dot makes their setup unusable, then the situation prior to Monterey should also have made their setup unusable because the OS could have popped up an alert dialog at any time
It sounds like we are in disagreement around current un-usability because of (dot/notifications/etc) implying past un-usability. I get what you are saying in theory, and agree with you.
However, in my life experience, and many others in this thread, I am hearing counterexamples to this statement. The way in which I observed you responding to these statements is what invalidating _to me_. My felt experience is not "making things up".
I do not know your age and I am making no assumptions about that. The intention of my original comment was to: respectfully and kindly share the impact of how I have been receiving your comments, gain more understanding about your perspective on this issue, and offer an (obviously subjective) reflection to you about a communication pattern that I noticed in the comments here.
This sort of reflection is always coming from place of curiosity and so carries an implicit invitation to deepen into greater shared understanding and connection; I have no attachment to you receiving that reflection and I apologize if it did not land well for you. I understand these kind of things do not always translate so well in text.
I have never said that anyone was making anything up. Please do not put words into my mouth or make statements on my behalf when I have not said them.
>I apologize if it did not land well for you
This sounds like a abusive partner apologizing. "I'm sorry you made me so mad that I had to hit you"
>I am hearing counterexamples to this statement
You're not hearing counter-examples. You're hearing situations where the person, in the past, was lucky enough to not be affected by the situation they were in. That's great. It's like someone who refuses to wear their seatbelt telling someone that they never wear their seatbelt and they've never been injured even though they've driven 10000000 miles in that car. If reducing your chances of dying in a car wreck is important to you, you would have worn a seatbelt. This is like complaining that the car's seat belt chime wasn't insistent enough after you got into a wreck and are now paralyzed.
Nobody is attacking you here.
Yet, I experience your interactions here as carrying defensiveness and un-checked assumptions. That is my experience. That is different from me saying, “you are defensive.”
I am having an experience in this dialogue that feels in opposition to one of the main principles encouraged in this board, which is that of graciousness and good intent. I do not feel you have been reading my comments from that kind of orientation. Perhaps you have and I have misconstrued.
Regardless, I really don’t care enough about this issue to continue engaging with you about it like this.
Take care.
And you're right... I haven't been reading your comments from that kind of orientation because your very first comment to me claimed that I had somewhere let someone know that their experience was invalid, which I never did, or that I had somehow claimed that people's realized experiences were far-fetched, which I also never did. How can I assume graciousness and good intent from someone who didn't assume the same of me and then went out of their way to mis-frame what I have been saying? The only time I ever even suggested that something was far-fetched were the people who were claiming that something like this would affect productions like SNL or Mariah Carey on NYE because those are far-fetched suggestions.
That's fine not to continue but please don't pretend that I was the one that engaged with you "like this". You initiated the current conversation, including its tone and intent.
Take care. I hope the new year treats you well.
We don't want flamewars here. Please make your substantive points thoughtfully and without swipes in the future—regardless of how wrong other people are or you feel they are.
Btw, when discussion degenerates to the level of people arguing about what each other did or didn't say, that's a sure sign that the conversation has become tedious and uninteresting to those not involved in the spat, and that it's time to step away from the comment box.
You weren't the only person in the thread doing these things, but (from the subset I've seen), your account was behaving the worst, both qualitatively (in terms of how badly you were breaking the site guidelines) and quantitatively (in terms of how many posts you made and how much fuel you added to the flames).
Could you please review https://news.ycombinator.com/newsguidelines.html and take the intended spirit of this site more to heart from now on? I don't want to ban you, but if this keeps happening, we'll end up having to, because it's not what this site is for and it destroys what it is for.
Can you clarify where I broke the site guidelines? I don't believe that I've personally attacked anyone but that feels like a subjective measure so I'd like to be clear on what you consider a personal attack (in this thread specifically). I don't feel like calling someone out for mischaracterizing what I'm saying or flat-out being dishonest about what I've said is a personal attack but, if it is considered that by the admins, then I'll stop doing that. If it's something else, then I'd like to be aware of it so I can check myself in the future.
I'm reading the guidelines now and will try to take the intended spirit. I don't want to get banned but I also don't want discussion to be surface-level and I get that there's a fine line there.
Sorry again. I'll do better in the future.
(I'll try to respond to your other comment later)
There's not a lot of money in the scene for most people. They use the software/hardware they have. Hiding notifications and colourful dots from the OS shouldn't really be an issue.
Why not? The internal I/O is pretty good! Except for this issue, obviously.
Portability is essential for some people, and MacBooks have pretty reliable IO.
Also notifications won't really be an issue for anyone but people using the machine both for personal and professional stuff. In the worse case, you can have different user accounts. A professional machine used for VJing or even audio recording will have zero notifications.
Also I wonder if we're talking about different scales here. I'm not talking about the 150 inch monitor, I'm talking about video art, VJing, and small scale stuff. macOS works fine for those things.
Are you a macOS user? Your other examples talk about Windows Update... the situation in macOS is a bit different, which is a lot of people doing audio/video flock to it. Not everyone needs external hardware, just a MacBook can do a lot.
Yes. macOS is my daily driver and I'm on Monterey.
All I'm saying is that, if anyone wants to say that this dot makes their use case unusable, then they have to admit that the current OS setup was always unusable for them because the OS was always able to display chrome on their displays. It may not have happened often or even in a way that they thought was "unusable" but it was able to happen. The only difference here is that they're not happy with the type of OS-level things that are displayed.
In my experience, people for whom any kind of errant display items matter use dedicated hardware devices for their I/O. If it didn't matter before because it was only windows/alerts/notifications/whatever, then that clearly doesn't make it "unusable" just "not preferred". I fully agree that there needs to be some kind of option for this on presentation displays but the people saying that SNL wouldn't have dedicated hardware for their displays is asinine.
I feel like the notifications issue you mention is bit of a red herring, because having too many things running in the background will cause problems regardless of using external gear, regardless of them showing on the screen or not. You can't rely on external gear alone for stability, the computer itself has to be stable. And the computer alone being stable is enough for 90% of people. And even if there are notifications... so what? This is people doing it for art purposes, on parties. They learn a lesson and never have to care again.
If those people are really using Steam on their computers (like you said on another comment), they surely aren't pros worried about performance, reliability, or anything of the sort that warrants a dedicated playback card, so I don't really see this use case (Steam+Blackmagic) existing at all.
Surely the default I/O is nowhere near enough for SNL or even for local broadcast, but it is good enough for a large contingent of people that don't need the same reliability that you or SNL needs. And it does works for them in practice, without notifications, and without OS chrome... except for the new orange dot, which is a nuisance.
If I could have audio inputs/outputs that were good enough for my audio work I would also prefer not using an external audio interface. I often compose on earbuds, and that's fine. For mixing I need something else. Some people might not. Who am I to judge?
Also, it's not an "or" option. Pros turn off notifications/internet, and don't leave Steam running when working, like the other poster is saying.
So it shows that there's a lot of professionals out there not following best practices (which isn't surprising to be honest, it's the case in every industry, including super critical ones…).
Maybe the orange dot will actually help these people start using best practices in the end… (note that I'm not defending Apple's move when saying so, I really hate their tendency to think there customers are wrong and because they are Apple they know better)
I really don't believe anyone running Steam on their video computer is worried enough or even serious about reliability to use a dedicated video playback card. Sure it would be nice if everyone used a dedicated card, but it's 100x more important that those people stop running Steam... unless maybe if they're pro game streamers or something.
Also, even Steam requires extra permissions on Mac to display the overlays you mention.
And no, this wasn't a Steam overlay. It was a prompt to restart the Steam app to complete some update. That does not need additional permissions.
For an incredibly small set of people who are both professional enough for this to be an issue but also not professional enough to spend a hundred bucks on a device specifically meant for this purpose.
If you're going to claim gaslighting, then maybe actually include the intricacy that you seem to have missed there.
It continues to work fine for the vast majority of people.
Let's call a spade a spade. You're blowing it way out of proportion while in reality it's an issue that impacts an incredibly small fraction of the userbase.
Your post above was also only talking about those people with mic input and video output, so it shouldn't be a problem that I did the same.
Also it's not just video, it's basically anyone "plugging their mac into shit" for professional output purposes. Could be video, could be a powerpoint, could be a software demo.
It's not about OS notifications that you forgot to disable. It's anything that the OS wants to display. Notifications and alerts were just an easy example because everyone knows what they are.
People can still plug their shit in and it'll "work fine". If they're recording audio, they'll see a little dot. If they want control of what shows up on the display, there are answer for that. Pretending like that hasn't always been the case is misguided.
The unfortunate case with a preference is that as soon as you enable such a permission folks can force users to enable that permission to use their invasive software. The orange dot exists because applications have been abusing privacy by invasively using audio and visual recording to spy on people. The solution to this problem isn't very simple and while the orange dot is causing headaches the lack of an orange dot also causes headaches.
If both options have a disadvantage, give users a choice which of the evils they prefer, for example in the pre-boot environment.
P.S. I am of course aware that it is not typical for Apple to give users a choice.
It can be empowering to users to deny bad choices - since it prevents users from being coerced by malicious software (i.e. tiktok, facebook, instagram - not like virus laden software).
That all said there is some legitimate functionality being lost with this decision.
empowering ~ deny bad choices
Just my opinion, but these linguistic contortions undermine your point.
Providing users with a decision in which there is an asymmetry and/or incentives could be setting them up for manipulation. But i think there are ways to balance the asymmetry vs. just removing the choice. A simple report showing which apps were watching/listening along with screen time could be useful, for example.
I do think there might be some other solutions but I also think the orange dot is, for almost all users, a perfectly acceptable solution - visually obvious without being obnoxious.
That is why the user should be given the choice to activate it: make it a sensible default choice in the respective settings. The experienced users who know what they do should be empowered to make a different choice if it makes sense for their workflow.
Some of the conventions I've gone to ran everything in a room off a single laptop. (I've set up such things.)
Concerts aren't much better. Only the largest events and venues have the kinds of "professional" setups you're thinking of.
Again, we're talking about "professionals" vs., at best, prosumers and consumers. Those applications are not unusable because of a small dot.
I think this change would be fine as a default, but it should be configurable by the end user.
The point is that users never had control of the output on external monitors. This situation is exactly like the situation that's happened multiple times on every OS where someone discovers a way to do something that relies on some function that they either misunderstand or are misusing (think Y2K). Just because it hasn't bitten people in the ass doesn't mean that it's a good way of doing it. People in this thread have commented surprised that Apple hasn't run into this issue during internal uses by its production teams but the reality is that Apple's production teams don't run off the built-in I/O because that's not how you run a video system you need 100% control of.
I agree that Apple should find a way to make this better (or at least hide it on secondary displays) but that's only a workaround. Today it's an orange dot. Tomorrow, it'll just be some other display indicator. The fact is that you can't (and have never been able to) control what displays from the OS on these secondary monitors. The fact that it's just now biting people in the ass is their fault, not Apple's.
Um, no, how about the built in one worked fine, didn't require me to buy a very expensive additional piece of hardware. This change took away functionality that worked before the upgrade?
> let's not start with the idea that pros are outputting directly from their computers without the right hardware.
If professional means derives income from work, you would be wrong. If pro means works for an organization with unlimited budget, you would be right.
It had the same problem that it still has. The OS can place items on the display that you don't want in the middle of a presentation/performance. The only thing that "worked fine before" is that you were ok with what the OS put there because it was rare for that to happen.
>If professional means
It means that a dot in the upper right hand corner makes the function "unusable". If that's the case, then a professional would not extend/mirror a desktop display. They make sure that they control exactly what is being displayed and you can't (and have never been able to) do that with macOS.
It's not reasonable to say it's the "same" problem when they changed it this much.
> The only thing that "worked fine before" is that you were ok with what the OS put there because it was rare for that to happen.
So rare it may have never happened. So yes, it did work fine. Are you implying that's wrong? There's no way to make a bulletproof setup, after all. Maybe with an external device you get a glitched or blank screen instead of a notification, but any hardware or software could fail. Possible chance of failure is not the same as a constant 100% chance problem, and does not excuse a constant 100% problem.
They didn't change it much. They added an indicator to the existing OS UI when a recording device is active. That's the only change that was made. As I've said elsewhere here, they could have added anything to the UI in the past and it would have had the same effect. People just didn't care because that stuff didn't affect them.
>There's no way to make a bulletproof setup, after all.
No one is saying it needs to be bulletproof. If it did and that's important to your production, you'd have backups to switch over to immediately. You're taking what I'm saying out of context and arguing straw men. If a small dot on the screen makes things "unusable" for you, then your setup is wrong. If anything that you don't want on the screen that you didn't put there is important for you, then you need to create your setup to function like that and allow for that.
All I'm saying is that there are people all over here, professionals or otherwise, who claim that a small dot on the screen is a dealbreaker for their ability to do their jobs. If that's the case, then they've been leaving their livelihoods up to chance because every OS has the ability to display things on an external display on top of a full-screen application. I'm glad some people were lucky enough for that not to happen but people whose livelihoods depend on that don't leave those things to luck.
They changed the percentage of time you have an OS overlay on the screen drastically. That's the metric I was using.
> No one is saying it needs to be bulletproof.
When you accuse people in situations where the dot matters of "leaving their livelihoods up to chance" for using normal output, you basically are saying that the notification-stopping part of the system has to be bulletproof. Swap 'bulletproof' with 'nigh-perfect, far in excess of all the other parts of the system' if you want.
And no, that's not going "by their own logic" or anything. Refusing to accept a constant dot in the corner does not mean a single notification would ruin their career.
>It means that a dot in the upper right hand corner makes the function "unusable".
I'm pretty sure professional has nothing to do with dots in the corner. There's really not much to defend about this change, and this change really reduces the utility of macbooks for many people who derive their income from work using that macbook. Hopefully, apple gets the message from users and fixes it.
It absolutely does in terms of this conversation thread since that's what the topic of discussion is.
>really not much to defend about this change
Yes, there is. It makes the vast majority of Mac users aware of when their input device is activated in situations where they may not know.
>reduces the utility of macbooks for many people who derive their income from work using that macbook
It absolutely does not. It only affects the very small portion of users for whom the dot is a dealbreaker, that have to capture audio while presenting, that are not technical enough to follow the steps to remove the dot, and that also have never cared before about the OS being able to render chrome on their work/display output.
There is ZERO reason to force the dot on every display. Restrict it to the display(s) also showing the menu bar and this becomes a non-issue. I can't believe anyone involved in this at Apple thought this was a remotely reasonable thing to do!
It didn't work perfectly fine beforehand, though. They just didn't care about how it worked before. Now, suddenly, they do.
For me, it's good, not bad. I’m sorry that for some people it means they need to do their job a little bit less careless, but the overall importance of this dot is worth it.
Search for it. There are countless threads about the issue online, and last time I checked noone knew of a way to prevent it.
Imagine holding a presentation, or watching a film with someone, and suddenly your private emails fill half the screen...
As repeatedly said by many people, Apple is making a tradeoff between security and special-purpose requirements. If you have a special-purpose requirement, then make sure your tools are configured for that purpose. Don't whine that the general use-case doesn't fit it!
You'll see similar whining from web devs trying to make Chrome or Firefox "hide" the chrome and go full screen programmatically. That's fundamentally incompatible with end-user security and shouldn't be allowed, ever. Asking for it won't get you anywhere. If you need full screen control, use something like Electron, not a web browser. If you need full screen projector/screen output, use a tool/software appropriate for the job.