Cirk2

Since we now have confirmation that an open implementation is legally impossible I would consider the HDMI forum to be a cartel and not a standarts comitee. Therefore it should be dismantled by anti-trust authorities asap.

"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.

Display Port has a standing in Computer Displays but is basically unheard of in Home Entertainment.

Why are they so desperate to be liked by users? Their whole mission is anti-user. Their job is to scrutinize paying users and take away the softest they bought when something isn't right. Of course they are not liked, they are the bouncer at the disco sending people away based on their feeling.

So the HDMI founders are Philips, Panasonic, Sony and Toshiba Known for their Players and in part TVs. The HDMI Forums consists of the rest of the TV Manufacturers and the big names in component Making (Analog Devices, NXP, Realtek, Qualcomm, etc.). So they are all members of a cooperation dedicated to "encouraging and promoting the adoption and widespread utilization of its Final Specifications". I hesitate to call their decisions on connectivity options unencumbered by interests.

oh btw: Anti-Trust does not require to there be no competing offer, just vast majority of market share.

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.

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.

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.

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.

Having the runtime of the codec installed in a wine prefix is not the same as having it work. Just like wine has to work on the codec to get the data to it and output back to the game, in a way that the game, the codec and wines d3d implementation can deal with it. This is made mode difficult by some codecs doing output themselves and some handing buffers back to the game for display.

This is hard and gruesome work. With painstaking observing and duplicating behavior, since a lot is not documented and for a clean room implementation the person implementing it can not look at disassembled binaries or (hypothetical) code-leaks.

Now how do you get a game to not use the codec it’s shipped with? By cracking.

That is just wrong. "Cracking" is the circumvention of Copy-Protection. Before Denuvo afaik no Copy-Protection had data-integrty checks, so modification of game Behavior (aka Modding) did not require tampering with the Copy Protection. Best Example SKSE for Skyrim, a tool adding a lot of additional functions to the internal scripting language while still keeping copy protection in tact.

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.

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.