2G of ram at build is not that outrageous, however yes, with composer2 (released like 7 years ago?) it uses less ram.
Also the frameworks got less bloated and more modular
Coffee contains several ingredients that act as opioid receptor antagonists, which can be unpleasant (as in "reverse the pleasant / calming effects of endogenic opioids"). Some people seem to be more affected than others, kinda like with the intensive gastrin release / coffee induced instapoop.
You'll usually stop hearing the CRT whine in your 20s, 30s if you're lucky. It's at nearly 16KHz and the highest frequency you can hear always drops as you age.
Of course, these days people also regularly don't hear it since CRTs are nearly all gone.
Even back in my youth and early adulthood, there was a wide variation on how loud CRTs were between models and individual units. There were some that were close to silent for me, while others were very noticeable.
The signal is at a frequency of one cycle per line-second, but there's an idle period while the beam goes back up to the top where it still cycles so the actual frequency will be a bit higher than a simple lines/frame * frames/sec calculation would indicate. Even for broadcast TV that was beyond what a lot of adults can hear (but a lot of kids can, as plenty of posters in this thread have said.) I want to say 15.7khz but I certainly won't swear to that. As your resolution goes up the frequency will go up so some people would be able to hear what resolution a monitor is set to.
That's only if they don't QC every single part, for every single car, coming from new suppliers.
Which RR would do to avoid the obvious problem, only after a supplier has been verified to be sending only the highest quality product, would they ease off.
The simplest thing is that the supplier charges double or triple the unit price such that they can accept half the parts failing inspection and getting sent back.
It's more than just QC. When you make 3M cars per year, you get a lot of data points about what fails, and you you feed that back into new designs. You also nail manufacturing tolerances. When you make 4,000 (and a lot of those won't see the same mileage as a Honda), there aren't as many opportunities to find these issues.
Or another way: you an QC a bolt to death, but that doesn't tell you if it's undersized for the design.
Yes it does when there are several stages of prototypes and engineering builds before the actual production vehicle is shipped to customers... and the hundreds of other mechanisms and systems that major automakers use nowadays. I mentioned QC because it's the first screening for arriving parts, not the only thing that occurs.
Do you not know how car manufacturing works?
Anyways you don't have to take the quality of RR parts on my word if you still think it's impossible, just go a showroom and inspect it yourself.
Design iteration is typically a long tail phenomenon - new issues keep coming up as the system (car) faces new scenarios.
Even a high-resource prototyping program can only go so far with scenarios like - wear and tear/part fatigue, adverse environmental conditions, local peculiarities (e.g. regulatory requirements for uncommon configurations), unintended but common maintenance mistakes etc.
For example, a Fiat car my family owned suffered a cascade drivetrain failure after about 9 years on the road. I don't think a prototyping program could have captured that ahead of time.
The fact that the showroom RR parts look fine only indicates that the parts are ok immediately after manufacturing; it does not promise they'll work fine after several years even if treated will.
> Design iteration is typically a long tail phenomenon - new issues keep coming up as the system (car) faces new scenarios.
Even a high-resource prototyping program can only go so far with scenarios like - wear and tear/part fatigue, adverse environmental conditions, local peculiarities (e.g. regulatory requirements for uncommon configurations), unintended but common maintenance mistakes etc.
Which is why automakers typically recommends a maintenance schedule that catches the vast majority of potential failures before they occur on the road.
How does this, or anecdotes of your family's Fiat, relate to engineering and verification practices of parts coming in from suppliers?
I got to top 10% of Trackmania players (extremely competitive) just by watching Wirtual’s streams. Couple of advices (and learning to implement them) were worth more than hours of (bad) grinding.
And he is „only” in like 99,9th percentile in time trials, not even competing in top tournaments.
Same: when Path of Exile was less popular and had races I was often able to finish top 10% (or even much better) by just copying techniques from streamers who were good.
The concentration of knowledge that was available in a (successful player's) stream was far more useful than what I could gain from personal experience playing alone.
The tradeoff seems to be „ability to deploy working software without reliance on single central authority”.
You may get rid of several smaller bottlenecks this way, introducing an enormous, all-encompassing one.
Or am I wrong?
