fisf

Funny enough.

There is ongoing AI assisted work on this, and precisely the problematic gap in the theory (around Corollary 3.12).

As of now, a required step appears to definitely be missing, but it's not clear if this is a genuine / unrepairable defect.

https://zen.ac.jp/news/zmcpostevent0331e

https://github.com/lana-agents/iut

https://github.com/LANA-Project/genl

> It's like they can't step back from the problem and realise that they need to simplify to make it work better. Nope, just keep hammering more code/proofs against the problem and eventually you'll hit the goal.

There is nothing wrong with that approach if it accomplishes the goal faster, i.e. you can work at the speed of an AI.

>I think it's not just to check - it's to interpret, simplify, apply taste, basically get these proofs into a form that humans can grok and build on.

Sure, but we are approaching a time at which we will have to answer a "why" here. I.e. anything beyond checking and validation becomes of mostly artistic value at some point. And there is nothing wrong with that.

I think you are slightly missing the mark of the historical reference.

What you say is true for modernized budō disciplines. They have very different purposes.

But this this is not what Musashi was concerned with. He was practicing kenjutsu (not kendo) / writing about hyōhō.

The primary criterion was absolutely murdering people as efficiently as possible in a life and death situation.

"The true Way of sword fencing is the craft of defeating the enemy in a fight, and nothing other than this"

That's overly dramatic.

At this point, the assumption would be that they are a non-party witness.

So, beyond not destroying any potential evidence, you might as well tell them to shove it.

By that measure, most software developers should be unemployed.

Last time I head of them, Bosch was planning to cut 13000 jobs in Germany.

Both of those killings sparked protests, and are subject to ongoing investigations and lawsuits.

Well, the National People's Congress / CCP define and frame that practically for you.

It's not like 1.4 billion Chinese have much say in that.

If I am wrong, please remind me again how much say Chinese people had on the escape hatches of Article 51 in your constitution.

Platformio is not simple by any means. That few .ini files generate a whole bunch of python, and this again relies on scons as build system.

That's a nice experience as long as you stay within predefined, simple abstractions that somebody else provided. But it is very much a scripted build system, you just don't see it for trivial cases.

For customizations, let alone a new platform, you will end up writing python scripts, and digging through the 200 pages documentation when things go wrong.

Are you ignoring the codex desktop app on purpose? Or the integrations?

Those use cases are already actively implemented, or being implemented in current software. The 5-10 year estimate is wildly wrong.

You do not need a plugin anymore.

People are accountable for the results they produce using AI. So a scientist is responsible for made up sources in their paper, which is plain fraud.

Getting an automated reply concerning the submitted issue is deeply iconic.

> CCC always has been explicit far left/green, looking at its history, as other people in here have mentioned.

Yes, but what has shifted is "the left", to a point were it has basically been taken over for very specific agendas.

> I suspect that Chinese models are largely forced to open source as a trust building step because of general China-phobia in the west.

The obvious bias of the models, when it comes to Chinese politics and history, certainly does not help here.

I do not understand. If auth is bypassable, this is not a browser issue, right?

It's also a fundamental problem of security research. Lot's of irrelevant, highly contextual "vulnerabilities", submitted to farm internet points (driven by a broken cve system). AI only amplifies this.

Pulling unvetted stuff from docker hub, npm, etc. is not a question of redundancy.

Because you should not depend on one payment provider and pull unvendored images, packages, etc directly into your deployment.

There is no reason to have such brittle infra.

Well, some engineer somewhere made the recommendation to go with AWS, even tho it is more expensive than alternatives. That should raise some questions.

If you are running k8s on prem, the "easy" way is to use a mature operator, taking care of all of that.

https://github.com/percona/percona-xtradb-cluster-operator https://github.com/mariadb-operator/mariadb-operator or CNPG for Postgres needs. They all work reasonable well, and cover all the basic (HA, replication, backups, recovery, etc).

This is blatantly false. There are MLIR based backhands for other languages. This is explicitly mentioned on the landing page at https://developers.googleblog.com/en/introducing-coral-npu-a....

Please language troll somewhere else.

Looking at the state of the original Coral TPU (which was basically abandoned, just like regular other Google stuff), would make me very wary to use this is a long term product.

People like to think that they are anti-establishment and disruptive at a startup. They conveniently ignore who is writing the cheques.

Care to ellaborate? Not shitting on libavcodec here, I would also guess it just beats a new project on raw performance.

But according to the repo, this project also uses both slice and frame multi-threading (as does ffmpeg, with all the tradeoffs).

And SIMD usage is basically table-stakes, and libavcodec uses SIMD all over the place?

They are not complaining about the price, but about the closed source nature of the product.

And this is particularly painful, if you actually need to run, build, and test on old OS versions, that come with old Node versions.

> No amount of internal review and coding standards and etc will catch all of these things. You can only hope that you build the muscle memory to catch most of them, and that muscle memory is forged through being punched in the face

Everything you mentioned is security 101, widely known, and can be caught by standard tools. Shrugging that off as a learning experience does not really hold much water in a professional context.