It feels very much like the next step after jquery+templates. The nice part is that this enables you to choose your own strategy. For instance only using small amounts of code and regular forms. It requires a lot of decisions about structure decided already in a lot of js mvvm frameworks. These frameworks look like rails for client-side coding. Great for certain types of problems, but requires learning how to use it. Like always, if you can accept the limitations you get a boon. The big problem is that it’[...]

Turns out bundler does have documentation related to Bundler.with_clean_env. You just have to read the bundler.io man pages or the man pages for bundler exec.

Using ruby is kind of easy in the beginning. We started by having a folder of loose scripts. This turned a bit messy after a while. By moving these to separate gems we got some needed structure. Many of the programmers complained about globally installed gems (i.e. our local gems). In order to get a predictable executing environment we started to levarage bundler more and more. Turns out that there is a gotcha: Executing a bundle exec script inside a bundle exec script. The inside script will inherit the e[...]

Big news. Microsoft releases the next c# and vb.net compiler as open source. Miquel de Icaza speaks of making it work on mono as well. It’s licensed under Apache license.

In order to setup ci for open source targeting c# projects I looked into using travis. There is a solution on stackoverflow. The post got me started. Turns out that there are some problems with using nuget packages for mono using xbuild (Path.Combine in the msbuild file NuGet.targets is not supported yet). I patched NuGet.targets to accept parameters (thus I can supply the correct paths using albacore). I’ve added the variable PackagesConfig to all the csproj files in the solutions: <PackagesConfig>$[...]