> To be completely clear, it’s not on the “IMMEDIATE” roadmap (as noted in the prior comment). It’s absolutely on the roadmap and I even already started some it in a branch. But as a passion project, we prioritize working on whatever we want and this isn’t currently the priority. It’s high on the list but not like.. next release (“immediate”) priority at the time of this comment.
I mean I can respect that, personally it isn't as a big of deal with me so I use ghostty on my mac but I would still think that I would advocate ghostty only after disclosing this to anyone to be really honest.
Hmm. Still has the biggest issue I’ve observed with AI songs in the past: the lyrics don’t have a consistent or pleasing rhythm. It seems like the lyrics are generated with little regard to rhythm, then the melody is generated and tries to fit the lyrics without being able to change them. The result is a song where verses constantly have too many syllables (resulting in them spilling into the next meter when adjacent verses don’t), or too few syllables (resulting in awkward rests), or syllables with the wrong stresses. Occasionally the singing tries to compensate by just skipping syllables. In the second verse, the word “whispering” is replaced by an indistinct two-syllable word that sounds like “forming”. In the chorus, the phrase “the dimensions” merges the first two syllables to sound like “the mentions”.
Someday, I’m sure, Suno will find a way to fix this issue. But today isn’t that day.
> Personally I didn’t have borrow checker problems, but that’s because before I started using Rust at work I’d designed and built my own borrow checker. I don’t know if that’s a scalable pedagogy.
Yeah... maybe not, but I can see this being a project in an undergraduate course.
Well, according to (ahem) a copy that I found, it only goes up to MRI 1.9 and goes out of its way to say "welp, the world is changing, so we're just going to punt until Ruby stabilizes" which is damn cheating for a standard IMHO
reply