On Thursday, 4 July 2013 18:35:28 UTC+1, Ash Moran wrote: > > > > The current development environment is such that newer features are > either very slow or impossible to develop. > This bears repeating: it's more important to understand why this is the > case than to solve the problem this time round. >
So for example : Something that was added recently was a click-tracking feature for emails sent out of the system. A complete HTML Parsing library had to be written from scratch. And I mean - from scratch. This sort of problem is traditionally difficult, but I really shouldn't have to write a state machine to parse HTML. Other examples : The language can only talk ASCII. RESTful web calls can only be provided by having the native web interface wrapped in Classic ASP. Sending JSON is possible with the latest beta version of the language, but Structures passed in must be strictly typed. It's slower than RAILS. The latest changes to the web framework are possibly a mistake. Most Damning of all is the fact that the language is dying. The numbers of people coding in it are dropping year on year. The only coders I'll ever be able to find for the language will be based in other countries, The number of developers in the UK for this language is probably less than 100. I can see where you're coming from, and believe me when I say that I have serious concerns about doing a rewrite in a whole new language. But the main impetus to this rewrite is not because the system is wrong. It's because the language is wrong; it's old and you can't get developers. > -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nwrug-members. For more options, visit https://groups.google.com/groups/opt_out.
