> WARNING WARNING WARNING: qhasm is in prototype form. The existing qhasm tools and interfaces have produced high-speed professional-quality software for several applications, but they are not themselves professional-quality tools; they have many known deficiencies and many sharp corners. Each of the qhasm tools has at least one complete rewrite planned. The .q language is not stable; if you write .q files then you should plan on having to modify them extensively for future qhasm releases. The machine-description language has a stable structure but is still undergoing tweaks; I can incorporate machine descriptions into qhasm and keep them up to date, but I won't promise that non-incorporated descriptions will continue to work. The prototypes of qhasm's cycle counter, range analyzer, and scheduler are several generations behind the current .q language and, as a practical matter, aren't usable right now.

Seems like quite a lot would need to be done, even if it works to some degree. Have you tried it? (I haven't.)

> Not scared? Okay. Here's how to download...

I have had a great user experience with all his other software except one[1]. Thus I was not scared. High learning curve, but high reward.

1. A FORTH he wrote for IOCCC. Problems compiling probably due to my own stupidity.

I love programs that are just that well-written that they don't need an update twice a week. I like this philosophy way more than 'we only use the newest technology'. This is actually a lot of companies say. Then, they demand their workers come in 4 evenings a week for seminars and workshops, unpaid. No wonder if employees have to learn docker, git, redux, jquery, django, azure, mercurial, specflow, angular, selenium, design patterns, ...