Good question. Their POWER series of CPUs were not insignificant in capability, their chip designers were clearly technically sophisticated, and GPUs are just specialised vector processors with a few extra bells and whistles - stuff IBM is extremely familiar with.

It would not have been difficult to release a GPU or other LLM-specific processor to go along with the POWER11. They'd been working on the POWER11 for 4 years, they knew in 2020 that LLMs had a strong potential to be significant for Big Data processing - an area you use big iron for, they're not rank amateurs, they have plenty of reserve, they could have assembled an emergency team to build a vector processor that was custom-designed for just LLM work, and released an LLM processor card that could run circles around nVidia.

They didn't. Because, as has happened before, their management is simply too stupid and too slow.

I feel like I need to spell out the math.

300 * 1,000,000,000 = 300,000,000,000
300,000,000 * 5% = 15,000,000,000

That's all CA will get from the one time tax "from Apple". Just 15 Billion Dollars.

What if...

Someone (say someone who was familiar with doxygen and GCC) developed number of comment types, where some stipulated preconditions that must be true for the function to run correctly, postconditions that must be true once the function has run, kernel facilities that the function definitely needs, and kernel facilities that the function definitely doesn't need. These would all be optional for any given function.

A static checker could then validate if the code meets the behaviour expected by the programmer. This is precisely what is done in SPARK, a fork of Ada for high-reliability code. Combined with existing static checker capabilities, this would greatly increase the number of bugs that could be caught with all kinds of tools, AI included.

It could ALSO build a full fine-grained mapping for any fine-grained mandatory access controls system. You'd also want includes that you could import for precompiled libraries. This would allow someone to verify if the code was making unanticipated/undesirable calls but would also make SELinux possible to develop for at the application level.

It would not be trivial. If it was trivial, it would have been done simply because it already IS done in other languages and that makes it "obvious" to anyone who has been programming for a while. However, it should not be massively complicated, simply because you can use AI as the static checker. Once it has a definite set of bounda that must be satisfied, it should be much more capable of knowing what paths would violate those bounds. Which means that the checker stage essentially is trivial today, leaving only the markup stage.

Your statement would apply if these data center space nutters could certify that everything they launch will reach escape velocity.

For everything else, what goes up, must come down. Right back into our jurisdiction.

Is to set coursework and exams that are specifically crafted to exploit where AI is weak or prone to hallucinate.

You do not ban cheating, because those who cheat will inevitably find ways to circumvent the ban.

Rather, you exploit the properties of the mechanisms of cheating to ensure that those who actually understand the ideas are marked relatively highly (regardless of whether they reach the textbook conclusion) and whose who do not understand the ideas cannot do well even if they give what is in the textbook.

The interest should not be in precise answers, but in precise use of tools of reasoning and analysis, because this is what actually matters when it comes to understanding. Yes, it means you can't standardise so easily, and you have to devise things in ways that don't penalise intuitive thinkers over methodical thinkers, but you cannot teach a subject properly if you are only concerned about the surface.

We can't afford to let the success of big tech companies depend on the health of fragile meatbags. We need to get resilient, fault-tolerant AGI in there running the enterprise. Also, unlike meatbags, you don't need $100M stock payouts to convince an AGI to work as a corporate executive.

I didn't see a 5.6 option on the Windows client last night.

Haa anyone else observed 5.6 in the wild?

Trump doesn't need to have power, he only needs to create fear, uncertainty, and doubt.

Companies are risk-averse, which is why Anthropic pulled their AI model for a while.

You can get Veracrypt to work with the Mac, via FUSE, but I don't know how safe/robust that is. It's probably more secure than anything Apple has. It's certainly more secure than anything Microspot has.

But, yeah, it's getting extremely irritating that useful stuff is being taken out of commercial OS' and junk put in.

There's no known client, but there is a very good unknown client:
(For those familiar with Kenny Everett...)

https://dev.to/jfscoertzen/cha...
https://snapcraft.io/chatgpt-d...

Whether it has all the official features, I don't know. But that's your best bet.

They've already dealt with this. If you read the fine print on these agreements, many or most of the recent ones say that the company has the option of rolling up any "substantially similar" arbitration cases into a single mass arbitration. (Which as usual, is decided by a person whose paycheck ultimately depends on the business of that same company.)

Sorry. When you signed up for that discount card a few years ago, you agreed to individual binding arbitration only.

I just have to chime in here. My drop-out paper - back around '91 - was titled "Shovels & Society". It was the final for my Computers and Society class - which I did not think much of. The TA was great, though.

After a few weeks in the class, the TA asked our group how many of us were in this because we enjoy programming. I raised my hand. I was it. I decided I was no longer in the right place.

Anyway, my brief argument was that computer/software advances were a lot like those of the shovel -> bulldozer, etc. Just like every other advance, ever. People would lose jobs like they always had, etc. It was supposed to be 15 pages - but I just wrote 3. I feel bad for my TA - she was so disappointed.

I've been happily programming ever since (and before). I'd learned everything I was gonna for compsci anyway.

But holy crap. AI. The shit I can get done now. I feel like there is no way I could get another programming job - between AI and Agism.

The DoD is known for viruses transporting payloads across airgaps onto Internet-connected machines. One thing it isn't is "so secure".

But, to the extent that it IS secure, it uses pretty much what I outlined. They use Class 3 certs for all users and all machines, and have done since about 2001. The US Navy got to trial run thei system to shake down the defects in the design, before they rolled it out to everyone. Beyond that, they use segregated networks (in principle, physical separation rather than logical separation, but who knows?) and encrypted communications.

What I've done above is take what the US DoD uses today, threw in what the US DoD recommended but never actually implemented in the 70s to fill in some of the gaps, and also included what the US DoD implemented and actually used in the way of Trusted OS deisgns in the 70s and 80s. The NSA and IRS likely use some variants on the same techniques.

So, what I've got above is pretty much why the DoD is as secure as it is.

What I've done is augmented it to handle the fact that you need to verify the hardware and not just the endpoint, and that you need to verify the physical host independently of the logical host. But that's pretty much it.