After re-downloading the model, do not use --dry-multiplier... and also, don't ask me how I know...

Is it called node because of its inode usage?! Jokes aside, it's just crazy how big node_modules can become for a simple app! I was kind of surprise the first time I got a "no space left on device" error and df shows < 50% of usage :/

If you're talking about project.json, it's already dead :/ http://xoofx.com/blog/2016/05/11/goodbye-project-json/

No I'm talking about the version numbers themselves, things like: 1.0.0-preview2-final I will not take a working(and money-making) code base and migrate it to a platform where that is the version I need to use.

As for project.json. I actually liked using JSON over XML, but it's a personal preference thing, can't really make a case that it's better.

I was wondering, what would happen if the algorithm create an existing riff and use it in a composition? Gotye use a riff from "Luiz Bonfá - Seville" in "Somebody I Used to Know" and it costs him 1M$

There's an interesting presentation on cockroachdb https://www.youtube.com/watch?v=MEAuFgsmND0

It's the price to pay for implementing generics via type erasure, not for getting functional features in a statically typed language. http://stackoverflow.com/a/24421331

This isn't necessarily due to erasure. This actually about boxing. Reified generics is one way to solve this. Another option is tagged pointers. That is how OCaml handles this[1].

[1] http://stackoverflow.com/questions/3773985/why-is-an-int-in-...

edit: clarity

That was an interesting read. Thanks for the link. It also confirms what I always thought about their 'model'.

It remembers me this http://yacy.net/en/

Already exists http://briangreen.net/2010/11/diy-ultralight-faraday-cage-po... lol