Parrot 0.5.0 was released just over a week ago. As this article discusses, one of the major changes was the transition to NQP.
While NQP brings some very interesting technical benefits, it also further shows one of the significant problems with Parrot that I identified a couple of months back. Namely, the near complete lack of design and architecture stability as the project matures.
Today I was reading an article concerning the design of new back and forward buttons for Firefox. While such thought and experimentation has its place, I’m not so sure it’s appropriate considering the current state of the Firefox codebase.
Recently, I read about how, as of the middle of November 2007, there were about 700 blocker bugs against Firefox 3.0. It is anticipated that about 80% of those bugs will not be fixed before Firefox 3.0 is released. And this is for a release that is already a number of months behind schedule.
For the past couple of weeks I have been working with a very interesting system administrator. He’s responsible for maintaining a large number of Web servers, mail servers, and database servers. Like most system administrators, he employs a number of scripts he’s developed to automate a variety of tasks. While most sysadmins would use a language like Perl or Python for developing their scripts, this fellow uses Haskell. Of course, I asked him why he used Haskell. His answers really aren’t surprising to somebody who has used Haskell before.
Although it hasn’t (yet?) caught on much in industry, anyone who follows modern computing trends will no doubt have heard of D. Its Web site describes it quite nicely: D is a systems programming language. Its focus is on combining the power and high performance of C and C++ with the programmer productivity of modern languages like Ruby and Python. Special attention is given to the needs of quality assurance, documentation, management, portability and reliability. The D language is statically typed and compiles directly to machine code. It’s multiparadigm, supporting many programming styles: imperative, object oriented, and metaprogramming. It’s a member of the C syntax family, and its appearance is very similar to that of C++.