I sure don't miss the footguns and raw boilerplate that is having a copy constructor, move constructor, copy assignment operator, move assignment operator, and destructor, per class.
Yes, you should avoid the manual memory management that necessitates writing them. But work with a team of developers fresh out of school and next thing you know your codebase will be brimming with this kind of busywork.
> After seeing a brief demo of a grotesque zombie-esque creature
Reacting to an animation where a gross critter "learned to walk using AI" instead of being animated by a person 8+ years ago, and ended up using its head as a leg
It has nothing to do with the current image generation topic beyond the "AI" label being stuck on both of them
Which is not to say I expect he's thrilled about ChatGPT cloning the art style on a mass scale, but that quote that everyone keeps reposting doesn't have anything to do with it
If you continue the quote, he says: "I would never wish to incorporate this technology into my work at all. I strongly feel that this is an insult to life itself."
He was pretty clearly talking about AI, at least to me.
Not at all - he was talking about a CG demo he'd just seen of a wriggling 3D model, which didn't bear any technical or visual resemblance to generative AI.
I mean, the quote might very well reflect his actual views about generative AI, but that's definitely not what he was talking about.
The purpose of that demo was to create a machine that can draw like humans can, as the creators explained. His objection was that whatever produced this had no concept of pain, and that’s what makes it grotesque. He called out that he had no objection to creating horror if that’s what the authors wanted to do.
That complaint is just as applicable to current Gen AI models. He wasn’t simply reacting with his gut to a gross looking video but to the concept of a thing with no concept of pain creating and animating artwork of living things. He understood the technology was about Gen AI, as “deep learning” is written on the whiteboard. He deserves some credit.
> The purpose of that demo was to create a machine that can draw like humans can, as the creators explained
Watch the video - the purpose of the demo, as the creators explained it, was to train a creature to move quickly. Since the AI model didn't simulate pain it used its head like a foot, and since the result was creepy they thought it could be used for a zombie game. That's what they presented to Miyazaki, and that's what he commented on. Then Suzuki asked where they eventually wanted to end up, and a different presenter said the thing about machines that can draw.
> That complaint is just as applicable to current Gen AI models
If you like, but that's not what Miyazaki applied it to.
> Watch the video until the end where they say this explicitly
1. The person who says that wasn't describing the purpose of the demo
2. He says it after Miyazaki's comments, ergo Miyazaki was not commenting on it
> - "Here, Mr. Miyazaki -- we have made a fast-moving zombie!"
Please don't sarcastically put words in the mouth of the person you're replying to - it's rude and it's never useful. All my previous comment did was summarize what was said, in the order it was said. I didn't suggest it was anything more or less than the words in the transcript.
It is really depressing to see how people universally don't even understand what he's talking about, and stick to non-explanations.
Art is humane. It tells humans how to be humans. A thought about an ill person in pain is worthy of being told as a story. Not only that animation automation thing is of no use to someone trying to express those thoughts, its authors — just like many, many others — have no idea what humans do with their lives, and which tools artists may need to show it. They've made a toy, and were told that it's just useless wanking, together with the whole genres of pointless amusement that introduced such images into pop culture.
“An insult to life itself” is not just a phrase. There is life, and there are people who deliberately ignore it, and enjoy the sights painted on cardboards.
"After seeing a brief demo of a grotesque zombie-esque creature, Miyazaki pauses and says that it reminds him of a friend of his with a disability so severe he can’t even high five. “Thinking of him, I can’t watch this stuff and find [it] interesting. Whoever creates this stuff has no idea what pain is whatsoever. I am utterly disgusted. If you really want to make creepy stuff, you can go ahead and do it. I would never wish to incorporate this technology into my work at all. I strongly feel that this is an insult to life itself.”
He's disgusted by the creature, not the computer based technique. While he's on record as disapproving of CGI, Earwig and the Witch, directed by his son, used CGI so his disapproval isn't absolute.
"Whoever creates this stuff has no idea what pain is whatsoever."
I think it's clear that he is specifically responding to the the overall soullessness of the technique - to animate without a human understanding of what is being animated. But as others have pointed out this is well before modern AI image gen and I have been corrected in that aspect.
Presenters: "This is a presentation of an artificial intelligence model which learned certain movements [...] It's moving by using its head. It doesn't feel any pain, and has no concept of protecting its head. It uses its head like a leg. This movement is so creepy, and could be applied to zombie video games. An artificial intelligence could present us grotesque movements which we humans can't imagine."
The screen shows some Silent Hill looking vaguely humanoid, crawling blob. As the presenters say, it's pretty creepy looking.
Miyazaki: "I am utterly disgusted [...] I would never wish to incorporate this technology into my work at all"
IMHO saying Miyazaki outright hates AI is putting words into his mouth. All the clip shows is that a dude that doesn't make zombie horror films doesn't need a zombie horror generator thank you very much.
So yeah, he clearly rejects the product pitch. But judging from Kiki's Delivery Service and My Neighbor Totoro I don't see why you'd pitch him that product.
"Well, we would like to build a machine that can draw pictures like humans do"
"Would you?"
"Yes"
Awkward silence
From this I don't think it's difficult to extrapolate his feelings about modern AI image gen. But you are correct in that this is not a direct assessment. Appreciate the correction, thanks.
Not to mention, 99^6 = 941,480,149,401 ≠ 99,000,000 (which TFA also quotes). But who's to say notation didn't degrade along with the rest of society? :^)
I hear you man. The fact that a `byte` in ROS's bootleg protobuf is actually signed, and `string` is ASCII-only means that if you want to send a file or binary blob you have to use a `uint8[]`, which of course C++ will turn into a `std::vector<uint8_t>`. Good luck turning that into a proper `std::string` without an extra copy. And don't get me started on the comically scattered documentation for any basic use case that only ChatGPT can seem to make sense of. Better yet, the complete insanity that is node parameters - ever heard of reading from a file? Can't believe anyone takes this seriously.
ZeroMQ, protobuf, and a little thought would go a long way at our org.
It's fantastic when embedding Lua in a self contained executable too! I have a routine that goes through and 'cdef's certain headers that were also #included at compile time. Super powerful extending a C program this way.
It doesn't run the preprocessor, so you have to expose constants as externs, for example. Things like `int32_t` still work, so it must just have built in support for standard types.
Cargo is i) not a compiler, and ii) moving to the sparse index protocol [1] that do not fetch the whole index anyway. And even the older git protocol won't fetch the same data twice.
As a fairly avid Rust user I can say I'm excited to hear that! Just playing a little devil's advocate for fun.
That said I was moderately upset by this Friday after carefully assembling a development container for a project at work. Guess I'll have to make something persistent somewhere if I don't want to twiddle my thumbs before each build.
Yes, you should avoid the manual memory management that necessitates writing them. But work with a team of developers fresh out of school and next thing you know your codebase will be brimming with this kind of busywork.