The problem is that you guys didn't (do it properly), and now have to emit 'fix-me-ups'.blast wrote:We'd do it properly and add support for the features to the API.
And he bashes my choice of language for doing it in --- as if I had suggested should switch his language to what I prefer to use. Read between the lines.blast wrote:He didn't suggest that you suggested that. He specifically mentioned writing a plugin. Please try to read all the words.
Yes, he mentioned server. But do you know what 'context' means ?blast wrote:Again, try to read all the words. He specifically said the server.
So he bashes me ("What a colossal waste of time this has been") because I was stupid enough to ask a legitimate question about the API and am not using his preferred choice of language ? Quite a way to make a new guy feel welcome people. Well done.blast wrote:The number of public Windows servers is either zero or could be counted on a single hand.
Keep your warm welcomes up and you will become even less popular than before.blast wrote:Also, popularity? What popularity? Have you seen the player counts lately? We are not popular.
FYI: I'm using the server when I host LAN games, (viewing the result of) world-editing and experiments. If I would have had the client only I would have dropped the game quite a while ago.
I have no idea what you mean here. As far as I can see I was defending myself from an unwarrented attack.blast wrote:Sounds like some advice that you should follow yourself.Beardy wrote:In short: Get off your high horse, you're not making much sense.
Bullsh*t. It does what the programmer wants it to do.blast wrote:Because it's an API. That's what APIs do.
I supposed you missed the "(copies of)" and "(read) access" bits ? How would handling copies lead to instability ?blast wrote:Allowing direct access to the internals of the server would lead to instability and wackyness
The "proper" way would have been to inventorise before implementing.blast wrote:So, the proper way for your idea to work is to just extend the API to expose the necessary features.
I'm was not. That is why I used "(afaics)".blast wrote:Why are you so sure they are non-portable?
Because although I most Windows OSes have JS I do not use google chrome ? Poof. In that case not even portable within the same OS.blast wrote:The JS one appears to be usable with Linux and Windows, and probably OSX. It is written as a proper BZFS plugin and uses the V8 JavaScript engine that powers Google Chrome. So how is that not portable?
But yes, I did not realize that VC8 could have such support build-in.