juno

There is a reason why most small bands and producers sell through Bandcamp, Beatport, or Juno Records.

Then there is juno and julia studio if you are inclined towards an rstudio like interface.

With Juno imminent, I might just start over and hope the Juno installation isn't so difficult, though that doesn't seem to be a top priority for the developers.

But then again, artists like Kimya Dawson (prior to Juno fame) have organized entire cross-country tours based on word of mouth.

Maybe his experience was exclusive to the way things were run at Juno as opposed to the trading side of the business.

Or you might end up walking from Juno to Omaha beach hoping that you can hitch a ride with some Canadians back to Caen.

I've been playing around with Juno [1] and like it a lot so far.

Compare to Juno which was launched four years later.

On the Juno project we spent several months rearchitecting at one point: just moving things around, cleaning them up, creating base classes that made sense, and creating sharp interfaces between the modules.

The networking situation has improved in Juno and Kilo, but yeah: One often gets the impression with OpenStack that there's so much attention being paid to new stuff that none of the existing stuff (even recently new) is ever brought to a state of stability and usefulness.

The "just preload a malloc that aborts" rationale I got from a friend (then) at Juno.

If I wanted "free" email from Juno, I would have to call within my area code, but outside my exchange and pay per minute.

On a real Juno, half of the voice cards would be dead.

I've been using Julia through LightTable and Juno, which makes these types of iterations and experimentation WAY easier and faster.

Instead of Julia Studio, I would recommend Juno[0], the IDE based off of LightTable.