I wonder if/when we'll reach the point that it's cheaper to manufacture SRAM (with 6 transistors per bit if I recall correctly) than it is to manufacture DRAM. (with 1 transistor and 1 capacitor per bit)
The transistors get smaller every year. The capacitors, like you say, don't anymore. At some point those 5 extra transistors will be cheaper than the capacitor, unless Moore's Law well and truly bites it.
My feeling about JavaScript is statistically speaking, random JavaScript code is more likely to be spaghetti nonsense than, say, the equivalent Python code. This feeling isn't based on empirical data, tbh it's probably as much anti-JS bias as it is experience with poorly written JavaScript.
Is your criticism of tracing specific to messy, confusing code, with lots of edge cases in the main loop, or does it also hold true for well written code?
I have no experience with compiler design, didn't even take a compilers course in college.
I think you might be misunderestimating how incredible the dav1d AV1 decoder is. Not only does it require less total time than the reference decoder to decode the same video, but it can spread that out over far more threads. I was unable to watch 4k 60fps av1 video on my media center PC (it's from 2019, so predates hardware av1 decoding, and, well, the CPU was a little long in the tooth) until I switched to dav1d. With dav1d I am now able to watch 4k 60fps av1 using software decoding, and my machine uses 10% CPU while doing so. Really amazing piece of software.
With any luck, the dav2d 5x claim will hold true, and 10% CPU usage will scale to 50% CPU usage, meaning I'm still able to watch 4k 60fps video on my media center without a hardware upgrade. (that machine doesn't have hyperthreading, so 50% cpu is actually 50%, not 100% in a fancy suit)
Wikipedia does not say that the Strait is Iranian/Omani territorial waters. Wikipedia says that Iran and Oman claim that the Strait is Iranian/Omani territorial waters.
A lot of people don't understand just how bad the 3d printer ecosystem can be. Most people understand how bad HP/Epson/Canon ink printers can get, but they really need to understand that 3d printers can be worse than that.
While I kinda sorta need my 3d printer more than my 2d printer, it's an absolute nightmare in a way that my 2d printer isn't, and it's caused entirely by the dogshit proprietary software I have to use in order to print things.
"Bambu's software" is forked from an AGPL project and is therefore itself AGPL. I have a right to fork, modify, and use it how I wish subject to the terms of the AGPL. Bambu's TOS is irrelevant. Their TOS is superceded by the terms of the AGPL.
I like the idea of keeping stuff out of the kernel as much as possible, but in this case, there are good reasons why cryptography has to live in the kernel.
We need on disk encryption, and we need to be able boot from an encrypted disk. So we need encryption for that.
We need network filesystems, and we need the traffic over the network to be encrypted. So we need encryption.
IPsec, for better or for worse, is authenticated and partially encrypted at the transport layer, so if we want a linux machine to speak IPsec, we need encryption.
Fixing/changing this would require a huge restructuring of the kernel; it would basically require switching to a microkernel. Given the fact that nobody's ever written a microkernel that doesn't completely suck ass, I don't know that it would be worth the effort.
Within the past month or so there was a fix for rtx cards that should unlock a massive performance increase for certain games. Only applies to rtx 30xx, 40xx, and 50xx. Search terms are "vulkan descriptor heap" if you would like to know more. It's very fresh so you'll need an up to date distro.
The last time I had a season pass to something, they printed me the equivalent of an employee id badge with my face and name printed on it. The badge was the ticket. How do you resell an individual ticket?
Hiding profiles has genuinely made the platform profoundly worse. It's impossible to tell if you've just got a troll on your hands or someone who's making a good faith argument. It used to be enough to check their profile, and either downvote and move on, or engage with someone on a human level.
Now everyone is a troll/bot by default unless proven otherwise.
I was on a jury a few years ago. The defendent was a homeless person with mental health issues. The cop was obviously lying about the one thing that was the core element of the crime. It was like a child telling the truth about every element of the indoor soccer game expect the part where they were the one who kicked the ball.
The jury was me, (white) nine other white people, and two brown people. Me and the brown people thought the cop was obviously lying, and was therefore not guilty. The nine other people thought he was guilty.
Like the cop was obviously fucking lying.
After three days of deliberation we declared a hung jury.
I was speaking with the prosecutor afterwards and he mentioned they were going for the felony version of the crime instead of the misdemeanor (he was obviously guilty of the misdemeanor, the felony depended on the element the cop was lying about) because the dude was a bad dude and they needed to get him.
I looked him up when I got home. (I didn't look him up during the trial, they expressly forbid you from doing that) He had done something bad and went to prison for four years. He did his time and got out. They were still trying to throw the book at him for bullshit.
I looked him up recently. He was never convicted of anything ever again, but died in jail two years after we declared a hung jury. Prosecutor got what he wanted in the end, I suppose.
AirGas prioritizes industrial users, in the case of helium, copper welding. Argon is perfectly good enough for almost all welding purposes, but copper is different because of its heat conductivity. The heat from the weld really wants to go anywhere else. Helium has substantially higher heat conductivity than argon, which allows the heat to flow from the electric arc into the metal faster, resulting in better welds.
Obviously you can't have oxygen in welding gas; it would oxidize the shit out of everything.
A little bit of oxygen in party balloon gas is beneficial. Some kid will breathe it, and when they do, you didn't want them to asphyxiate themselves.
My experience is that it's really easy to subtly fuck something up if you're doing a bunch of trig in code. If there's something subtly wrong somewhere, everything seems to work for a while, then one day you hit gimbal lock. Then you have to add a special case. Then you hit gimbal lock somewhere else in the code. Or you have tan spit out +/- infinity or NaN. Another special case. Or you have acos or asin in their degenerate regions where the minor imprecision isn't minor anymore, it's catastrophic imprecision. Another special case. Trig heavy code will work 0% of the time if you have an obvious bug, or will work 99% of the time if you a subtle bug, and once you start chasing that long tail you're just adding 9s and will never get to 100%. And if you have code that will run thousands/millions of times per frame, you need a lot of 9s to make sure a user can get through minutes or hours of using your software without hitting bugs.
Doing the same work sticking strictly to vectors and matrices tends to either not work at all or be bulletproof.
The other thing is that trig tends to build complexity very quickly. It's fine if you're doing a single rotation and a single translation, but once you start composing nested transformations it all goes to shit.
Or maybe you're substantially better at trig than I am. I've only been doing trig for 30 years, so I still have a lot to learn before I stop making the same sophomore mistakes.
That's not true. The Bible provides a recourse for unwanted pregnancies in the form of a procedure to perform an abortion.
Which is another reason the Bible should be banned from being accessed by minors. If a child needs an abortion, they should consult a medical professional. They should not read about how to perform an abortion in an app on their phone and attempt to perform the procedure themselves.
I have 64GB of RAM and 16GB of swap. Swap is small enough it can't get really out of hand.
I have memories from like 20 years ago that even when I had plenty of RAM, and plenty of it was free, I would get random OOM killer events relatively regularly. Adding just a tiny bit of swap made that stop happening.
I'm like 90% sure at this point it's just a stupid superstition I carry. But I'm not gonna stop doing it even though it is stupid.
If you're using libaom, try switching to libsvtav1. It's still slow, but it's slooow instead of slooooooooow.