maartenba

Turns out pigs can fly!

Really interesting language!

I'm a startup owner myself so really like this type of stories and experiences.

That's a cool approach for working on an MVP (minimum viable product). Instead of pushing something out there and hoping to get feedback, these guys are using the inverse approach and asking people what to build.

Looking forward to reading a follow-up on this with details on how many reactions came aboit and how they handled all that.

Ripple is more aimed at dependency management of components. Much like NuGet (in fact it uses NuGet) combined with direct fetching from Git repos, better resolving of dependencies and such.

OneGet is more aimed at installing system components. It is like Chocolatey (and in fact uses Chocolatey under the hood).

Cool! Pretty similar to what www.phpexcel.net does for PHP.

True that! And I hope more SDK's are shipped in NuGet packages so we can define explicit dependencies instead of implicit ones.

I said "most" projects :-) But even with that I don't have to go through my build logs 50 times before finding out which dependencies have to be installed for the build to work. The build should "just work".

Added a P.S. to the post to reflect this: P.S.: A lot of the new packages like ASP.NET MVC and WebApi, the OData packages and such are being shipped as NuGet packages which is awesome. The ones that I am missing are those that require additional build targets that are typically shiipped in SDK's. Examples are the Windows Azure SDK, database tools and targets, ... I would like those to come aboard the NuGet train!

That is not entirely true. For example the Windows Azure SDK has to be installed. Database tools have to be installed if you want to be able to compile a database project. There are many of the new things that do not follow this approach (hopefully: yet).

The good CPAN times :-) It was a bit of a cumbersome thing to work with as a newbie back then but at least it handled dependencies very well.