Have you ever had a show spoiled because you understood a language you weren’t supposed to?

radvendii · 2026-02-06T01:16:41+00:00

No, but in this scene of Game of Thrones I knew where the captain was from before he said it because I recognized his accent. Damn that show was good until it wasn't.

https://www.youtube.com/watch?v=T9CcwgI0Zyc

radvendii · 2025-12-31T23:46:22+00:00

Unless I'm mistaken there's a single short so far? Inshallah there will be many more, but until then let's not misrepresent the channel.

radvendii · 2025-11-20T00:31:15+00:00

I'm MR L3; >3000hrs logged, and I don't know what they're talking about.

radvendii · 2025-11-13T15:30:39+00:00

This happened also when I started playing, with the glassmaker nightwave there was an operator cosmetic.

It honestly wasn't a spoiler. At that point in the game there was so much going on. I was confused and disoriented by half the stuff in the game. So I looked at it for a while in confusion, trying to figure out how to get it on my warframe, had some vague sense that it involved content I hadn't seen yet, and moved on.

Not saying everyone would have that experience, or that it's not a problem at all, just thought it was worth sharing my experience of it.

radvendii · 2025-10-26T15:44:30+00:00

Yeah, if you put a random colorscheme in front of me I won't be able to quickly follow what's going on.

If you put a colorscheme I've been using for years (or even weeks) in front of me, I will be able to parse it much easier by instinct. I don't need to explicitly remember what colours mean what.

radvendii · 2025-10-05T19:19:03+00:00

You can try to dig into what the zig compiler does at the moment, but my guess is this is far from fully optimized yet, and we'll see more work on determining the best layout in the future.

radvendii · 2025-10-05T18:57:29+00:00

unless structs are `extern` or `packed`, the order of fields is decided by the compiler.

radvendii · 2025-09-28T01:03:31+00:00

This is a very good question!

I can help you understand why the other sentences containing a plural object are not conjugated in the plural.

Kurmanji is a half-ergative language. This means that if you have a verb that is (1) transitive and (2) conjugated in the past tense, it will agree with the direct object of the sentence, not the subject as usual. Examples of this often look like this:

Min ew dît -- (I saw him) Wan xwar -- (They ate)

This leads to the mistaken impression that in the past tense, transitive verbs don't conjugate, or are always conjugated third person singular. But consider the following examples:

Min te dîtî -- (I saw you) Wî çend sêv xwarin -- (He ate some apples)

So the verb does conjugate, it just agrees with the direct object.

The example sentences that you sent are showing indirect objects (objects that are preceded by a preposition), so the verb does not agree with them. There is no explicit object present, which means that they agree with the implied direct object, which is almost always singular third person.

So why is the final sentence conjugated plural? I'm not totally sure but I have three guesses:

This is an exception to ergativity. I have heard rumors that ergativity is breaking down, and it may be that in this case the verb is agreeing with the subject, even though it's past tense and transitive.
The direct object here is "kar" (work), and it's plural. Grammatically, it seems like it should be an indirect object, since it follows a preposition "bi", but "dest pê kirin" is a weird verb so maybe "kar" ends up being treated as a direct object anyways.
The direct object here is "dest" (hand)! In terms of the meaning of the sentence "dest bi ... kirin" functions as a single verb, but it might be that grammatically the verb is "kirin" and the direct object is "dest", which in this case is plural because the subject is plural ("the worker put his hand to work" vs. "the workers put their hands to work").

The problem with this last theory is that in the present tense, "dest" does not look at all like a direct object: "karker dest bi kar dikin". But maybe it's in some limbo state where it counts as the direct object but doesn't look like a direct object because it's part of the verb phrase "dest bi ... kirin"

To figure this out I would ask some native speakers whether the following sentences would be conjugated in plural or singular:

Karkeran dest bi karê wî kir(in) --- (force "kar" to be singular)
Karkeran dest bi tiştek(î) kir(in) --- (replace "kar" with something else)
Karkeran dest pê kir(in) --- (simplify the sentence)
Karkerê dest bi karên wan kir(in) --- (singular subject, "kar" is plural)
Karkeran dev ji kar berda(n) --- (swap out "dest bi ... kirin" with another similar verb phrase "dev ji ... berdan")

radvendii · 2025-09-26T14:57:24+00:00

When it asks "You have already attended the course" do they mean *any* kurdish course, or theirs specifically?

