146 karma · joined December 3, 2016
It turns out that the Kindle runs an embedded version of Java without a GC. This seems to have stifled the development quite a bit, so it's really cool to see how Raspberry-Pi/Inky homebrew is becoming a thing.
function bindPromise(p, f) { return p.then(f); } function returnPromise(a) { return new Promise.resolve(a); }
Proof of the laws left as an exercise to the reader :).
But yes, you are correct that promises do quite a bit more than only being a monad, for example because of how they treat errors.
EDIT: I concede, I am wrong! https://buzzdecafe.github.io/2018/04/10/no-promises-are-not-...
By "combinator" do you mean combinator as in the combinator pattern?
I have no idea what value your comment brings us except a way for people who already agree with you to give you upvotes, and what's the point in that?
EDIT: Nah, not really. CASH Music gives a platform, Drip is for connecting platforms.
EDIT: Assuming inlining and call-by-value struct is a possibility.
Only if you buy a juice concentrate. Making your own juice is equivalent to chewing an orange.
>You're free to believe what you want. A slime of chicken skin, fat and ligaments isn't digested the same way as a chunk of chicken breast. The nutritional values are just a small part of a big equation.
Of course not, I'm not arguing for that. What I am arguing for is that there's nothing inherently unhealthy about eating any of those things, and that offal is actually very nutritious.
>That's another side of my point, they evolved on that diet, most people didn't. Do you think the lifestyle of the average first worlder has anything to do with inuit lifestyle?
If an American adopted the diet of an inuit in such a way that their caloric needs are satisfied then I doubt it would matter. It is definitely possible that the inuit have evolved in some ways to accomodate for their diet, do you have any sources for that?
>It's like eating a fruit vs drinking a juice
Another thing that doesn't matter. What exactly do you think magically happens when you put an orange into a blender and mix with a bit of water that would make it lose its nutritional value?
The reason that processed meat (that is meats which are smoked, salted, etc.) is recommended to not be eaten is because it has been shown to be carcinogenic.
The egg thing is based on the idea (I actually don't know enough to know if this is correct or not) that dietary cholesterol intake affects blood cholesterol levels, and eggs have a bit of dietary cholesterol in them.
I get that we're not very educated within this area but perhaps we should stay quiet then? What's the point in writing comments on HN about things we know very little about?
Here's the best source I have on Norway: https://www.fhi.no/nettpub/hin/levevaner/overvekt-og-fedme/
I wouldn't disregard it as a factor.
Anecdotally I've talked to some teachers who say that children's media nowadays is simplified. Less 'difficult' words, always explaining (never leaving things to be figured out by the consumer).
Just a last comment, we're kind of off the rails here. I'll read your reply but I won't answer, I hope you're OK with that!
> What you're presenting is a Turing tarpit kind of argument - totally irrelevant to anybody with a sense for practicality.
Not really, it requires very little to do so. Here's how to make fixnum arithmetic go wroom-wroom: https://plaster.tymoon.eu/view/1380#1380
Does that look like a Turing tar-pit to you? Scroll down to the assembly.
I mean, I do think that C-level safety is unacceptable though.
> [...] and half wrong. Yes, UNIX is the worst useable OS, except all the alternatives.
You happen to be misinformed regarding this. It's true today regarding Linux perhaps, but not back then.
>I suggest actually reading my comments, because I've written all that I have to say. In one sentence,
Didn't you just say that empirical evidence points towards C being fast? That's not enough.
Better or more performant for some measure of performance? I mean, you can always read the UNIX hater's handbook if you're interested in qualities that UNIX did not possess decades ago.
>You need much more sufficient-smartness to make LISP fast. Isn't it obvious? Or is that somehow counter to any history you've read, except when cherry-picked and reinterpreted by some HN commenter?
If you want to make a pedantic argument, then no, it's not difficult to make Common Lisp potentially as fast as C. This is because I can very easily drop down to a level of safety which is on the same level as C. This is, of course, unsafe and I would never recommend it.
I don't understand why numerics performance is cherry-picking, but "systems programming" (what does that mean? OS dev. only?) is not.
This would be a much simpler discussion if you concisely describe in a semi-formal manner why C has a larger potential to be fast than CL. If you did so, it probably would be a lot more difficult for me or anyone else to refute your claims.
Alright, but to what degree is the latter the cause of the former? The OP has already noted that C used to not be very fast, and that it became fast through the rise of sufficiently smart compilers. Do you dispute this claim?
>Why don't you try improving SBCL times there and then come back?
What good would that do? You have already seceded that you can write a C-like program in Common Lisp. This is especially true in SBCL, where you could write a Lisp program to generate the correct assembly code for the program.
Why? What even was the point in making them 'typed' then?
Also, what exactly are the relevant language-level details which BOSQUE contributes? It seems more like a large library than anything else.
He's basically telling you to educate yourself ;-)
Push ups aren't bad, but training your pecs and anterior delts only is a bad idea to do, especially for someone who sits at a computer all day. Get a band and at least do some pull aparts with it, 200 or so every week.
GDPR is a massive win for the individual.
I didn't realise that SBCL is interpreted.
1. Having a finite set of variables with a finite set of possible values
2. Having a finite set of propagators which are monotonic on variables (that is, it either reduces the amount of possible values for a variable or does not (it never adds).
3. A space describing a full set of variables and propagators
4. A way of reducing the amount of values when all propagators have hit a fixpoint for some space.
5. A way of rewinding state when some variable runs out of possible values
And then it basically (BASICALLY) runs this loop:
while(!solved(space)) {
if(failed(space)) {
rewind(space);
}
while(!fixpoint(space)) {
for(p in propagators(space))
{ p(space);
}
}
make_choice(space);
}It's mainly used for solving NP-hard problems by being smart when attacking the full search tree.
One (very cool) instance of constraint programming occurs at Ericsson through the Unison project http://unison-code.github.io/ .