I'm surprised there is anyone on this forum (other than me) that is that old!
Understood - I remember them all - SMAC, SCRIPT, SAMS, SCAMP etc.!
Raven, FINN (IBM ?) and that product developed by Patrick Bird in AVON LA (as it used to be) - what was it called ?
I think that software that can improve children's lives is *very* exciting, which is why I like this job so much! The purchase or licensing cost isn't the main issue, the support is where there will always be a cost centre - and that's the same whether you're open or closed source. Although i'm an OSS fan, I can see a strong case for keeping source closed in order to keep the vendor viable.

Personally I think we should go back to paper files and trusting the school secretary to know all the gossip.![]()
![]()
There are published guidelines and a fairly precise data dictionary for CTF exchange, along with an xsd schema, etc. I've not looked too closely at the SIF stuff for data interchange as the configurability of sims, serco, etc renders a lot of it moot. There are plenty of published information standards though.

Oh, of course not. But I, as a programmer, find applications that I can't work with without wading through a mass of bureaucracy first to be dull. If I have to sign NDAs, argue with support people to get access to APIs or figure out undocumented utilities myself I get fed up and start thinking about alternatives to the system I'm using - programming is complex enough without adding unnecessary complications. If you want an application to be considered interesting by your average programmer, emulate the best of what you can see around today - Google, Amazon, Apple, Microsoft and so on all making well-documented APIs available so developers can work on applications at their own pace and to their (and their users') own requirements.
--
David Hicks
There are currently 1 users browsing this thread. (0 members and 1 guests)