Unit and method tests are still useful to quickly find where the issue occured. If you just test the input and output of the program, no its individual units, then in an error case you still need to figure out where it exactly went wrong. So in short, its not just to check if program behaves correctly, unit tests also helps debugging.
Greed.
Steam and itchio are not curated (or only minimal). So naturally those places will also attract junk. The tradeoff is the free and open market without any organization telling what is allowed and what not (at least for the most part). Similar to Apple vs Google store, I prefer the Google store with more freedom over Apple. The price is more junk, but I want to decide.
If you have security concerns, then its probably a good idea not even to run the code. But if you really really want to, one could use Virtual Machines with CPU and graphics cards passthrough. In case of Linux, even the Kernel on your machine is reused in the Virtual Machine and the filesystem is nowadays very good optimized too. All of this gives you near native performance. The little bit performance hit I think is acceptable, given that security is high priority here.
I personally wanted to set this up, but honestly I’m too lazy. BTW Flatpak is not a good container, if security is a high priority.
Why does everyone want to fuck Sam Altman?
It’s not AI usage in the kernel - it’s the increase in AI to do code auditing that had seen the spike in bug reports.
Umm, that is Ai usage in the Kernel. I didn’t talk about generating code. The developers use Ai. You even explain how they use Ai…
The point is not to buy more RAM, but reuse the existing one and buy a new CPU.
CPUs have still a good price on the market, I don’t know about Motherboards. So you could eventually buy a new board that supports modern CPUs, but still support DDR4. Then just reuse the RAM. Everything else could be reused. That’s the only way forward I guess, if you don’t want spent too much money, but still want a modern CPU.
I was using a 1070 just a few years ago. I also felt the performance lack, but it wasn’t just the card. The entire PC was old, with old CPU and DDR-3. I wonder how the 1070 would hold up on my current DDR-5 based computer. I would have swapped out for testing purposes, but I don’t want to install and setup Nvidia driver. I’m on Linux and the modern Open Source drivers only support starting with RTX 20xx series.
Those Pascal series was the best graphics card I ever had.
There goes, my hopes and dreams for 2027.
Linux versioning does not work like that. There is no major release, the are all equivalent. It’s not a joke, Linus Torvalds just don’t want high numbers, so at the latest .20 (dot-twenty) release they create a new major one. But functionally it doesn’t matter. Therefore the release version is meaningless for our discussion. I’m really serious about this, this is not in any way trolling or being toxic. All we need for this discussion are already present in the graph.
Have a look at: https://en.wikipedia.org/wiki/Linux_kernel_version_history
In contrast to semantic versioning, the major version carries no intrinsic meaning for the kernel, as Linux promises stable interfaces and behavior even when the major version changes. However, since version 3.x, minor versions have been capped around 20 to avoid the false perception that changes between large minor versions (e.g. from 5.30 to 5.31) would be less voluminous or impactful than changes between smaller minor versions (e.g. from 6.1 to 6.2).
This doesn’t make sense. We are comparing single releases, not the entirety of 6.0 up to 7.0. How many years would this be? Also why do people want see 6.0? We have 14 last releases, in span of 2.5 years. And only the last two or 3 releases got a huuuge spike, which coincides with the broad usage and advancements of Ai in the Kernel.
We don’t need to compare older versions. The data is here and enough to support this claim. These are 14 releases for gods sake.
I’m not arguing that (and know about the Palworld case off course). What I argue is, that most companies big or small want to avoid going to court, and fight (possibly years) over patents. Or avoid getting sued if they use patented mechanics. Just like with the situation of emulators, it doesn’t matter if the developers are right or wrong, they fear going to court against Nintendo.
Now in case of Palword I have to say, bravo. Wish more had the courage (and money!) to fight Nintendo. It would make gaming better, because I hate game mechanics being patented.
That is more plausible, agreed.
Exactly why this is still a problem. There are patents of game mechanics that prevented other devs to implement them, because they do not want to go to court or fear they could lose in a court. The Nemesis system is such an example often brought up in discussions like these. Or the ability to catch a Pokemon with the Pokeball in the way Nintendo does, and riding/flying with a monster are also patented. And on that note, I think Nintendo lost the case with the riding or with the catch mechanic, I don’t remember details.
Game mechanics being patented is enforceable as far as I know, but only if the patent is in that country and is valid (validity can change even after it was granted, but that is not common). The point is, if valid or not, most companies just stop using those game mechanics out of fear. And that still holding back innovation.
game mechanics cannot be copyrighted
But patented.
The game companies probably paid them to block.
There is no need to go older. We have 14 releases in between 6.9 and 7.2.
It shows that the CVE fixes were consistent during the last 2.5 years and 14 releases. And with the recent rise of Ai usage in the Kernel, this bump aligns.
commit frequency bump compared to 5.0 and 6.0 releases
Why 5.0 and 6.0, those are ancient. This goes back to 6.9 from May 2024, where Ai usage in the Kernel wasn’t a thing until the recent few releases.
I see two reasons this could be: a) either it is by design, so people click and read it, or b) he couldn’t figure out a good and short title that conveys the article. So in other words either clickbait or skill issue. :D (I’m just joking here!)