I don't get it either. The notch essentially covers up the middle of the menu bar and is a non-issue when full-screening. Apple essentially encroached the screen into the camera's territory and used the extra few pixels for the menu bar with the notch covering the middle of the menu bar which is typically empty and wasted space.
There's zero impact on full screen apps and non-fullscreen apps get to claim the space formerly used by the menu bar.
How so? Are they going to push full screen apps up to the bottom of the notch? If not, how are you sure it won’t have any impact on so many different apps?
The menubar disappears when you’re in a full screen app, so that won’t help.
I’ve used full screen only for essentially every app daily for the past 10 years on Mac, curious to see how this works out.
By default the system blacks-out the segments next to the bar in full-screen mode. If devs opt in, they can instead choose to use the extra space in full-screen mode. So there's literally no downside.
The screen is apparently a 16:10 display, plus approximately 70 (not sure about the number) pixels on top: thusly, when an app goes fullscreen, the OS just blacks out those top pixels and puts the app in the 16:10 area (unless it uses the new API and requests access to these pixels)
> This analysis completely ignores that the new shiny system is supposed to be a better experience
Having used a Qi charger for my existing phones and a MagSafe charger for my Apple Watch, I can say that I prefer the non-MagSafe Qi charger for my phone. It's the one that most gives the illusion of truly wireless charging.
With MagSafe charging now I imagine I'll have to lift my phone and presumably detach the MagSafe puck at the same time, making it more cumbersome than what I do now, which is just lifting the phone off the Qi charger. I verified this hypothesis here: https://youtu.be/XDKPNwC-5D4?t=185
While there will likely be sticky/weighted versions of the MagSafe charging puck to alleviate this issue at some point, this is not a better experience as designed.
I'll likely continue to use a generic Qi charger for my phone
My Turbo Pascal story is weirder than most I think. When I was much younger, someone I knew was learning COBOL and the "editor" they were told to use was a pirated binary on a floppy. That binary was called tp3 and nobody paid any attention to it until I, wanting to also learn a bit about COBOL, decided to try it out myself and read the notice that the program output. Something about Pascal.
Long story short, I ended up looking into Pascal and using that tp3 "editor" to learn a bit of Pascal, which seemed a lot more fun than COBOL.
All Pre tells me is that everyone else is going through more "security" than even the TSA deems necessary for absolutely no reason. I refuse to enroll in it mainly because of that.
I'd imagine by your 50s you'd have already learned the right attitude to succeed at anything: do the best you can, ask for help often and speak up right away when scope explodes!
Attitude is not the problem here, getting a job is. Few acquaintances of mine in their thirties also try to jump this developer bandwagon and it's very hard to get a junior position for them, because they are "too old" (of course, nobody says that directly). Actually, they started to get interviews only after had hidden years in their CVs (as per mine advice).
Which is quite funny when you consider many of us are using technology that is only a few years old and we are constantly told we shouldn't stop learning to have a career in programming.
That's close. It's meant to be more like dysfunctional queue.
From the README:
DIStributed QUEue but is also a joke with "dis" as negation (like in disorder) of the strict concept of queue, since Disque is not able to guarantee the strict ordering you expect from something called queue. And because of this tradeof it gains many other interesting things.
There's zero impact on full screen apps and non-fullscreen apps get to claim the space formerly used by the menu bar.