To others yes, but not to you. It can be impossible to prove to an idiot that they are an idiot, but you do realize others read Slashdot, right? Or are you an even bigger idiot than it at first appears?

Zig isn't ready for AI because AI isn't ready for Zig. There is a bootstrapping problem. Quality training data is limited because it is new, and many humans don't yet have the experience needed to be good at it.

Since Zig is newer, developers are often learning the language alongside the AI. A novice developer might accept an AI's bad allocator usage or improper async handling simply because they lack the expertise to audit it properly. This creates a situation that causes AI to be less effective when using it for Zig development when compared to C and C++ development efficacy, even if they review proposed changes prior to submission of the pull request. Citing Zigs experience as indicative of a global condemnation of AIs usefulness in a software development context represents a complete failure to look at the big picture and place the facts in context. One can use an AI to explore this further.

After thinking a bit about this I asked Gemini (free version) "I am trying to determine if AI generated zig code would likely be of poorer quality than C code due to a few factors. One is that zig is new so many developers may not be very skilled with it, and another is that there is limited training data as compared to C or C++." It had a lot of insightful commentary on my point. In fact there was far too much to copy and paste here, but anyone interested can do so if they want to explore my point (made primarily in the first paragraph of this post) further.

An example that a lot of people don't understand how to use AI properly is not an example of proof that AI is useless or flawed and produces trash and reduces efficiency. As with any tool, when used properly by skilled people it is a good thing, and when misused by people with no training in its use it can be counterproductive and sometimes destructive.

Assuming a correlation between Slashdot UID and the users age and experience calls into question your software development skills.

Nobody knows that because you just pulled that claim out of your ass.

I have no idea what you're doing with your phones, then.

The only Android phone that I used for any length of time was a Nexus 4 and it would die in 1 hour when I went to the pool because it would burn all of its energy desperately trying to get a signal from inside a locker.

My current iPhone 16 Pro lasts the whole day unless I'm using it actively and playing a game on it. It has notoriously poor battery life under load because it's not well cooled, but when idle? Days of battery life. I've been on trips where I've tossed it in my bag and not gotten back to it for hours, and the battery has basically not moved, even WITH the radios on.

Yes, that they're mad that you don't understand what a union is.

I'm not gonna make any claims that unions are perfect, but a union is just a way for a collection of workers to have more leverage for bargaining rights. The most prosperous times for workers in the last century have been during times of heavy unionization.

Reagan busted the unions, and with them, he busted middle-class prosperity. As is often said, we owe weekends and the end of child labour to unions.

As a long-term worker in the industry, I'd love a union, particularly if I were to go back to work at one of the huge game companies like EA (ugh) or Rockstar or Blizzard.

Not especially. Remember, Google pays Apple about $20 billion/year to be the default search in Safari. The reports are that Apple pays Google $1 billion for Gemini.

And if we're honest, Gemini is not the clear-cut best model, it's just that Google and Apple already have a pretty good relationship. Given the amount of Capex Google is putting into AI/Gemini, they need to make money from SOMEWHERE, and Apple is a reliable partner. I'm sure they're extremely relieved that Apple is going with them instead of Anthropic. Though, indeed, there's no reason for Apple to only rely on one vendor.

This whole thing shows that LLMs and models are already being commodified. Who knows if some of these companies will ever make their money back.

There's no such 'well known fact'. Apple Phones have historically had some of the best battery life in their generations, with occasional outliers. (If we compare the latest Samsung vs. the latest iPhone, for example, the iPhone has significantly better battery life.)

On the other hand, there are occasional Android phones with absolutely absurd batteries that last a couple days on a charge with the tradeoff of looking like a pound of butter. The fact that these have better battery life is not surprising and is the actual outlier.

Crucially, in all but a few languages, whitespace doesn't matter at all. The parser throws it out.

Whitespace is a HUMAN affordance for a HUMAN audience. If you think it looks kinda okay, that's all that's needed. You absolutely cannot do that with code that actually does something.

I suppose, fundamentally, all code is for humans to read; the CPU doesn't care how the bits got organized. But LLMs can't just jump straight to the compiled output, they have to come back to the intermediary of human-readable language, and that means they're bound by the limitations of the languages we've asked them to write in. That also means that they write bugs and bad code because they're trying to produce readable tokens that possibly do the thing you ask, and they're not writing the code and testing it and refining it in a tight loop before delivering it.

When I write code, a function may see multiple passes before I even show it to anyone else. If you don't understand the output the LLM is giving you, but it compiles and vaguely does the thing that you ask, you might take it at face value on the first pass. And since the code is only receiving "yeah, that looks right," level scrutiny, it's so much more likely to be bad.

It won't.

Making games isn't actually that easy? I've been doing it for 25 years, and making a game that's good that people enjoy requires, in no small part, that you yourself enjoy playing games, and that you understand what fun is.

It's not just the designers that make games fun, either, even if they're responsible for a lot of the mechanics. Every breakdown of job responsibilities I've ever seen (which we use come review time) has something in it about how you understand game mechanics and your ability to make contributions in that regard, and that's regardless of whether you're in design or art or programming. As a programmer, I'm not tasked specifically with making the game mechanics--I'm there to make a platform for designers to execute their vision--but I have made changes independently that have shipped effectively untouched in the final game.

So all that to say, if you use AI to write your games and you're not a solo designer, your games will probably be worse. The bigger the game gets, the more you'll feel the lack of scrutiny from individual contributors. Any of the small, interesting, fun details you've played in a game up until now was almost certainly put there by a real human that wanted that to be in a game themselves.

There's a possibility that AI will make my job easier or make me a bit faster, but I'm not losing my job to AI (though a greedy CEO may blame it on AI). There are ALREADY a zillion games out there. The barrier to making games is low. If all you want to crank out is slop, bad news: humans have been doing that for decades now. Slop by an AI agent isn't actually going to do any better.

Sure, so why are you bringing your feelings into this?

You actually have no evidence that he's never asked, "how do I avoid memory bugs in C?"

If I had to make a bet, I'd say literally every programmer that has spent a non-trivial amount of time in C has asked that question of themselves, even if only in passing. It is a constant fight, but it's also a deeply stupid fight to have if you have a tools--including a whole, purpose-built language--that allows you to elide that fight almost in its entirety. Like, you can CHOOSE to do it for fun if you like, but if your goal is to write memory-safe code, use all the tools at your disposal.

I'm a C++ programmer (that's what the games industry runs on) and I have the extreme privilege of only having to worry about keeping games from crashing, the most trivial kind of memory safety. It's a deeply stupid language (IMO) that has only gotten better by poaching the best parts of other languages. But I'd love to not ever have to think about weird crashes that are caused by people kicking the stack 5 minutes ago in some other game system. If I was told that Unreal Engine was being fully reinstrumented in Rust, I'd learn Rust. What a relief it would be.

Anway, tl;dr: you're the one that's got feefees about this. Rust is a demonstrably safer language in real-world use. For you to rail against it this much is just your feelings, not anything to do with facts.

I wouldn't mind if it were a static image, but it's that Gemini ad that's constantly writing and erasing text. It's definitely cut down how long I stay on the site.

No, those are the words of someone who has seen nothing but slop for more than a decade (OK, there were a couple of exceptions), and has reached the point where there is no expectation things will ever get better. I have also given up hope that Star Wars will ever be good again.

I expect your opinion, which I share, is a majority opinion. Star Wars is almost nothing but slop now.