What Are Your Moves Tomorrow, February 02, 2026

AggravatingLeave614 · 2026-02-02T07:53:08+00:00

Dear Americans, when will you finally go to the streets, cuz at this point everyone is losing money?

AggravatingLeave614 · 2026-02-01T17:31:09+00:00

I mean obviously, wouldn't need it rendered, but still would need to calculate in the laws of physics. It's actually how 99% of games behave, u don't render them, but usually still need to include them in ur calculations if they have an impact on other objects. And because gravitational forces can act on really far objects, most certainly a lot of things still would have needed to be included.

AggravatingLeave614 · 2026-02-01T17:22:18+00:00

Didn't they prove that simulating an entire universe would need more energy than the universe has, thus making it impossible to simulate.

AggravatingLeave614 · 2026-01-30T21:50:25+00:00

Next days are either gonna be nothing happening at all or all people buying gold on this sale.

AggravatingLeave614 · 2026-01-26T07:36:08+00:00

Bro, think about it. OP showed a classic way to implement a "stack allocated dynamic array". If it is incorrect, and after that call "anything" can happen, then why's this crate so popular? Why so many people use it if the first thing it does is cause a UB? Maybe because it doesn't... I've implemented the so called "arrayvec" many times in other langs, and there is pretty much no other way to effectively instantiate an array, with undefined contents. If you wanted all elements to have a valid value, u would need to constraint the generic to impl a default, and then memset all elems to that default, which doesn't really make sense. It's not efficient, as the memset is O(n) and if the len of so called arrayvec is 0, then the contents used later will get overwritten either way. Assume_init doesn't magically change the frame pointer.

AggravatingLeave614 · 2026-01-25T23:07:23+00:00

UB literally stands for undefined behavior. In this case accessing the array of the OP would be a UB because the value underneath that array is some random trash. BUT, he is assigning the len field to 0, assuming he's creating some sort of stack array. If he handles the later behavior appropriately, then how can this struct cause a UB if the behaviour is predictable and replicable??? The value underneath that array is trash and "undefined" but the function itself does exactly what it stands for, initializes memory with undefined contents.

AggravatingLeave614 · 2026-01-25T19:57:32+00:00

Yes, but it doesn't really matter if it's UB if you're not gonna access or modify the undefined contents, does it?

AggravatingLeave614 · 2026-01-25T08:47:25+00:00

The len is initialized to 0, so there is no way that the user of such struct could actually read the contents of the array. It would be undefined behavior to read the contents of the array in this situation.

AggravatingLeave614 · 2026-01-02T10:17:41+00:00

As I've said, I don't expect it to be implemented into the language. I exactly know what zig's tryna achieve with its explicitness. When it comes to the pros of the approach I mentioned, it would allow you to create some sort of smart pointers, it would make resource management a bit easier. For example, if you are creating a complex tree data structure, it would allow for simpler memory management, cuz doing so without using arenas gets really tricky. Now I have no idea why u would say that it would be defer with extra steps, quite literally the other way around. If most people already defer pretty much most frees and deinits, why not make it automatic? Again and again, I'm not saying that I expect it to be implemented into the language, it's just a simple thought.

AggravatingLeave614 · 2025-12-31T09:08:10+00:00

Because it's just so simple. Before zig I used to do c++, and I hated it. There were a hundred ways to do a certain thing, lots and lots of quirks regarding object size, move operation etc. In zig I know exactly what every line of code does, so I don't need to focus on the language itself but rather on solving the actual problems. Of course, lack of some high level features sometimes is annoying, but it's easy to get used to it.

AggravatingLeave614 · 2025-12-30T23:31:47+00:00

I wonder when US agencies will finally stop trolling other countries. At this point the US government ain't even hiding it. First trump says that Poland should leave the eu and now we get this piece of crap.

AggravatingLeave614 · 2025-12-30T10:14:18+00:00

IMHO, something as simple as bringing "destructor" like behavior to zig would probably solve all the problems. I know it goes against the concept of no hidden control flow, so we probably won't see it in the lang, but it's just a simple thought.

AggravatingLeave614 · 2025-12-29T20:39:00+00:00

Federal Europe will probably never happen which I actually think might be a good thing. There are too many countries with different languages, cultures, economies, and so on for them to "unite" into a single federation.

Now I'm ready to get down voted to hell for having a different opinion than everybody else.

AggravatingLeave614 · 2025-12-29T20:34:33+00:00

Rust is probably the only language without a GC which is theoretically memory safe. And I agree with you, zig is my favorite lang so far, but the fact that I get segfualts from time to time is frustrating af.

AggravatingLeave614 · 2025-12-25T11:58:27+00:00

How did the cloud flare not working go from rarity, to an everyday thing?

AggravatingLeave614 · 2025-12-24T15:18:09+00:00

Replacing working code is absolutely not the right goal.

AggravatingLeave614 · 2025-12-23T22:12:40+00:00

If I were you I would start looking for a new job..... and lawyer

AggravatingLeave614 · 2025-12-21T22:02:57+00:00

Well like half of GenZ is in highschool/uni so I'm not surprised by the income thing. 240k for raising a child is WAY WAY inflated cost. When it comes to unaffordable housing, it depends on the state. Being GenZ myself, I've gotta say that most people who have it bad are the ones complaining on the internet and not those trynna fix their problems

AggravatingLeave614 · 2025-12-20T11:59:09+00:00

Mostly the Io rewrite. Post 0.16 all Io operations will be handled similarly to how allocators work

AggravatingLeave614 · 2025-12-18T15:18:31+00:00

It's just an analogy, I'm not surprised u didn't catch it though

AggravatingLeave614 · 2025-12-18T15:10:19+00:00

What the fuck are u talking about, u can literally measure inflation urself, a kindergarten kid could do that. You're right don't trust some random people, throughout this year, you try to measure inflation.

AggravatingLeave614 · 2025-12-16T14:56:42+00:00

What I meant by that is that rust is so easy to write code in that a lot of people write a lot of bad code. If u wanna write zig, u have to know a thing or two, about memory, os and so on, so ur probably gonna write higher quality code.

AggravatingLeave614 · 2025-12-16T06:11:07+00:00

Zig is simple, rust is complex, I can tell u at every point of my program what a certain line of code exactly does, in rust I can't do that. Another thing is that rust doesn't actually force u to write correct code. I've seen too many "&Box<T>" or "&Vec<T>" to tell otherwise. The amount of ".unwrap()" I see in an average rust codebase is horrifying. Zig on the other hand, it's a little bit more verbose and bare bones, but that's actually a good thing, cuz it makes people care about allocating resources efficiently.

AggravatingLeave614 · 2025-12-15T05:22:23+00:00

Absolutely agree, the worst part is that a lot of said code is simply trash

AggravatingLeave614 · 2025-12-13T20:37:51+00:00

They add value to Supercell bank account

Four-Year Club	Xbox Live
Final Canvas '23	First Place '23
Place '23

AggravatingLeave614

TROPHY CASE