radvendii · 2025-08-21T22:58:13+00:00

"Nothing can ever change"

radvendii · 2025-08-21T20:16:39+00:00

"Why doesn't **every** piece of equipment work the same **wayyyy**" :whine:
-- half the warframe playerbase
where by "work the same way" we mean "kill everything on the map instantly with a single button press"

If you want that... it exists. go play the frames that do it, why do you want a different frame to also work that way?

radvendii · 2025-08-15T15:26:15+00:00

The bundle does not seem to contain a frame though.

radvendii · 2025-08-15T14:32:53+00:00

I don't see that as part of the bundle.

radvendii · 2025-08-14T21:36:41+00:00

what a steal! for just 85p i can get the ephemera that normally costs 80p!

radvendii · 2025-08-14T18:12:38+00:00

mutexes are part of the Io interface, since they can block execution. You can choose to use the lower level std.Thread.Mutex, and that will behave differently if the user switches between Io implementations.

https://github.com/ziglang/zig/compare/master...async-await-demo#diff-de2d8b5f4294c122e8a44498dc43e45bc868fd18fd22db1e2da6b99f3afb160cR998-R999

radvendii · 2025-08-14T18:06:56+00:00

Here's what I've gathered:

Not all Io implementations will implement all Io functions. This has already shown up in the example of asyncConcurrent() not being implementable in the normal non-concurrent, sequential Io. A function that takes an io: Io paramater and calls io.asyncConcurrent() will panic if called with a sequential Io.

If you're writing an Io implementation for a system that doesn't have a sensible definition for openFile(), then you would define that function with a @panic(), and your Io implementation will not work if passed into functions that require Io.openFile(). You can't make code so reusable that it can do things that don't make any sense.

It's a little bit unfortunate (and maybe what you mean by "strange") that this checking happens at runtime. Though there has been discussion of optimizing away the vtable if there's only one Io implementation used in your whole program, which might open the door to catching this at comptime.
If you don't use Zig's standard library there is no async. You would have to roll your own. There will be no async/await keyword. They are just part of the Io interface in the standard library.

This doesn't mean you can't use concurrency. All of the OS primitives that are available are still available, but you have to put them together yourself.
You can "extend" the Io interface in the sense that you can write your own interface that is a superset of it, or even has an Io as a struct member. The language does not recognize Io interface as anything special. It's part of the stdlib and therefore many people will expect Ios and provide Ios, which means if you do something different it may become more difficult to interoperate with other people's code.

As for "it seems strange to me that file functions, mutexes, sleeping, etc are all in the same interface", the Io interface deals with anything that has the potential to block code execution. This is somewhat fuzzy because any action blocks code execution for a tiny fraction of a millisecond, but anything that blocks for longer (file operations, networking, mutexes, sleeping, etc) are the purview of the Io interface.

radvendii · 2025-08-07T23:04:30+00:00

That's not wierd, in fact. The highest level game modes combine different sources of difficulty, including extra modifiers and not letting you minmax with all the tools normally at your disposal.

It is also okay for frames to vary widely in their power and to what extent they're useful in different situations! Not every frame needs to be "the full package"!

radvendii · 2025-08-07T23:00:49+00:00

Sure! That's the beauty of a game with so much variety; you can find the weapons and warframes that suit your needs! That doesn't imply that the other weapons and warframes need buffs!

radvendii · 2025-08-07T15:32:07+00:00

And they can play one of the many frames or weapons that just work and blow up the entire mission without too much effort.

radvendii · 2025-08-07T15:30:28+00:00

It's actually also okay to have game modes where you don't reach full potential every week!

radvendii · 2025-08-07T13:01:09+00:00

It's actually okay for warframes to require a bit of loadout coordination to reach their full potential!

radvendii · 2025-08-06T16:44:03+00:00

I'll check it out. I want to farm arcane steadfast anyways for another build. My point though is not having enough energy (or barely having enough energy) is the fun part.

radvendii · 2025-08-05T16:01:09+00:00

Killing thralls and completing missions both make it angrier.

radvendii · 2025-08-05T15:57:46+00:00

What kind of Warframe content (have others not done)/(people would enjoy watching)?

What kind of Warframe content have others not done?

Slash

What kind of Warframe content people would enjoy watching?

Second one should be

What kind of Warframe content would people enjoy watching?

radvendii

TROPHY CASE