strmpnk

20 ms·

151.
by strmpnk 10y ago
While it's rather introductory, "A Tour of C++" is a much more concise book. Read that and then maybe look at some Scott Meyers books (I haven't read "Effective Modern C++" but the other entries in the series a
152.
by strmpnk 10y ago
This is exactly what I was thinking too. I have my old phone I wouldn't mind using for travel. I'd just keep that one mostly empty and swap the SIM card when traveling. Alternatively a backup could work as long as you place it som
153.
by strmpnk 10y ago
I'll try to compile some references on a page but I gave this talk last year for an Elixir conference: https://www.youtube.com/watch?v=_HQfS8efVeg (It's not the best talk I've delivered on the topic but it&#x
154.
by strmpnk 10y ago
Anonymous functions in Erlang are lambda-lifted into named functions during compilation (during Core Erlang -> Kernel Erlang transformation IIRC). So there isn't much difference in terms of the final representation. Erlang's co
155.
by strmpnk 10y ago
While I'm already one of the few that use F# full time, I think this is a rather self-fulfilling statement. Looking back in time, Microsoft has continually cubbyholed the language, almost to the point of counter-marketing its general p
156.
by strmpnk 10y ago
Which is pretty close to 338 words on a 64bit system (338*8). Looks like it's taking 2 extra words there though. Curious.
157.
by strmpnk 10y ago
Fair point. I guess I never see the prophet thing but his ideas are interesting so I tend to follow Kay's work, if only to blend it with many other things, not so closely aligned with his views (ex: Lamport being close to opposite of K
158.
by strmpnk 10y ago
It's hard to put words in Alan Kay's mouth for him on this point but what he usually talked about was the biological model, specifically in regards to cellular units. In computing this does translate to independent, reliable, and
159.
by strmpnk 10y ago
I don't think that explanation is clear. It takes a bit more work to get something which proves the experimental difference. One of the better explanations I've seen is regarding measuring spin with three state detectors: https:&
160.
by strmpnk 10y ago
I came away with a similar reaction, but there is no need to map separately first: https://news.ycombinator.com/item?id=13136056 Sometimes I do wish Erlang had something like F#'s active patterns because it'd make
161.
by strmpnk 10y ago
There might be a good alternative. Sometimes it's that one function right in the case expression that prevents lifting the matching to the function head (which is considered good style in Erlang). To do this you could try wrapping the
162.
by strmpnk 10y ago
Prolog itself has many issues, many of them rooted in its somewhat unrestricted use of terms. The nice thing about datalog is that it has very nice strong normalization as a natural property of term evaluation. While it's true that it
163.
by strmpnk 10y ago
You might like F#'s object expressions for the cases where a lambda won't do.
164.
by strmpnk 10y ago
Some of the gain in concision is from the language it seems but I think this case is very much from the view of leveraging frameworks and libraries which themselves are quite a bit bigger than the app. I cloned a few of the repositories and
165.
by strmpnk 10y ago
Rumors had it that they're in shorter supply than the other colors so it might make sense for them to mark that one as a premium model only. They could add a 32GB model later. Another theory might be the branding they started with the
166.
by strmpnk 10y ago
BEAM was just one of a series of virtual machines that implement the Erlang language, so it's not really fair to compare it to Java (just as HotSpot was built a few years after Java).
167.
by strmpnk 10y ago
I was about to mention that was backwards but forgot about that silly April fools joke. That was worth a good laugh this morning.
168.
by strmpnk 10y ago
It's demand based. The consumer will request a fixed size of input and then the producer will send up to but no more than that until more demand is made.
169.
by strmpnk 10y ago
Which is interating here since F* can extract to OCaml. I wonder how hard it would be to wire up a test harness to compare the two with randomized tests.
170.
by strmpnk 10y ago
Though it does seem to show decoding is slightly faster with LZFSE unlike your parent's local benchmark. It's not clear to me that either is always superior on those charts.
171.
by strmpnk 10y ago
F# is similar but if you're using features like polymorphic variants, functors, or first class modules, it might take more effort. In terms of package management, I'd check out paket. It wraps up the otherwise very quirky nuget sy
172.
by strmpnk 10y ago
F# comes from Microsoft Research and was notoriously ignored by the corporate side for years (and still is to some extent). So I'm not sure F# has really ever been a project of Microsoft corporate interest, and now there is the F# Foun
173.
by strmpnk 10y ago
I work with F# and have a lot of experience with Erlang (less so with GHC and it's lightweight green threading but I've heard good things about it). F# inherits lots of .Net's primitives which at their core are thread pool ba
174.
by strmpnk 10y ago
I think we have different definitions then. A thread (green or not) is a context of execution which includes a stack. Saying that it's not what it is seems like you might be thinking of stackless generators or something, which are most
175.
by strmpnk 10y ago
A lot of the edge cases like back pressure and certain kinds of state machines are a lot easier to represent as function calls rather than an asynchronous events. Most of the good implementations of these ideas with events have some sort of
176.
by strmpnk 11y ago
This assumes failure is clean. Some failures are tougher, for example, imagine code going into an infinite loop. It either system, you have waste but the scale of the disruption in Erlang is kept isolated where Akka would fail to release th
177.
by strmpnk 11y ago
Exactly. In terms of fault tolerance, a buggy actor is isolated in regards to scheduling others. Bad behavior has a more limited scope. This isn't to say that one can't create a process that eventually has harmful consequences to
178.
by strmpnk 11y ago
One tough part of the load handling is that if the L has increased capacity, this could, in some cases, just make congestion worse in many other areas because many people need to make at least 1 transfer for their trips. The tough problem i
179.
by strmpnk 11y ago
For most scaled up examples in Erlang and Elixir, there is a BEAM process (green thread) per connection as well as others (usually arranged as a supervised pool so one can avoid an acceptor bottleneck). There are a few reasons it does bette
180.
by strmpnk 11y ago
Map is a constructor in this case. You'll want lists:map/2 (fn comes first). I don't know LFE much so there may be sugar of sorts for this, perhaps a comprehension syntax.

More ›