how on earth does openssh not only have incredibly fucked versioning but is the only package i've ever seen to mention a "privilege separation" chroot path which actively breaks non-root builds. are you fucking kidding me bruh. "privilege separation chroot" defaulting to /var/empty and it immediately errors if it can't create it????? why are your version strings like that bruh?????
241
Replies
·
0
Boosts
@aeva the point is, LLM guys are all like this. first problem set freshman year uchicago and they're sweating cause they've never had to actually read the assigned text to answer a question before. they're all nervous like "a uniform distribution..........is fair" just like daddy von neumann told them. and they felt real pride when they got a gold star on that response
@aeva so the ones who (bernoulli's law of large numbers, that's a real one) achieve a sufficient string of successes to have convinced others that, of course, this was ordained by their ability to divine the future, are consequently blessed with further success, because financial markets are confidence games
@aeva so now guys like masayoshi son have not only sufficient capital but a sufficient reputation pipeline that nothing they do has any effect upon their financial success whatsoever. and these guys think they're pretty fucking shrewd.
they have long since detached from the capacity for emotional investment. they can't explain anything that happens in the world around them. they know what to do: uniform distribution is fair. so they don't play fair. it's so easy to imagine justice and fairness as a weakness.
@aeva so we hit the 90s and computers have completely revolutionized the financial industry. why? because you can make decisions so much faster! and that means more decisions, which means more money.
the internet is sometimes slow? sometimes down? netscape to the rescue! the internet is an application platform! the application is on the internet! what do you mean down? i'm on the internet right now!
@hipsterelectron ok so this is fascinating but why is SIMD evil?
@hipsterelectron like was that remark specific to avx512 being something of an "expensive planes that don't fly" situation or was your meaning that there is something fundamentally bad about vector processing?
@aeva there is something bad about ARM's vector processing standards, which are different in many ways. the latent potential evil in in vector instructions is because they are in fact motivated, in part, to achieve what LLMs are hoped to
@aeva that if you can pay more money for hardware you can leverage that technical advantage for corresponding market dominance. this mindset is the monopoly shit reaching its apex with LLMs
@aeva the reason i personally have bad vibes about them is because the bigger and bigger ones have ridiculous pipeline latency issues and are progressively more difficult to use within that sweet spot where you can achieve a useful application result without hitting the redline too hard and stalling out
what this means is (unless you are geoff langdale + hyperscan team and spend immense amounts of effort developing novel mathematical frameworks) they're literally just accelerators for extremely simple straight-line shit
@aeva [i promise this concludes immediately]
@aeva and literally all i need to do is exactly two things. my fucking kingdom. two things:
- indices of individual bytes matching this set of bytes in a contiguous memory region
- asynchronous memcpy queue that doesn't interface with any part of the fucking x86 CPU
@aeva SIMD instructions largely don't even need 256 wide vectors to do cool shit because the "SIMD" acronym was coined by 80s sloppers
@aeva i guess technically a scatter and gather are "SIMD"? but masked loads for example are actively reducing the M because human intelligence can compose the I
@aeva so along with "cryptographic hash" i guess i'm also immediately ceasing my use of "SIMD" because "vector" is the cool as shit fucking alligator in shadow the hedgehog
