@ictinus_x Don't forget people, this guy is an avid expansionist Megali Idea dreamer. Don't let him fool you when he talks as if he desires normalization, like here:
https://t.co/FouvTaHWfV
If this is truly “the most friendly period in recent years,” then now is precisely the moment to demonstrate it through action-not words alone.
The immediate and unconditional withdrawal of Turkey’s threat of war (casus belli) against Greece would be a meaningful step toward peace and de-escalation.
What do you think ?@cuneytozdemir
With AI what would have normally been 2 hours of study, 2 hours of white board, and about 6 hours of programming has been compressed into 7 2 hour sessions that have gone in the wrong direction.
Truly alien technology
@alfondotnet@encrypted You are absolutely right to pushback, I'm sorry. Do you want to learn about how to uninstall pnpm — that's the #1 culprit for "my agentic orchestrator accidentally installed pnpm package with config.minimumReleaseAge=0 override and infected my development computer with malware".
Ben bu demoların maksadını anlamıyorum, eğer ki full fledged bir işletim sistemi değilse o zaman neyi kanıtlamış oluyorlar ki? Aynı şekilde Anthropic'in compiler muhabbeti de öyle, C compiler'ı "yazdı" ama yani "yazmak"ın tanımını değiştirdiğimiz zaman yazdı diyebiliyoruz. Yani "ooo işletim sistemi yazdık ve doom oynattık" hype'ı var, fakat altını kazıyorsun, kullanılabilir bir şey değil. O zaman gerçekten komplike task yapmayı kanıtlamış oluyorlar mı? Yoksa average Joe'un zor bildiği şeylerden birisi işletim sistemi yazmak diye onlara karşı yapılan vasat bir marketing mi bu?
The CEO of Take-Two, the company behind GTA, just said something the entire AI industry doesn't want to hear.
And he said it without being anti-AI.
Strauss Zelnick's argument is precise. AI is built on datasets. Datasets are backward-looking. Creativity is forward-looking. A model trained on everything that already exists cannot, by definition, produce something genuinely unexpected. And all hits, by their very nature, are unexpected.
Asset creation and hit creation are not the same thing. AI is getting very good at the first one. The second one is what actually makes money, builds franchises, and changes culture. Nobody has shown AI can do that yet.
The derivative property problem is real. You can clone GTA with existing technology. You could do it before AI. It would take 3 years and look identical. It still wouldn't sell. Because it isn't GTA. It's a clone of GTA.
And consumers, despite what the industry occasionally pretends, can feel the difference between something genuinely new and something assembled from the residue of things that already worked.
Thousands of mobile games ship every year. 0 to 5 hits get made. The same studios make them every time. The technology to make more games has been commoditized for years. It didn't democratize hit creation. It just flooded the market with more forgettable product.
The Silicon Valley thesis that AI unlocks game creation for everyone is true in the same way that cheap cameras unlocked filmmaking for everyone. They did. And the same 5 studios still make the movies everyone watches.
What Zelnick is saying, without quite saying it, is that the thing AI cannot replicate is taste. The instinct for what hasn't been done yet. The cultural antenna that detects the gap in the market before the data can see it.
Data tells you what people wanted. Hits tell people what they want next.
Those are different jobs.
@ZPostFacto@livebeef You are not "agentic programming" I suppose? I think that is the missing link here, people who are against "AI assisted programming" are usually against agentic.
@OlexGameDev@Wassimulator It is by design, but still, this is done in industrialized way right now, in a way nobody was expecting to see in their lifetime. I understand the complaints.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.