you sent me six mails in September, six in October and by November 6th I haver already received three. I did not want to check the all opt out box because I’m interested to be informed about you, but I do not accept to be spammed monthly, so I just checked the damn box.

You used to be nicer, but lately Forrester is much nicer: it only sends two emails per month.

• IIS memory leaks when coding ASP pages because it was a threaded server.
• Huge MS SQL server code in the database because developers came from C/S backgrounds.
• Low level dll development interfacing with .asp pages through COM because .asp was not fast enough.
• Registering manually the COM/VB code each time we had to deploy a new release.
• Sacking MS consutants trying to sell you DNA.

I have no idea about Ruby on Rails, but you can botch a MS stack pretty easily.

Also, why do you want to make the Ruby on Rails comunity angry? I have no doubt they’re rabid fanboys, but I know who you are, so don’t be child and stop nagging the children.

Executing the rsync algorithm on the client side has two main advantages: first of all, you can zsync over any protocol (zsync is able to syncronize over HTTP). Additionally, it avoids the high server load associated with running the algorithm on the server.

Ah! And it is able to handle compressed files.

(defun |#q-reader| (stream sub-char numarg)
  (declare (ignore sub-char numarg))
  (let ((terminator (read-char stream)))
    (loop for ch = (read-char stream)
          until (eql ch terminator)
          collect ch into chars
          finally (return (coerce chars 'string)))))
 
(set-dispatch-macro-character
    #\# #\q #'|#q-reader|)

More information in Space Station Lambda.

You can find CL-INTERPOL in Edi Weitz’s website.

 To avoid loss of face, a Chinese employee will not say that he only understood half of what his expat colleague tells him. This leads to misunderstandings, and ultimately to a lot of time lost.

We encountered a lot of these problems working with the outsourcing team that made all our 3D models. The same mistakes would be made over and over again because the modeling team didn’t understand the comments we made on their work, package names would have spelling errors in them, etc.

Towards the end of the project, these problems gradually became smaller, as Chinese artists started to understand English better and expatriates became more proficient in the Chinese language. More bilingual support, both at Spicy Horse and at the outsourcing studio, would have helped a lot in the beginning, though.
 

Globally, the experience is positive.

After reading the article I don’t know if calling them ‘dynamic
programming languages’ is a good idea. These languages are
useful not because they’re dynamic, but because they make the “idea to
deployment” cycle shorter than previous technologies. This is the main
benefit.

Anyway, the terminology in the computer science world is so complex I
will use the ‘dynamic programming languages’ terminology.

In the Key Findings I’ll like to add not only:

Dynamic programming languages require new best practices, not only
for AD, but also for production capacity planning.

…and application deployment and business processes will require
new practices. With scripting languages (specially if the architecture
is loosely coupled) modifying an application is quicker and
safer than with non-scripting languages. As soon as business people
discover they can move from idea to deployed application in two weeks
the relationship between business and apps. development will change
completely.

But I question why should I integrate dynamic programming languages
with existing software investments? As you explain in the article,
“broad commercial support for dynamic languages remains limited” and
in my experience the community support for languages like Python, Ruby
or Perl is better than initiatives like IronRuby or Groovy. Maybe
integration with existing investments is important, but a better path
would be to integrate through web protocols (REST, SOAP, SOA…) than
to do it thought proprietary/more cumbersome VM interfaces.

Also I would like to comment your report in my blog, does Gartner have
a set of policies for bloggers who want to discuss ‘Gartner only’
reports?