dom0

60 ms·

601.
by dom0 9y ago
> there's no particular penalty for random-access vs. sequential usage This is not really accurate; random access has a penalty compared to sequential access (that's just the physics of it folks™) — the unique characteristic wo
602.
by dom0 9y ago
I'm not sure that's feasible.. there are exactly zero independent TeX or TeX-like implementations, everything is patches on top of TeX, which probably has a reason (given the general open source community's inclination to rew
603.
by dom0 9y ago
> > Not merely exaggerated, nonsense. All filesystems using non ecc memory are more likely to experience damage to the data stored therein. > If it were "nonsense" then one could flip the argument and say "ECC memory
604.
by dom0 9y ago
It still looks like the FS exhibits perf degradation (well, uh, worse than Linux already degrades under I/O load anyway) under not-that-untypical workloads. A few years ago it had the same problems with bog-standard workloads such as u
605.
by dom0 9y ago
Also for projects that regularly receive a good dose of Twitter hate (e.g. systemd).
606.
by dom0 9y ago
s/exaggerated/wrong
607.
by dom0 9y ago
Even later on BIOS got it wrong from time to time.
608.
by dom0 9y ago
This is Intel. None of the previous iX HEDT platforms supported ECC. Intel being Intel also means that they remove features for cheap (i.e. <1000 $) parts, such as memory channels or PCIe lanes.
609.
by dom0 9y ago
Generally speaking, streaming AEAD is discouraged on an API level, because it incentivises using unauthenticated intermediate decryption results. Thus, block the data into reasonably sized blocks. Also, yes.
610.
by dom0 9y ago
OP: > people making millions > It's made me think who has been the most successful at building a company as a sole proprietor.
611.
by dom0 9y ago
I assumed that OP's "making millions" referred to a yearly-ish timeframe, not the entire existence of a business.
612.
by dom0 9y ago
I'd be surprised if he made millions from this service.
613.
by dom0 9y ago
Besides some scattered text files and the Linux man pages, there is this: https://www.kernel.org/doc/html/latest/ It's fairly new - started about a year ago, but there's quite a lot of stuff in ther
614.
by dom0 9y ago
2) is concurrency, 1) is parallelism; there are various programming models for multiple threads. The basic approach of mutual exclusion (=shared memory, locks, barriers) is just one of them, another approach would be message passing /
615.
by dom0 9y ago
The fastest file format is always the one you can just dump into memory and fix a few pointers. But these tend to be also the hardest formats to change/evolve... Densely coded formats, such as msgpack, are neat for archival / long
616.
by dom0 9y ago
$MFT et al are not special file names. It belongs to a set of files (they are well-formed files) that make up the NTFS volume (they're in the volume root); I think the design is a bit poetic - the file system is made up of files conta
617.
by dom0 9y ago
Information.
618.
by dom0 9y ago
How about Hyrothrax? That name got a fine Anthrax-vibe going for it!
619.
by dom0 9y ago
Cargo.lock for applications freezes the entire dependency graph incl. checksums of everything, for example.
620.
by dom0 9y ago
That's a good point I overlooked. Although the journal is not that big (<1 GB); so doing some extra I/O after the shred should get rid of that. When the original contents are older, then it's rather unlikely they're s
621.
by dom0 9y ago
Yes, although this applies to all forms of porting changesets or patches between branches or releases.
622.
by dom0 9y ago
As the branches diverge, merges take more and more time to do (up to a couple hours, at which point we abandoned the model)... they won't be done automatically. Since merges are basically context-free it's hard to determine the &q
623.
by dom0 9y ago
> In general, Python is slow (compared to C or whatever) because of excessive memory allocation and overuse of hash maps. Python is a highly dynamic language with an API (towards both Python and C) that is very invasive. These two things
624.
by dom0 9y ago
My exact experience (in the context of "merging upwards"). Large merges are a huge pain to do, and are basically impossible to review, too.
625.
by dom0 9y ago
Also git rerere When maintaining multiple release lines and moving fixes between them: Don't use a bad branching model. Things like "merging upwards" (=committing fixes to the oldest branch requiring the fix, then merging the
626.
by dom0 9y ago
> Not even multi-process. Threads on Linux can have their own seccomp profiles. Feels kinda pointless, since all threads in a process share the same memory protection.
627.
by dom0 9y ago
I dunno if it's actually vim or some variation on it, but it is the default on, for example, Arch Linux, although I believe most other distros dropped me into it as well (e.g. git commit / rebase -i). If there is such a thing as
628.
by dom0 9y ago
Also: Emacs is rarely if ever used in the terminal today, and exiting it through the standard desktop protocol ([X], Ctrl-[Shift]-Q, Alt+F4, ...) always works.
629.
by dom0 9y ago
A couple people use external tools (rclone and git-annex are popular) to sync their Borg repos somewhere else. This requires enough local space (hard drive / NAS / whatever) to store the repository. This can be an advantage (=stor
630.
by dom0 9y ago
AIUI smart contracts mean that a ton of nodes has to execute this code, so making the language of the code as weak as possible would seem like an important design goal to me from a langsec PoV.

More ›