106 karma · joined October 28, 2015
I don't think he addresses this subject in the book or in his talks, but it would be interesting to know his opinion on the subject.
So 100g of carbs seems like a reasonable number if you want to be sure that your subjects do not enter ketosis.
What's the difference between Alan Platform and Apache Isis?
"War on/against x" is becoming a meaningless expression.
As far as I can see, our only real plan is: we'll invent something. The rest is just rhetoric.
I mean, in theory the market should push the profit down to a minimum, forcing the miners to spend their revenues in order to keep mining.
You might be able to give up control over something, but never the responsibility that comes with it. So in this particular case, we are free to let the algorithm decide for us, but we should all be aware who will suffer when the algorithm goes haywire. It's that simple.
https://think.ing.com/uploads/reports/171218_Why_Bitcoin_to_...
When you work for a charity, do you ask for a raise? Do you get a bonus if you collect more money? How much to you get to keep?
Not even mentioning that sometimes the money goes through a chain of charities, all making a living out of it, but leaving almost nothing for the final beneficiary.
He was just trying to emphasize, what in his view is a discrepancy between what some people preach and what they do.
Don't get me wrong, I like Kotlin, but Ceylon did the multi platform thing much better.
They have real platform modules, built into the language (not just a build tool trick), and a language specification that was written from the start with multiple platforms in mind.
But it never took off (yet), and Kotlin's support is good enough, so it will have to do I guess :).
- the parity ethereum client: https://github.com/paritytech/parity
- the exonum framework: https://exonum.com/
But just as a counter-argument, look how a simple lock looks like in Rust [1]:
fn main() {
let counter = Arc::new(Mutex::new(0));
let mut handles = vec![];
for _ in 0..10 {
let counter = counter.clone();
let handle = thread::spawn(move || {
let mut num = counter.lock().unwrap();
*num += 1;
});
handles.push(handle);
}
//...
}
----- edit: Just to clarify my point. The ownership model is a beautiful solution to the resource management problem. And as the parent pointed out, some concepts can be cleanly borrowed/reused in other languages.
But now, in Rust, in practice, you realize that this model requires a lot of boilerplate code just to make the borrow checker happy, even for simple things like using a lock: create Arc(Mutex(data)); clone the arc reference; move the new Arc reference to the new thread.
Now, my predicament: I love Rust's type system and tooling, but it's really hard to justify to myself the pain of writing correct Rust code (borrowing, lifetimes, etc.) when I know I can get almost the same effect by using a GC language + immutable messages.
And I don't need that last drop of performance either.
So if you just want a native language with a good type system and a growing ecosystem, where do you go? Still Rust or something else?
I'm sorry, but you can't brush that subject off with a single sentence. It's a huge problem. If you want a real currency, that is.
You might hope that the free market will fix this problem, but I have my doubts. The current whales don't have a real incentive to sell.
And if Bitcoin would reach its goal, we would have some new, anonymous and untouchable overlords that would make the feudal ones look like amateurs. No thanks.
But could you please shed some light on this sentence:
> Yet, bonobos are indeed known for organizing attacks on neighboring primate groups
Are those primates other bonobos? That could be called going to war. If not, it's called hunting: those other primates are just food. It's not like we go to war against whatever other animals we are eating.
I've been reading some books on the subject that claim the contrary, also based on archaeological proofs (and on identifying faults with the existing studies). So I wouldn't state that with such confidence.
See RoboTeddy's comment for some details on this POV.
And also, if we look at bonobos, another primate closely related to us, we might get a completely different perspective on life in the distant past. It's just that we discovered chimpanzees first.
30% unsuitable for human consumption? This choosiness is a just one more sign of affluence and one of the habits we have to get rid of if we want to improve our ecological footprint.
Go to a rural village in a developing country and you will see them using 95% easily.
This is just
2. Not all properties are relevant or even desirable: For example, I could live without POW or a fixed cap.
3. That being said, let me give you an example of a currency that could realistically be adopted by a government: a centrally controlled currency (the central bank is the only miner) but the blocks are validated by the citizens.
Here you could have the inflation rate specified through a smart contract (e.g. 3%). The only way to print more money would be to to ask the nodes to vote on an amount that will be included in the next block.
Basically the nodes that have a stake in the system are allowed to vote on the direction the project is going.
My personal impression is that currently this model is still very rudimentary, but in the future I could still an almost autonomous system taking off.
They talk about modules and I am curious about their syntax (if any). If we are to support a new multi-platform ecosystem, we should make sure it is built on a stable foundation.
For example, I really like scala, but I can't convince myself to try scala-js due to the unsoundness of the platform. Some scala libraries work, some libraries compile but won't work as expected and some libraries need porting. And you don't really know which is which.
1. Angular 2 is not object oriented in the standard meaning of the term: it does not rely on inheritance or polymorphism that much.
But it does rely on classes as the backing structure of your UI components. In other words, they tried to create a platform for creating widgets that compose. And more or less succeeded.
This is a tried and true pattern that has been used to create complex user interfaces since forever. I would wait a while before claiming that this stile is obsolete.
2. Angular 2 is quite functional.
Decorators in Javascript are just higher order functions (like python I guess). They look like like Java's annotations, but work in a completely different way.
They made streams (RxJs) the standard way of working with data.
And pipes are also a functional construct.
3. There are some good things to say about their routing module too, but I have to go.
Anyway, my opinion is that Angular and React address different needs and there is definitely room for both of them.
Almost nobody will leave his job / stop looking for one / risk a complete career change if that income is not guaranteed for life.
wait until we'll know everything our own gut bacteria is doing to us
- So you are talking about how much value we create and that we should receive more of it.
- Then someone else mentions a lot of other professions that do that too: create a lot of value.
- Now the discussion does a 180, forgetting completely the first topic: value. Now it's about supply and demand.
Pick your measuring stick people.
You either trust that markets work best and then you are paid exactly what you deserve, because you are free to change jobs and ask for more.
Or you don't and think that a better system should be in place, but then it should apply to everybody, not just software developers, right?
You keep telling developers that they are not good enough but they should rest assured that some smarter people are working on the problem and they'll come back with the answers.
When in reality, I think that all developers, when using a library, would like to think that they could have written it themselves, it they would have had the time or the interest.
They corrupt the developers, because the purpose is no longer to create a great product. You now have to think on how to:
* tweak your product to accommodate ads
* trick the user to comeback even when he shouldn't have to
* collect as much data about the user as you can
And they corrupt content creators, because it makes them focus on volume (views) instead of quality.
And yes, we painted ourselves into this corner, where is really tough to make it without using ads. But that doesn't mean we shouldn't explore other options. And without ad blockers, the industry will have no motivation to search for alternatives.