Jerome Haltom schrieb: > Well, yeah. JScript is a poor choice for anything, but at the same time, > it worked. I'd have liked to take it all the way, turning it into a > "Real Program". In fact, somebody should do this. =) > > I will say though I would argue against using any technology that isn't > "Windows native". That is, I would argue against using Python, or POSIX > shell. I think there's something to be said in this space that if you > want Windows admins to use and modify it, you need it to be built in > something familiar to Windows admins. A Java stack is not that. Python > would be closer.
Yes, that's true. Using an interpreted language included in Windows, for a sub-100 kB file everyone can view/edit/correct is a clear advantage, and it doesn't scare people away (think of what I've written about adamoto, which depended on perl/java/tomcat/etc.). Not having to install any 3rd party stuff is nice, too (well, there is a WPKG Client now, but it's not obligatory, and I think/hope most users like it). Having said that, JScript is not very portable - I would still like to have something comparable to WPKG for administering multiple Linux machines. Any takers? :) -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ wpkg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wpkg-users
