It's funny, I appreciate DX and HR because they are still obviously video games at their core, jank and affordances galore. MD just felt like they wanted to go all in on realism and inverse-kinematics and cover mechanics and such so it felt like any other hyper-realistic modern shooter.
I loved the gold filter for HR, for another example. I know I am probably in the minority.
I would rather read a write up of someone doing just that. This exact thing has been done many times now and no one is really learning or demonstrating anything new. It is cool, insofar as AI tools are capable of reverse-engineering, mechanical translation, and automatic verification, but it is no longer _novel_ and borders on spam.
It looks like they are attacking the "leaker" instead of addressing the leaked issues? They clearly don't refute that Andy actually did tell employees to stop writing code and to ship faster with AI, and they don't refute the "loser" comment. It looks like damage control through shit-stirring and a poor attempt at a Gish gallop.
You have left out the second half of the sentence, "... by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries."
The position taken by the courts and the administration is that "authors and inventors" means "human". The monkey could not be the author of its own selfie photograph, for instance.
Maybe this doesn't reflect the intentions of the Framers, but it certainly should color any modern discussion surrounding the purpose of copyright law.
It would be a terrible idea for Intel to return to DRAM. Just like it was a terrible idea to enter the flash market. They are commodity technologies subject to massive supply and demand shocks. Intel made the most money by leading the process node race and shipping the best silicon for servers, and they lost their way through short-sighted financialization games, long bets on losing technology like 3D XPoint, and forcing out their best engineering talent.
There are many permissively-licensed source files in the Linux kernel. You are mistaken if you believe those files cannot be distributed independently and included in other permissively-licensed or closed works. The viral part applies when distributing the combined work, so the vendor can't say "some files are MIT so tough luck"; all sources must be made available for the binary you receive if any source is GPL-licensed.
Nvidia locks the hyperscalars into long-term contracts to buy GPUs and servers. These purchases then fill up warehouses because the data centers and power success cannot be built fast enough to bring the hardware online. The demand only exists because the scalers are in a Mexican standoff, and canceling the Nvidia contract is basically handing the model-training race to the competition.
If LLMs are good enough to write code, they are good enough to write tests. In fact, they can be quite creative at finding test scenarios which exercise the code in unexpected ways.
The usefulness of testing is basically orthogonal to the advent of language models. This question boils down to whether you think the agents are "cheating" through changing the invariants encoded by the tests to something that no longer matches your project's requirements. To this, I would suggest that you read the code they produce, tests included, and not sign off on stupid changes to cheat on tests. This is not a common thing I've caught agents doing, FWIW.
What? Niantic (Google) admitted they were training spatial AI models. I have not seen evidence that the data was a "foreign intelligence-gathering operation" and I would welcome a source.
My friend, inconsistency is the entire point. You now have incredible power to write truly native apps that fit in with the platform and follow all the standards. The bottleneck is now you, or whoever owns each target platform and understands what native apps feel like.
The standard doesn't dictate the UX of settings screens. That's entirely on the platforms which own the screens and I would hope that is kept out of already-huge standards like WebAuthn.
This isn't a standards problem, this is an "Apple, Google, and Microsoft made using your own software difficult" problem. They have an interest in making their authenticators the default, and the settings UX on all three platforms makes it unclear that their authenticator is active as well as your own "third-party" authenticator choice.
Wait, Trezor is just selling off-the-shelf QFP chips and holding their customers accountable for their own supply chain? They can't pot the bare dies? They can't burn in a signature? Do they think everyone else is stupid?