Readit NewsUberphallus commented on ABit BP6 Dual Socket370 Motherboard (1999) hardware-one.com/reviews/... · Posted by u/userbinator
I had one of these for years, with two 400 MHz Celerons clocked up to 500 MHz. The setup was not really stable, though. Used it on Windows NT4, Linux and FreeBSD.
I actually had 3 of these with PII 300MHz @ 450MHz running OpenMOSIX. Good times.
A great skill I have been developing as I mature is the ability to look at a seemingly suboptimal implementation I receive and not be appalled by the perceived sub-optimality but rather appreciative of the history that is embedded in the little details. For me, any system producing correct and useful results is perfect under the constraints of its implementation. Even if the developer was not great, someone was great enough to mitigate for it. I have seen many such ugly, perfect systems.
I call it software kintsugi[0].
After reading a few smug comments, I've concluded that some of the folks in this thread have never worked on an application where the production scale is many, many orders of magnitude greater than preproduction environments. There's no substitution for "testing in prod." If you're not "testing in prod" with your really-big application, you're not testing enough.
Exactly. Here we crunch loads of data, and by a lot, I mean our production databases run on a three digit cluster of four digit terabytes of data. Good luck having that scale in preproduction environments.
We have loads of redundancy, and dedicated "test in production" machines/datacenters to test actual production loads in actual production-scale sets machines.
Now, tests in production usually involves a pair of hands and 2 other people looking behind (dev + ops + dba), and requires a well defined rollback procedure and post-mortem. We still have absurdly high SLA (99.999%).
fer commented on Django 4.0 release candidate 1 released djangoproject.com/weblog/... · Posted by u/pauloxnet
> if your backend throws requests against external (and potentially blocking) services and you have the "audacity" of wanting to keep answering your clients.
If you have enough processes/threads running, the CPU scheduler should take care of that , no?
Yes, but more processes means more memory footprint, almost 4 times as much in that benchmark, something the author didn't cover. Threading solves that, but it's way more prone to shooting yourself in the foot than async, especially since it's not baked into Django (i.e. you gotta cook your own solutions over callbacks, polling, etc).
Uberphallus commented on Django 4.0 release candidate 1 released djangoproject.com/weblog/... · Posted by u/pauloxnet
agreed, I'm more convinced now that django is really enough and get shit done even if there a poor support of async, more convinced after reading this blog post that async python is not faster (was on hn) : https://calpaterson.com/async-python-is-not-faster.html
It's not significantly faster (or slower), it's the author that doesn't know how to run a benchmark. You can read my take on his take [0].
Leaving that aside, async is very advisable (even a must) if your backend throws requests against external and potentially blocking services and you want to keep answering your own clients without scaling for no reason.
I believe the FDA is already mandated by law to release this data, which is why the original lawsuit was filed.
From a Reuters article on it: They also argue that Title 21, subchapter F of the FDA’s own regulations stipulates that the agency “is to make ‘immediately available’ all documents underlying licensure of a vaccine."
So it really sounds like this is just part of the course of making sausage of approval. You have someone already embedded in the licensure project/process where this is all (very likely largely automagically) handled as it is always expected to be released to the public.
Yeah, but this scale of documentation production is unprecedented.
A lot of cash was dumped into fast and extensive R&D, trials and production scaling because of the urgency of the situation, and along comes an insane documentation backlog.
To put in perspective, the original HPV vaccine R&D and trial spanned over 7 years with 25,000 patients (of which only 20,000 women), and assuming the documentation was provided to the FDA as it was produced, it could be FOIA'd relatively quickly.
Pfizer/BioNTech did the same, with almost double the patients, in just over 6 months.
If the FDA is not able to deliver our documents to us in time, maybe it is time to shut it down. Let public do the research and let consumers decide if they want to take the vaccine based on available results.
Ironically, if the FDA could deliver those documents "in time" it would be a sign of a pretty limited trial, and people would be complaining about that instead.
Damned if you do, damned if you don't.
Uberphallus commented on What does microblogging give you that forums didn't? cybre.space/@tindall/1072... · Posted by u/dredmorbius
>Unlike forums, social media has an unlimited audience.
What does that even mean?
Critical mass. FB groups are a dumpster fire for topic discussions, but the fact that they're just there means loads of communities end up there anyway.
[0]https://www.fer.xyz/2021/11/software-kintsugi