rbehrends

11 ms·

61.
by rbehrends 5y ago
Its caching system is also smart enough to handle #include dependencies, so for simple C/C++ projects, it can also function as a make alternative (without having to write a Makefile). Plus, it makes cross-compilation really easy.
62.
by rbehrends 5y ago
> It depends on the runtime. In the case of Go e.g. the compiler inserts potential "yield"-s at every function call[1]. > And in the case of Swift the atomic "release" calls at ends of scopes will run regardless wh
63.
by rbehrends 5y ago
A runtime isn't some sort of magic thing that inserts itself into hotspots. Several of these benchmarks are just looping over pointerfree arrays for almost all of their runtime and still show differences. Unless you call parts of the r
64.
by rbehrends 5y ago
No, not really. Languages like Nim/Rust/D/etc. should not have significantly different speeds for equivalent implementations for these kinds of benchmarks, as they ultimately can be written to compile to equivalent LLVM IR an
65.
by rbehrends 5y ago
This was kicked off by Lynn Conway's famous VLSI design course at MIT [1], which began the Mead & Conway revolution. You can find a more detailed write-up of that course and other courses it inspired (as well as some of the practic
66.
by rbehrends 6y ago
And if you want something OSI-approved you can use either the MIT-0 [1] or the Zero-Clause BSD [2] license. The MIT-0 license is the MIT license without the attribution requirement, the Zero-Clause BSD license is (somewhat misleadingly) the
67.
by rbehrends 7y ago
Fossil's intended use case is different from Git's; it was originally built as the VCS for SQLite. In terms of its target audience, it's basically GitHub-in-a-box for small or medium-sized teams. Implementation/usability
68.
by rbehrends 7y ago
Thanks, but I do not plan to extend this project to other languages. I put it together a while ago as an illustration that conventional wisdom regarding GC cost is not what many people think. If I were to expand it, I'd look at other a
69.
by rbehrends 7y ago
This is not only a dated paper (a decade and a half old), but it relies on assumptions that do not necessarily hold in practice. If you test actual allocation performance on actual current day hardware, you may end up with completely differ
70.
by rbehrends 8y ago
This can be easily illustrated using this example [1], which uses both the Boehm GC (v8.0.2) and jemalloc (v5.0.1), directly installed via Homebrew, as well as the system malloc on macOS to implement the binary trees benchmark from the benc
71.
by rbehrends 8y ago
> The way you say "useful" brings to mind Inigo Montoya in Princess Bride: "you keep using that word. I do not think it means what you think it means." Concurrency and parallelism has been what I've been working
72.
by rbehrends 8y ago
Okay. First, I was talking about useful definitions of thread safety. That was language-agnostic, not related to Rust. And if absence of data races were all that Rust guaranteed, then Rust indeed wouldn't be much of a help. What Rust a
73.
by rbehrends 8y ago
What he is presumably talking about here is lexicographic DFS (as opposed to an unordered DFS), i.e. a DFS where the traversal order matters. To be precise: given a rooted digraph G with a set of vertices, an ordered adjacency list for each
74.
by rbehrends 8y ago
Freedom from data races is far too weak a condition to be useful. Consider the following example: you have a single global mutex, and every read/write to memory is bracketed by a lock/unlock of that mutex. The resulting code, whil
75.
by rbehrends 8y ago
The headline uses a too literal translation of the German word "Kartellbehörde" [1], which can (literally) mean cartel office, but in this case refers to the federal competition regulator (the "Bundeskartellamt" [2], whi
76.
by rbehrends 8y ago
Well, one standard deviation is far more than just "a few IQ points". One general problem is that much of this stuff tends to be very US-centric. If you look at British data related to poverty [1] and the IQ of children [2], you g
77.
by rbehrends 8y ago
Luckily, somebody already did the work [1]. In short: There is an implication in the Coleman essay that African Americans have less wealth because they spend more. Problem with that: 1. While black people spend more on these items than whit
78.
by rbehrends 8y ago
> It also only refers to ownership, not borrowing, and both are equally important. I addressed borrowing above. Borrowing is proving lifetime subset properties and that you therefore can avoid increasing the virtual reference count. And
79.
by rbehrends 8y ago
I am talking about just using basic references & borrowing. Once you introduce reference counting (Rc<T> and Arc<T>) and copying, you open up a lot more options, of course, but at this point you also can't make any life
80.
by rbehrends 8y ago
> This is a thing people say, but I think it's misleading. Reference counting can increase the lifetime of an object, but borrowing cannot. I've seen this really trip up beginners. "With a maximum reference count of 1.&quo
81.
by rbehrends 8y ago
> Oddly, Rust's ownership system really does solve these problems No. Rust's ownership problem solves it for trivial cases, at the cost of making it hard to do other things (such as sharing references past the lifetime of the o
82.
by rbehrends 8y ago
It is not a design error. You are making the mistake of equating reachability of a reference with making it legal to access it. And the problem is that the two often aren't one and the same. As a simple example, you may still want to a
83.
by rbehrends 8y ago
You can also have the exact opposite problem with RAII, where a resource survives the end of a transaction, because there is still a live reference to it hidden away somewhere (say, due to some debugging code holding on to it). This is a cl
84.
by rbehrends 8y ago
Well, but this subthread was originally about Article 11. I'm not sure how you are getting from that to Article 13?
85.
by rbehrends 8y ago
That's completely unrelated to ancillary copyright (the Article 11 stuff), however. That's the DMCA. You still have the right to quote, but Youtube is not required to host your content for pretty much whatever reason they like, in
86.
by rbehrends 8y ago
Yes, it is actually written into the Berne Convention as the right to quote [1]. And this is not going away at all. You will still be able to quote from articles in other articles, in blog posts, or in online discussions. The problem is tha
87.
by rbehrends 8y ago
Netflix already offers only a fraction of its US titles in EU member states. And you'd be surprised. The UK, France, and Germany combined already outproduce America in terms of movies [1] (quality may be a different story, of course).
88.
by rbehrends 8y ago
> 30% for each country seems really high to me. The article misstates what the proposal actually says. It's a quota of 30% on "European works". The term is defined in Article 1 (1) (n) of Directive 2010/13/EU [1]
89.
by rbehrends 8y ago
Against consumers, almost certainly unenforcable under the Unfair Terms in Consumer Contracts Directive alone, nevermind that some countries have even stricter laws regarding unfair contract terms. [1] https://en.wikipedia.org&#x
90.
by rbehrends 8y ago
The analysis of Article 11 is misleading. The actually relevant part is in Article 11 (3), which incorporates (by reference) the usual limitations and exceptions to copyright [1], including the right to quote. This is necessary, anyway, bec

More ›