Dear Squeaks,
Thank you giving us 2 more days for saying our goodbyes.
Thank you for 10 years of your companionship, your affection, and your love. You were such a kind and gentle soul.
Know that we loved you every single step of our way together. You will be dearly missed.
@ZPostFacto Totally agree with what you are saying, I'm on team const void*.
But I do wonder why nobody added an inline function/wrapper that takes a const void*, and forwards the call to the crypto lib with a cast?
That way, you have one call site with a cast and not 70.
The glacier engine is pure wizardry. I don't know how they manage to maintain great performance while having so many NPCs on screen at once, while also maintaining such a high level of detail.
@1nterlandi@typesfast Local-first & completely transparent, open source, no outstanding legal copyright issues, designed for strict human verification of all artifacts. It needs to produce what I would’ve produced more slowly with no catch.
@ZPostFacto@TrisH0x2A I don't think making toupper a pure function would change anything.
The code writes to s, which is also the argument to strlen, so pure functions won't help you here.
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
Storing undecorated names for private/local/static symbols inside PDBs was a stupid, stupid, stupid idea.
Mangled names would be smaller and unambiguous. On top of that, they're already there in the object files.
@rfleury No, they are not stored in the PDB, only for public/global symbols.
Other streams inside the PDB (e.g. compiland/module streams) only store undecorated names.
The debugger won't show you the mangled name, because it's not there.
Today is a beautiful day for updates!
On the Stable channel: rolling up a large number of features, perf optimizations, and QoL changes made over the past months
On the Insider channel: support for our instrumentation API has been implemented on PS4 & 5!
Go check it out!