dist1ll

15 ms·

151.
by dist1ll 3y ago
If you're interested in queues, you might want to check out the USENIX BBQ paper from last year: https://www.usenix.org/conference/atc22/presentation/wang-ji... They've gone with a block-based appro
152.
by dist1ll 3y ago
That's not entirely correct. Deadlock-freedom means that at least one thread will make progress in the absence of failures . Lock-freedom is a much stronger statement. It guarantees progress of at least on thread in finite time, regar
153.
by dist1ll 3y ago
Who invigilates the invigilators?
154.
by dist1ll 3y ago
> That said, I still hate async with a passion, it makes the language more complex and not very elegant (i.e. function coloring) Function coloring seems to come up a lot in these discussions, but I don't see a better way without pro
155.
Counting cycles and instructions on ARM-based Apple systems(lemire.me)
2 points by dist1ll 3y ago|0 comments
156.
Sneller Regex vs Ripgrep(sneller.io)
4 points by dist1ll 3y ago|3 comments
157.
by dist1ll 3y ago
> clone() makes an immutable, deep copy/recursive copy of the original data structure. No. clone() calls std::clone::Clone::clone. For many std collections that means deep/recursive copy. For custom data structures, it can mean
158.
by dist1ll 3y ago
(Warning: super pedantic) Actually, what akvadrako described is just called multiprocessing - not SMP. SMP refers specifically to systems with uniform latency to shared memory. So any distributed memory topology like ccNUMA w/ interc
159.
Hello World Under the Microscope(gynvael.coldwind.pl)
2 points by dist1ll 3y ago|0 comments
160.
On Custom-Width Integer Types(alic.dev)
4 points by dist1ll 3y ago|0 comments
161.
by dist1ll 3y ago
> Personally I think Dlang get it right by making GC as a default and provide no GC as an optional feature. I vehemently disagree. D's GC is the #1 reason for its fade into obscurity, instead of becoming a viable C++ competitor. Now
162.
by dist1ll 3y ago
That's a very elaborate way of saying that competitive players should delude themselves to cope with their weak mental game. > Anything below 80% winrate, means it becomes hard to distinguish the learning signal from the variance of
163.
by dist1ll 3y ago
> Which brings us back to regular discussion: C ( and C++ ) does not match hardware anymore. There is no real control over important properties of generated code. Programmers need tools to control what they write. Plug and pray compilati
164.
by dist1ll 3y ago
clang has __builtin_unpredictable [0] [0] https://clang.llvm.org/docs/LanguageExtensions.html#builtin-...
165.
by dist1ll 3y ago
To add to this, the superset of these ideas is referred to as "non-blocking", and lock-freedom is one flavor. There is also obstruction-freedom, starvation-freedom, wait-freedom, etc.. All of which have their own trade-offs and co
166.
by dist1ll 3y ago
The article in the first link is pretty bad, and the entire code is undefined behavior. First of all, using inline asm + volatile to emulate well-ordered release & acquire on x86 is unnecessary. That's exactly what atomics are sup
167.
by dist1ll 3y ago
> Most of the cases are found to be on android devices. Do you have some relevant sources about banking fraud? Android devices make up more than 70% of Thailand's market share [0], so it's not a surprise. [0] https:/&#x2F
168.
by dist1ll 4y ago
> Did the people working on this really think they wouldn’t be smacked down hard for it Of course they knew. That doesn't stop a hacker. Individual freedoms will always be hard-fought. And authoritarian governments will always resis
169.
by dist1ll 4y ago
> light-weight threading with preemptive scheduling prioritizing latency over throughput Tasks for backend systems are usually pretty homogeneous. I'm not sure how in such cases the overhead of preemption is in any way better than c
170.
by dist1ll 4y ago
Sure, but that's due to Bitcoins implementation. There's nothing inherent to "open" ledgers that prevent them from providing anonymity. My point is: dunk on Bitcoin all you want. Just don't drag the general idea of
171.
by dist1ll 4y ago
"Open" is a heavily overloaded term. One of the main premises of Bitcoin is tamperproofness and permissionless participation. That in itself does not equate to lack of anonymity. Just have a look at Zcash[0] or Monero[1]. In gener
172.
by dist1ll 4y ago
This is a bookmark-worthy paper. > YARPGen v.2 was able to detect 66 previously-unknown bugs in GCC, 28 in LLVM, 16 in the Intel® oneAPI DPC++ compiler, and 12 in Intel® ISPC. Amazing. I'm curious what a future version of YARPgen w
173.
by dist1ll 4y ago
Yup, linguistic determinism is nonsense, thanks for pointing that out. I edited my comment.
174.
by dist1ll 4y ago
> Your vocabulary is tied to your expressive power and your ability to form coherent and compelling arguments There is even more to it. Language can influence (prev.: limits) your thinking and ability to categorize. See https:/&#x2
175.
by dist1ll 4y ago
Thanks for providing those references, I'm pretty curious about this topic.
176.
by dist1ll 4y ago
Great to see a futhark lib in the wild, the code seems really concise and readable. I feel the main reason for Futhark's ergonomics is FP combined with its array prelude (e.g. fold/transpose/flatten/rotate/indices).
177.
by dist1ll 4y ago
> There are numerous studies that show a positive correlation with ketone production and cognitive performance. Do you have a source? Your second link measures cognitive performance in rats, not humans.
178.
by dist1ll 4y ago
I think that's a reasonable decision. Devs who need lots of networking throughput usually have their own NICs cards from a preferred vendor (with the necessary features) anyways.
179.
by dist1ll 4y ago
You can emulate closures with anonymous structs. struct { fn foo() { /**/ } }.foo If you want closures that capture values, you just need to define the appropriate struct. I'm pretty sure with proper use
180.
On Nontermination and Optimisation in Futhark(futhark-lang.org)
4 points by dist1ll 4y ago|0 comments

More ›