Thank heaven for community supported firmware - Amen.

Definitely avoid charging for CM - that will put a total damper on community enthusiasm. The better approach would be to rationalize builds - we don't have to have nightly builds. IMHO even weekly builds would be plenty.

Weekly builds would be fine if the nightlies never broke. But nightlies often do break. So you end up using yesterdays or the day before. But going in back in time with weeklies pushes you back much quicker.

However, there may emerge a development process that obviates some of those breakages.

Anyone else having compile issues? I'm on Ubuntu 11.10 (Server x64) and make fails consistently.

Yes, I get some 32-bit issues, gfortran and some packages (-dev) were not installed, still getting an error 139:

JULIA sys0.ji Segmentation fault make: [sys0.ji] Fehler 139

Is it due to openblas not building? This may help:

https://github.com/JuliaLang/julia/issues/370

Thanks for your suggestion. I tried that, but it wasn't it. I'm still getting lots of build errors, culminating with this:

Saving to: `lapack-3.4.0.tgz'

2012-02-19 01:03:26 (55.3 KB/s) - `lapack-3.4.0.tgz' saved [6127787/6127787]

make[3]: gfortran: Command not found make[3]: * [lsame.o] Error 127 /bin/sh: ./testlsame: not found /bin/sh: ./testslamch: not found /bin/sh: ./testdlamch: not found /bin/sh: ./testsecond: not found /bin/sh: ./testdsecnd: not found /bin/sh: ./testieee: not found /bin/sh: ./testversion: not found make[2]: * [lapack_install] Error 127 make[1]: * [lapack-3.4.0/INSTALL/dlamch.o] Error 2 make: * [julia-release] Error 2

Is package gfortran installed?

@olaf: I was missing gfortran and libncurses5-dev. It's working now, sweet. :)

make worked very smoothly here on my Mac, downloaded and installed its own deps.

Great work guys.

This is very exciting - congratulations on the launch of Julia. Now good luck as you move towards building a strong community!

Python does have the strength in all the powerful libraries it makes available to you, and that may be a determining factor in the relative popularity of Python v. Ruby in the future.

I've used Python for many years but recently took a serious look at Ruby to see what it has. I haven't looked back - I found Ruby to be less verbose and still easy to read, and very enjoyable to code in. Python was enjoyable too, but for me, Ruby much more so.

I'm glad to learn the jury made the right decision. Sometimes it seems too much to expect even that much. Something really needs to be done to fix this nature of trolling.