zkhalique

Whether it's Angular doing dirty-checking in the $digest cycle or React walking the virtual DOM and doing dirty-checking?

Why not just subscribe to events and update things when the model changes? That would seem to be far more efficient, and also make clear the mapping of dependencies of views on data.

Looks like some experts agree w me: http://www.space.com/21333-asteroid-nuke-spacecraft-mission....

What will really change real estate patterns is increased support for telecommuting, both with tools and cultural acceptance.

What I wonder is, how is inflation being calculated in terms of the CPI, which is essentially prices in dollars? After all, what exactly is being measured by this? If dollars the very currency which is being printed, how does measuring prices account for how much M0 money there is?

I mean logically, if they've already given you the money and there isn't any way they can take over governance of the company, then the only leverage I can think of is signaling in future rounds. And if you weren't even going to raise one VC round, then at that point you may as well raise exactly one and then signaling is irrelevant. Yes you've diluted yourself 20% and now you've got a board member that wants you to grow fast, but so do you. Of course, I'm assuming here that you failed to raise on Kickstarter, and you aren't making enough $ to hire people to do development/testing/security/evangelism/PR/marketing/operations/etc. anytime soon. Why waste years of your life when you can hand the project off eventually to a community you've built, and move on? If you want to retain control over the project forever, can always be BDFL of the community, at least until some better-funded company forks it. I just really want to understand, what is the reason that guys like DHH say VC can control you after you take their money?

There is a reason why Apple makes every app implement its own receipt validation scheme. So a dedicated attacker can't crack all apps at once. Same here.

Like this:

hash = sha1 applied recursively 4071 times ( password . salt ) . salt

Serious question. Don't just say religiously, "just use bcrypt". Tell me what is really wrong. What attacks will succeed today? Any crypto enthusiasts in the audience?

It is not really measuring the time you're going to be up. That interpretation is based on faulty assumptions. It's like the statement "the sun will burn out before one bit is flipped" is wrong. It is quite likely that by that time, all the bits will be gone.

https://signalvnoise.com/posts/3067-lets-get-honest-about-up...

The other philosophy that thought about this, but on a more intellectual level, was Stoicism, which was very popular in the Roman empire.

(a lie, I added $14k to the original offer)

See... it's hard to be "totally honest" in sales, even of your own time, because of the red queen effect.

This was an integral step in the process of raising your salary. If you volunteer all information honestly, I am pretty sure that most players in the system will not have an obvious path to increasing your salary. Otherwise it would represent an arbitrage opportunity for everyone.

So yes, for append-only tree structures, this may work. In terms, of say, a Google Doc that means you can never delete or insert any text, but only append text to the end of paragraphs etc. Certainly very limiting.

Unless there's something you haven't described, in which case I encourage you to provide a more in-depth comment describing a solution for actually inserting or modifying the tree.

Many users want to do things with other users

That means there has to be a way to persist state and history (of a group activity, an evolving resource, etc.) across machines. Mental poker is still very hard to do for groups. Since most clients will not have amazing uptime, that means you still need a network of servers. Servers that manage security behind a firewall.

So, the conclusion is -- for group writable data, the best you can do is have servers be completely interchangeable, but you will still need servers and networks of servers.

The good news is, many of the challenges are orthogonal to each other. Someone's building a Mesh network, for instance. Someone else is building the protocol layer with IPFS. We're building the social layer for this coming web.

Money has been decentralized.

Social networking hasn't, yet.

Security hasn't, not really. Have you installed the latest SquirrelMail patches yet? You probably use GMail so you don't have to worry about it.

But, are the people in the exam allowed to use the internet?

This is an interesting question (and somewhat meta, given the question itself) about test taking today. What is the point of remembering all that knowledge if you can look it up and understand it quickly?

I think that, if a cache is combined with a push indicating a change, then it's basically a local "eventually consistent replica" which catches up as soon as there is a connection to the source of truth.

Seriously, many times you are READING data which changes rarely (read: every X minutes / hours / days). So, in the meantime, every code path that will need access to the data may as well look in the local snapshot first.

The question about consistency is an interesting one. The client's view of the authoritative server state may be slightly out of date, when the user issues a request. If certain events happened in the meantime that affect the user's view, then the action can just be kicked back to the user, to be resolved. But 90%+ of the time, the view depends on 10 things that "change rarely", so a cache is a great improvement.

Related issues involve batching / throttling / waiting for already-sent requests to complete.

PS: That was quick. I posted this and literally 10 seconds later it got a downvote.

Check this out instead:

https://crowdprocess.com/