That was the UK.

The concern: “Why aren’t we in on it?”

It’s not a bug, it’s an unimplemented feature. The !community@instance syntax is not part of any Markdown flavour, so every client has to implement it independently, and it’s possible that it collides with some other kind of token (e.g. with the @user tag).

Finishing a Dark Souls game.

And finishing a Dark Souls game.

You should also look at which processes use the largest amount of memory. ZFS is weird and might allocate its cache memory as “used” instead of “cached”. See here to set its limits: https://forum.proxmox.com/threads/limit-zfs-memory.140803/

The most useful is probably cat /proc/meminfo. The first couple of lines tell you everything you need to know.

• MemTotal is the total useful memory.
• MemFree is how much memory is not used by anything.
• Cached is memory used by various caches, e.g. ZFS. This memory can be reallocated.
• MemAvailable is how much memory can be allocated, i.e. MemFree + Cached.

“It’s just one goto, what’s the worst that could happen?”

let you build faster like Python

I have to write so much boilerplate code to make sure my objects are of the correct type and have the required attributes! Every time I write an extension for Blender that uses context access, I have to make sure that the context is correct, that the context has the proper accessor attributes (which may not be present in some contexts), that the active datablock is not None, that the active datablock’s data type (with respect to Blender, not Python) is correct, that the active datablock’s data is not None… either all that or let the exception fall through the stack and catch it at the last moment with a bare except and a generic error message.

I used to think that static typing was an obstacle. Now I’m burning in the isinstance/hasattr/getattr/setattr hell.

@Mods, please don’t delete this. It’s a valuable lesson.

It’s a combined disability discount: people with hook hands, peg legs, and eyepatches may be entitled to a price as low as 0%.

Nintendo sees rock bottom as a challenge.

The rules are on the same page I linked (https://www.indiegameawards.gg/faq), under the “Game Eligibility” tab. I gave them the benefit of doubt and assumed that they had defined the exact terms of what is and isn’t allowed, but apparently I was wrong. Regarding AI, the document contains a grand total of one sentence:

Games developed using generative AI are strictly ineligible for nomination.

I’m assuming the definition of what that entails is “at their discretion”, meaning whatever they feel like at the moment. I see that sentiment reflected in this thread too.

It’s possible that potential nominees have to sign some kind of declaration that they’ve complied with the rules, and that might include a more detailed list of rules, but I have no evidence to support this.

Unfortunately the boundary between “AI” and “not AI” is the polar opposite of sharp and well-defined. I’ve used Allegorithmic Substance Designer a lot for CGI work (before Adobe ate the devs; fuck Adobe, all my homies hate Adobe), and it contains a lot of texture generator algorithms from simple noise to complex grunge textures. Things like Perlin noise and Voronoi diagrams are well-known algorithms and definitely not AI. Chatbot slop is right out, but in between those two, things get remarkably fuzzy and Heisenbergian. What about an algorithm that uses real-world samples, like an image? Or multiple images? Machine learning is not the same as AI, so is that allowed? Where’s the line? I’m reasonably certain that everybody has a different answer for different situations based on different criteria.

The issue is not that the game was disqualified. If the rules clearly and unequivocally state that at no point can generative AI be used (and also clearly state what, in the spectrum from algorithms -> machine learning -> chatbot slop, they consider to be unacceptable, which I don’t know if they did or not, guess what, they didn’t, but that’s not the point), then there is no controversy, and I’m not criticising that.

The issue is that the article completely disregards mitigating facts that counter the narrative. There are no credible sources linked in the article save for one that was grossly misrepresented. Critically, we don’t know what Sandfall actually said before the nomination or after, or how the decision to disqualify was made, only the second-hand account in the FAQ. The article presents circumstances in a biased way, leading the reader to interpret it with the assumption that there are AI-generated assets currently in the game. It is, frankly, sloppy journalism.

Horrid article, unless the intention was to throw shit around and hope to cause a commotion. There are no AI assets in Clair Obscur, and it should have been made clear by the article. From the IGA’s own statement:

[…] the use of gen AI art in production […] does disqualify Clair Obscur: Expedition 33 from its nomination. While the assets in question were patched out and it is a wonderful game, it does go against the regulations we have in place.

For fuck’s sake CA, please let me give you my money

This isn’t about some feature of the language being good or bad. It’s about Rust being ugly or not. The things I mentioned will always look ugly in the source code.

Enums and nested blocks. I understand the importance of Option and Result, but it’s fucking infuriating when I have to check and destructure the result of every function call and either bubble the result up the stack from six levels of nested if let blocks or risk Cloudflaring my program by using .unwrap(). And while I like being able to extract a return value from an if...else expression, the structure gets really convoluted when multiple if and match blocks are nested (of course each one returning a value), and it gets completely fucked once closures are introduced.

I like Rust, but calling it pretty is delusional.

Network Chuck’s earlier videos are pretty good, especially the You Suck At… series.

Unfortunately he’s been pushing AI shit lately.

15000 rows. 120 columns. One sheet. Creation date: 2011. A dedicated computer. Working at a multinational company is bad for mental health.

You know it doesn’t have to be all or nothing, right?

In the early design phase, for example, quick placeholder objects are invaluable for composing a scene. Say you want a dozen different effigies built from wood and straw – you let the clanker churn them out. If you like them, an environment artist can replace them with bespoke models, as detailed and as optimized as the scene needs it. If you don’t like them, you can just chuck them in the trash and you won’t have wasted the work of an artist, who can work on artwork that will actually appear in the released product.

Larian haven’t done anything to make me question their credibility in this matter.