shwestrick

9 ms·

31.
by shwestrick 4y ago
This debate has gone round and round for decades. There are no hard lines; this is about performance tradeoffs, and always will be. Perhaps the biggest misconception about reference counting is that people believe it avoids GC pauses. That&
32.
by shwestrick 5y ago
I think laziness would be a distraction here. The idea of encoding effects as "action values" is relevant and interesting, even under eager evaluation. Certainly laziness has influenced a lot of things in the world of FP. But it&#
33.
by shwestrick 5y ago
OCaml is pretty close already to what you're describing. The OCaml ecosystem fully embraces imperative programming. And if the syntax of OCaml is problematic, then perhaps ReasonML ( https://reasonml.github.io/ ) is what
34.
by shwestrick 5y ago
A combination of both. This work targets multicore, but execution on the GPU is definitely possible. It's just a different line of research. I'd highly recommend taking a look at Futhark ( https://futhark-lang.org/
35.
by shwestrick 5y ago
Author here. One of the cool things about the property we're using here---disentanglement---is that it specifically allows for shared data, under only mild restrictions. This allows us, for example, to implement fast libraries which ut
36.
by shwestrick 5y ago
The defining feature of these effect systems is "resumable continuations". Essentially, at the point where you catch an exception, you have the option of resuming the code which threw the exception, and you can tell it how to proc
37.
by shwestrick 5y ago
"opposite" is not the right term... tree-shaking appears to be a particular technique for dead code elimination. I.e., there are many algorithms you could use to eliminate dead code, and tree-shaking seems to just be a simple one
38.
by shwestrick 5y ago
There's a lot of caveats on this data. It's only showing the ratio of people submitting reports through their benchmark software, which apparently only runs on Windows. So, that makes it sound like the entire space of Linux server
39.
by shwestrick 5y ago
In the "Race Conditions? Not with Javascript!" section: > They [...] decided that no concurrency between threads is allowed, for the safety of everybody. This resolves the race conditions by removing the possibility that multip
40.
by shwestrick 5y ago
Genius! Cheap, effective, and low-maintenance.
41.
by shwestrick 5y ago
I don't think this is really anything to do with music vs programming. The author just used the wrong words... it's pretty clear they meant "generate a chromatic scale starting at any note" ;) Thanks for bringing up the
42.
by shwestrick 5y ago
An observation that I find kinda nice: passing a default value is essentially just a special case of CPS :)
43.
by shwestrick 6y ago
> you should always return in an 'if' branch Interesting. This code style simply doesn't need 'else' at all. I can surely say, if I was reading a codebase that adhered to this discipline, it would be very easy to
44.
by shwestrick 6y ago
IMO one of the most valuable things I've learned about static analysis is that the halting problem is overly pessimistic. It's easy to prove very interesting things about real-world code. Things like dead-code removal are a pretty
45.
by shwestrick 6y ago
Some additional information here: https://www.kubotaholdings.co.jp/en/ir/docs/20201216_EN_eSpe... Assuming this device is actually legit (I'm skeptical...), it would need e.g. FDA approval to be used in
46.
by shwestrick 6y ago
I think you and @stretchcat are saying the same thing. Ease-of-repair and durability are more important than recycling.
47.
by shwestrick 6y ago
I love this. It's so easy to use and works great on a trackpad. I'm going to start using it in my meetings. Nice job! ------ EDIT: After playing with it for a bit, I have some feedback :) - Sometimes, I accidentally press Z inst
48.
by shwestrick 6y ago
Such an invaluable resource! I spent many hours here while helping develop https://hexiconapp.com/ . The axial coordinate system, in particular, makes working with hexagons much simpler.
49.
by shwestrick 6y ago
Apparently RUNCOM is where the "rc" naming convention comes from?? (E.g. bashrc, vimrc, ...) Very cool. I always wondered what the "rc" meant. https://en.wikipedia.org/wiki/Run_commands
50.
by shwestrick 6y ago
Hmm I was separating the concept of "thread-per-core" from sharding. I would argue that typical cooperative task schedulers (e.g. work-stealing) get the performance benefits of thread-per-core without requiring any static partitio
51.
by shwestrick 6y ago
Thread-per-core has been around for a while! It's how a lot of modern multicore languages work. You've probably heard of "green" or "lightweight" threads before... it's all the same idea. Typically, you&#x
52.
by shwestrick 6y ago
What do you mean by "functions are supposed to be mutable"? Perhaps you are just pointing out that the output of the function (and therefore the value of the field...?) will change as the input changes? If mathematical tuples are
53.
Parallel Digital Reverb, Or: How I Optimized the Heck Out of a Comb Filter(shwestrick.github.io)
1 points by shwestrick 6y ago|0 comments