- Jonathan Hartley
- Programmer
Eschewed established programming languages like C# in favour of IronPython
Wrote lots of our own internal infrastructure
Typical of small technically-savvy startup
Niche implementation of a niche language
Python & Open Source have low penetration within technically conservative client organisations
Microsoft's acquisition of IronPython was a trifle worrying
Dynamic languages reputedly slow & unscalable
More functionality with less effort
Embedded in our product as a scripting language
User's cell formula & macros are written in the same language as the application
Dynamic typing matches user expectation for spreadsheet formulae syntax
Microsoft managing IronPython very well (eg. accepting and responding to bug reports)
Resolver One the world's largest IronPython application
Is a fully-interoperable .Net language
Client's spreadsheets can very easily use in-house or third-party components, commonly written in .Net languages like C#, VB.Net, etc.
Gained credibility amongst our .Net-oriented clients from the acquisition by Microsoft
Dynamic languages a natural fit for Test-driven development (TDD)
"Doesn't that halve your development speed?"
Good product & happy developers
Can't imagine doing future software development without it
Didn't set out to roll-our-own, but gradually accreted small improvements.
Replaced Cruise Control with a custom script
Test runner publishes results to a database
Distributed test runner spreads the load across idle PCs.
"Doesn't that halve your development speed AGAIN?"