froztbyte

jesus fuck so many parts of this are psychic injury

the account name, the presumption of "oh yeah my opinion is right", the very nature of this person's "engagement" (quotes intentional) with conflict, the deference to non-authority (holy fuck how the fuck is it that we have worse than the personal-abdication of christianity (oh right, it's mcfuckingsaltman's fault)).....

I want to say "some of these people are in desperate need of a hug", but then as a friend of mine pointed out recently: "maybe if they weren't all such self-loathing pieces of shit they may actually get a hug"

in the current most-typical mode of engagement, commit messages are too disconnected from the actual contents. it requires someone who gives a shit to go looking

conversely, what I mean is something like "a hook that guarantees that the moment the plugin is engaged and output from it is scribed in source, metadata about that event is simultaneously co-written"

it's already generating a pile of other things, it may as well generate timestamps and callsig and callhash and shit too....

the number one problem with this, of course, is that it's going to be extremely unpopular with a Vocal Set Of People who rely on this shit to make themselves look good

that was indeed another input to the heuristics

(post-hoc, to be honest. but it's still fucking hilarious)

that was indeed another input to the heuristics

nominative determinism strikes once again!

a ghoul’s impressionist rendition of an actual person

I got a handful of paragraphs into reading that and then realized I definitely don't want to read that tonight

def fuck that guy tho

an idea I just had (which would need some work but talking hypothetical): wouldn't it be lovely if ~~IDEs~~ VS Code[0] automatically inserted "Copilot Used Here" start/end markers around all generated shit. could even make it a styleguide/editorconfig so it's universally set across projects[1]

[0] - because lol ofc it's mainly vscode rn

[1] - and then when you find colleagues who lie about whether they're using it you wrap all their desk shit in foil

for many years, I went blessedly unaware of who this random fuckjack was, knowing only: 1) ambiently knowing the name, 2) that I ambiently know the name (these two things together are usually a decent heuristic for me to not bother digging)

and then I got jumpscared by a full-scale mrbeast standee in a shop some months back

may I soon be able to forget about this fuckjack once again

but the fact that they didn’t seize this opportunity

honestly, I think they did try, and ran into the unfortunate reality of physics

to make that product work, you need reliable high throughput (this is helped by codecs), sufficient juggle-able GPU space (this is helped by being a gear-hogging first-in-line monopolist), and lastly the casual little requirement of actually being close enough to your customer base

iirc US cost to coast latency is around 65~70ms (so 2x that is the upper timebound for player interactivity, obvs there it'd be less because more local DCs though). just from me to europe is 165msec+, with a far less predictable path throughput. the scale economics to launch a DC for this in ZA (even to serve subsaharan africa all the way up to kenya) just plain doesn't work, and there are many more places in the world where it doesn't

it'll be interesting to see if a retrospective as to why it failed leaks out of that biz someday

which part of it was the freebie? whole service looked dead on arrival to me (for the simple reason of physics)

looked up the previous thread (now that I'm at laptop briefly)

that article misses one of the delicious parts of that story: they called saltman a “podcast bro” in derision