It’s surprisingly calming to listen to Patrick cathartically vent, after what must’ve been a stressful education and career in finance.
It’s surprisingly calming to listen to Patrick cathartically vent, after what must’ve been a stressful education and career in finance.
Keep Lemmy small. Make the influence of conversation here uninteresting.
I’m doing my part!
I’m pretty sure that’s not how it works on Lemmy. For some reason “block” here is really what “mute” is everywhere else on fedi.
It’s basically corporate anti-virus software. Intended to detect and prevent malware.
Most large instances have a support community. That seems like the suitable place to raise a moderation issue with specific a community on the instance.
1995 by Kewlers & mfx
Do you do poison?
According to the article this system also detects power outages and shuts off when they happen. Just like full-scale solar power systems. But yeah, no physical kill switch.
I’m guessing regular non-LP DDR works fine socketed in desktops because power is nearly a non-issue. Need to burn a few watts to guarantee signal integrity? We’ve got a chonky PSU, so no problem. On mobile devices however every watt matters…
I doubt doing it in software like that outperforms sqrtss/sqrtsd. Modern CPUs can do the conversions and the floating point sqrt in approximately 20-30 cycles total. That’s comparable to one integer division. But I wouldn’t mind being proven wrong.
Well, yeah, but you asked why they didn’t use integer sqrt. It’s something many programming languages just don’t have. Or if they do, it’s internally implemented as a sqrt(f64) anyway, like C++ does.
Most CPUs AFAIK don’t have integer sqrt instructions so you either do it manually in some kind of loop, or you use floating point…
The builtin u64.isqrt
seems to be available in nightly only, and additionally I guess the author didn’t want to use any external crates as part of their self-imposed challenge. Though I think there may be an off-by-one result with f64.sqrt
I don’t think this functionally breaks their u64 code because they loop to root_n + 1
.
https://doc.rust-lang.org/std/primitive.u64.html#method.isqrt
There isn’t even any memory management in their code. And arguably the most interesting part of the article is implementing a bignum type from scratch.
The author pointed out they also could’ve just called openssl prime -generate -bits 1024
if they weren’t trying to learn anything. Rebuilding something from scratch and sharing the experience is valuable.
deleted by creator
As he alludes to, this is different on Teslas. Where in an attempt to save a few bucks on a simple sensor they’re using “machine learning” to detect rain with the front-facing camera and it doesn’t fucking work.
And I don’t think they give out stock grants to warehouse workers, but I could be wrong.
Yeah. That’s my point. And still people take these jobs and work very hard indeed. Try explaining “limited bathroom break time” to your average tech worker.
Average Amazon .com Warehouse Worker hourly pay in the United States is approximately $16.96, which is 7% above the national average.
People don’t seem to understand the average worker would kill to make $80/hour and $200k in RSUs. Not a dream job, right.
Yeah. Tech has gotten worse. But you really think it’s better in any other sector? I’m sure there are a few highly-compensated lap-dance-inspectors out there but the vast majority of workers deal with the same shit techies are dealing with, for significantly less pay and respect, if you can believe that.
Companies use the same kind of systems to (poorly) automate the search for candidates, which is also spammy, inefficient, and wastes job-seekers time. This just levels the playing field.