![](https://programming.dev/pictrs/image/1df84acc-6056-4d04-8d54-c9a3af20a3ad.png)
![](https://programming.dev/pictrs/image/028151d2-3692-416d-a8eb-9d3d4cc18b41.png)
Bundling my two sata ssds into a single zfs volume, instead of manually moving stuff around between the nvme and two sata ssds. Combined with compression, and for my code folder deduplication it also resulted in a lot more usable space.
Bundling my two sata ssds into a single zfs volume, instead of manually moving stuff around between the nvme and two sata ssds. Combined with compression, and for my code folder deduplication it also resulted in a lot more usable space.
That’s an interesting approach. The Traditional way would be to go by game score like the AI Mario Projects. But I can see the value in prioritizing Bullet Avoidance over pure score.
Does your training Environment Model that shooting at enemies (eventually) makes them stop spitting out bullets? I also would assume that total survival time is a part of the score, otherwise the Boss would just be a loosing game score wise.
Bringing more modern tools and features to existing large code bases is “destroying his reputation”? Bjarne and the committee is constantly extending and modernizing a language with code bases older than me. Yes that means the old stuff has to be kept around but that is the price of allowing existing code to migrate gracefully instead of just throwing it out of the window. There is a problem with some missing rails to enforce current and saver techniques but Bjarne is not denying that.
That is the mindset that gives us text editors using 100% cpu to blink a cursor because their css triggers a bug in the web browser they ship to render the text editor.
You can be memory save without shipping a whole browser, but disregarding power and memory efficiency will just make performance gained by hardware evaporate in overhead.
This also works the other way round:
The best programmers won’t be able to fix you clunky mess of bureaucracy by making it digital.
“But throughout that time, I actually had no inkling what game development was actually like. How hard the designers, programmers, artists, producers, and everyone else worked,” he says. “The struggle to bring a vision to life with constantly shifting resources. The stress.”
Then tell us about it. Make it heard where you get Stressed and where you rub up on the state of the art. List off what had to be finished in crunch time. What got pushed by Marketing or Management. Leaving everything up to a nebulous “you don’t know” makes any criticism easily dismissed and reduces leverage against systemic issues.
how do you stop it on client side? I’m not sure if it has been deployed into the wild but these days computer vision is good enough to just work off the images. Capture image signal, fake usb mouse outputting movements calculated from image data. If this isn’t already available it’s only held back by the need for extra hardware.
The question is: Are we asked to change it? The quotes hark back to Japanese first impression of the west using the term. They did not state that they want us to use a different term, Yoshi-P recalled his teams impressions of foreign reactions to their products from 20 years ago. The referenced Interview with the Xenoblade Devs also does not echo the Sentiment Yoshi-P put forth. As far as I can see all articles putting JRPG out as a discriminatory term are referencing the same single Interview.
I wish. Sadly the google play store requires monotonically increasing build numbers, so any option of resetting build numbers after major releases goes out the window.