Reply to thread

Message

<blockquote data-quote="Klintus Fang" data-source="post: 424330" data-attributes="member: 3580">but it all does point at an interesting thought.&nbsp; a tcp/ip solution might be a work-around for language or compiler issues, though I think there are better solutions if that's the only problem.&nbsp; I still don't think it helps cross-platform issues.&nbsp; the only way I see to do that is to use languages that compile on multiple os's and rip out the os-specific code; likely the guis.&nbsp; Unless the language you are using is Java, in which case things are usually portable (but I really do get annoyed when I have to install company C's x-y-z version of Java just to use some tool that I just downloaded).my personal coding style has always been to write most everything with text interfaces using stdin and stdout and/or file i/o so I can compile them anywhere and if the thing really needs a gui to be fully functionally later I worry about that at the end.&nbsp; devoloping from the outset with everything meshed into the gui code really leaves you in a pickle if you want any sort of cross-platform ability.&nbsp; but that is neither here nor there.&nbsp; just a suggestion about how to be more multiple os compliant without relying on java.</blockquote>

[QUOTE="Klintus Fang, post: 424330, member: 3580"] but it all does point at an interesting thought. a tcp/ip solution might be a work-around for language or compiler issues, though I think there are better solutions if that's the only problem. I still don't think it helps cross-platform issues. the only way I see to do that is to use languages that compile on multiple os's and rip out the os-specific code; likely the guis. Unless the language you are using is Java, in which case things are usually portable (but I really do get annoyed when I have to install company C's x-y-z version of Java just to use some tool that I just downloaded). my personal coding style has always been to write most everything with text interfaces using stdin and stdout and/or file i/o so I can compile them anywhere and if the thing really needs a gui to be fully functionally later I worry about that at the end. devoloping from the outset with everything meshed into the gui code really leaves you in a pickle if you want any sort of cross-platform ability. but that is neither here nor there. just a suggestion about how to be more multiple os compliant without relying on java. [/QUOTE]

Verification