elnardu

In case this website actually dies, see you all on mastodon: @elnardu@infosec.exchange

SOUL.md is really cool #L42" target="_blank" rel="nofollow noopener">github.com/openclaw/openc…

Looking into clawdbot internals is very fun

@gf_256 Yep

wtf gemini

@Nekrolm Вообщем не надо писать на плюсах и будет все нормально /s

@Nekrolm Интересно конечно что в си оно всегда работает, а в плюсах умирает при наличии любого объекта в скопе

Поскольку жизнь продолжается, я сел и написал вам очередную сказку на ночь о том, как я графики с метриками фиксил. Она не страшная. В ней я опять ругаю Rust (не сильно), а C++ молодец (нет) github.com/Nekrolm/ubbook…

rip :(

@cmgriffing (I also think that web would benefit from a bit of premature optimization, but that is beside the point)

@cmgriffing You are also assuming that there are readability issues (without measuring that as well)

User in chat (now banned): The "fill then map" is obviously slower because of extra iterations. Me: Laughs in JIT

@cmgriffing Stuff like that adds up quickly

@elnardu The 40-50% perf hit is for just the loop alone. If the loop is actually your bottleneck, then by all means fix it. But in most cases, the readability hit is not worth the gains you seem to care about.

@cmgriffing In general, if you want perf in js, you shouldn't rely on JIT at all. Chrome's, FF's, and Safari's JITs are all different and have different behaviors. Your app will have a lot better perf if you just stick to simple things and avoid all of that FP like JS entirely.

@cmgriffing I use this pattern all the time when writing jsx and it works quite well. And again, I don't think that any readability benefit is worth 40-50% perf degradation (esp in render functions that get called all the time)

@cmgriffing I don't think this is any less readable. (Or not readable enough to warrant a 40% to 50% perf hit)

@elnardu Just try it. It won't work. React JSX does not support that syntax inline. You can do other magic but then you move the context. Colocating the context of the loop with the rest of your JSX is pretty good for readability.

@cmgriffing Why would it not be usable :D ?

@elnardu This is fine, but it is not usable in a React render's JSX. That was the original use case.

@cmgriffing jsperf.app/susufa

@cmgriffing Sure

@SuperFashi1 @_JohnHammond Aren't they stored in the keychain on macos and ios? Not exactly plaintext

@_JohnHammond this is usually true for *all* devices that can connect to wifi😐

Fun fact: Windows stores Wi-Fi passwords in plaintext! You can extract passwords with netsh.exe, but that's a child process that might be observed -- we can improve our tradecraft to extract Wi-Fi passwords with native Win32 API functions... in Rust 😎😈youtu.be/auGJJOfmrMM

Not even joking learn.microsoft.com/en-us/virtuali…

Windows containers docs: "containers build on top of the host operating system's kernel" Also windows containers docs: jk, fuck you, in most cases you get a kernel per container