In simplistic terms, at supersonic speeds the air particles do not have sufficient time to "get out of the way" of the body moving in the air. This causes the air particles to be compressed into a dense "shock wave", which can cause separation of the air flow from the surface of the airfoil, leading to a stall. The properties of a wing that handles supersonic airflow well are often at odds with a subsonic wing.
While I've always appreciated some music due to some amazing specific technical aspect, such as Jacob Collier's harmonies or Steve Vai's guitar skills, the records I'd take with me on a desert island tend to consist of very simple elements combined and executed just perfectly. And by "perfectly" I mean with all their imperfections and unquantifiable emotional appeal, which has very little to do with the level of technical prowess. I guess what I'm saying is that for me, taste matters more than skill in music.
In my case, CPU usage goes to the roof if I use a scaled resolution instead of the default one. If that is the case with all macOS users with non-default resolution, I wouldn't call it low prevalence.
Not an issue for me. I have a imac 5K and a retina mac book pro. Both with image scaling on by default. I think most recent macs have retina now.
I use Firefox exclusively and have done so for the last 2 years or so. This sounds like it could be a driver issue for specific macs. Both my macs have AMD Radeon chipsets & quad core i7s.
Anyway, I'm sure this issue is real. Bugzilla ticket numbers probably exist for it and might be more helpful than vague complaints about things being slow.
Of course some web sites are a bit unreasonably javascript heavy these days. The downside of a large screen is that pushing a lot of pixels around is not free. Usually closing any offending tabs immediately restores any cpu usage I see. I'd suggest using the new task manager thingy (page menu->more->task manager)
Anecdotal, but I've found it happens when image scaling by a factor other than 2. Affects my setup of a 4K display at 2650x1440 effective resolution, or 1.5x scaling.
Exactly this. I run at 1920x1080 effective resolution on my 15" rMBP, and 1680x945 on my 13". I see the issue on both.
When I switch to the "default" scaling (1440x900 and 1280x800, respectively), it stops. Only the 15" has a discrete GPU, eliminating that as potentially causal.
Me too, and as it happens, I'm running on retina with "more space" enabled. Firefox is unusably slow, to the point where I'm probably abandoning it after a few weeks of really trying to get into it. Which is a shame, because I love the idea of multi-account containers and other privacy features.
That's not really a science either. While there are things like experiments and the scientific method, most of computer science is a confluence of mathematics and engineering.
Portability etc notwithstanding and purely from an API point of view, there's no question that DirectX is superior to OpenGL. There are lots of examples, but the mere fact that you need _another_ 3rd party API such as GLEW even to be able to use OpenGL's latest features in the first place should speak volumes.
Well, of course you don't _need_ it. You can always go and parse the extension string yourself, then call LoadLibrary() and GetProcAddress() to manually setup pointers to the extension functions etc. The point is that you don't have to care about any of that crap when using DirectX. Bear in mind, this is just one example.
In DX you have to care about version and capability bits (up to DX9) or speed (same caps, some may be implemented in software, DX10+). Same thing in slightly different way.
