On Tue, May 28, 2013 at 9:53 PM, Glenn Fowler <[email protected]> wrote: > > although vms are a good solution for some problems > I can personally report more businesses (retail, hospitals!) > still using windows xp on standalone pcs than I can count > on my fingers and toes -- not that they should be, but lets assume > for some reason out of their control they are stuck with it > > there are a lot more situations where standalone systems are the norm > > ast and uwin came about because of a need for portability on existing plant, > the need for a reliable, familiar and reproducable way to monitor and control > the plant, > and the need for a pathway to preserve parts of the environment when the > plant eventually changes > > re research > > although uwin and ast are visible parts of att research > it does not represent all of the work dgk and I are involved with > > they are part of a toolbag that lets us quickly gain traction > in legacy and new projects, and quickly design, test and propagate new > algorithms, > usually engineered inside familiar apis
The problem is that your work, your toolbag, is rotting away beneath your feet and without some investment in documentation, API updates, usability, developer friendliness, UWIN will soon become obsolete. It is already in too many cases. You have to do something at this point. Not later, not in the future, NOW!! Irek _______________________________________________ uwin-users mailing list [email protected] http://lists.research.att.com/mailman/listinfo/uwin-users
