An application that really wants confidence in a write—to the extent that the underlying device and drivers allow—should use O_DIRECT. Or maybe there is a modern equivalent with io-uring. But that is not easy engineering :)
6,130 karma · joined July 6, 2020
All posts and comments are my own opinion and do not reflect those of my current or past employers.
An application that really wants confidence in a write—to the extent that the underlying device and drivers allow—should use O_DIRECT. Or maybe there is a modern equivalent with io-uring. But that is not easy engineering :)
I have no words! Except that I really want to know the organizational dysfunction that ended up creating that policy.
I don't see that in Autodesk's terms, which (per quick search - not exhaustive) seem to apply to "Fusion for Personal Use":
https://www.autodesk.com/company/terms-of-use/en/general-ter...
The only license I can find it compels is "If You provide Autodesk with ideas for improvement, suggestions, or other feedback".
(Not a lawyer, not your lawyer, not legal advice etc. etc.)
(Edit) yup: https://en.m.wikipedia.org/wiki/Richard_Ridings
* Ref: https://www.wolframphysics.org/technical-introduction/ The podcast with Sean Carroll that parent mentioned is also a surprisingly accessible lay introduction, definitely worth a listen.
(Edit) Another thought, since you mentioned time—numerical computing power and the math required to exercise it have advanced greatly since the 1970s, and it's likely that some of the trajectories and maneuvers feasible (again with the same fuel budget) today, even if they took 100+ years to complete, weren't even calculable back then.
If you think this sounds more like a job for a K/V store than a relational database, well, you'd be right; this is why e.g. Facebook moved to MyRocks. But MySQL/InnoDB does a decent job and gives you features like write guarantees, transactions, and solid replication, with low write latency and no RAFT or similar nondeterministic/geographically limited protocols.
* You can also structure your data so that the shard is encoded in the lookup key so the "routing" is handled locally. Depends on your setup
To Daniel/hackermondev: whatever you're doing, keep it up!
Great Reddit discussion about this: https://old.reddit.com/r/firewater/comments/9p1fwe/methanol_...
The other message I get from sites like this is, “Our developers have no idea how to escape SQL parameters even though this has been standard since the 90s [80s? 70s?!] so we just do “‘“ + password + “‘“ “
I'd be ecstatic to be proven wrong empirically, but it doesn't make sense to start our search there.
It is also extremely cold (-171C mean) and near-vacuum (100 nanopascal).
If there is life in Europa and it bears any resemblance whatsoever to the biology we know, it simply couldn't exist on the surface. Even the hardiest single-celled organisms here, which have also had 4.5B years to evolve into uncontested niches, could barely survive a limited exposure to these factors.
Starliner is also held for confirmation of all systems being functional even with the SRBs. Better to let them burn out on the pad and clean up the mess than to risk release with, say, asymmetrical thrust. That said I'm sure there are variances between the two rockets' procedures which could make one appear faster.
Hopefully the new Debian version of this script is a bit smarter!