If you really, REALLY need to track changes in deeply nested objects, look into proxies. You can recursively create proxy trees.

It's shit, really inefficient, but if you really gotta "deeply" track an object, yeah.

But if you're at this point, you may wanna rethink your architecture.

This and ignoring the fact that it's not some fucking web apl embedded as a desktop app... The performance was better a few years ago.

I mean... Drown your sorrows in a good authentic irish pub?

Make shit up.

That's why we use typescript. To lessen the suffering.

Regardless, yes, closures and promises in JS can be a Major pita.

What- What does it even do?!

Sounds interesting.

Not a react developer, but I also like having my types separate from my logic.

It feels cleaner to me.

@lorentz
I had some major issues with the vtable though. Apparently I fucked up somehow and fixed it by using the appropriate compiler flags and using RTLD_GLOBAL in my dlopen call. Kind of a hassle to understand some things but eh.

@lorentz I went with a virtual class :)

Tja.

I don't wanna say "specialize" since I'm much more of a jack of all trades kinda person, but I'm really interested in building backends in something that isn't node.js.

I was considering C++.

Thighs.

Here comes the sun 🎶

Actual loving relationship.

Thanks for the reminder. Gonna eventually set up my da's old drum kit.

OOOCHH NÖÖ

DIGGA

Do you also kill turtles?

Lmfao.
Glad I never got on toktok, who knows what it'd have done to me.

Coward. Should've gone and told people face to face.

HomePC-WorkServer-CustomerRDS-CustomerDBServer

@int32 approved.

I fully agree with jestdotty here.

Obsidian seems solid to organize your work.

Falling metal pipe sound.

"I hope this E-mail finds you before I do..."

@sidthepajfuk That's... The point.

Immediate unforeseen death.

Burn the place down.

Understanding what the fuck the customer wants.