20.08.2017, 22:31
(
Последний раз редактировалось TheCman; 21.08.2017 в 01:45.
)
(Sorry for the double post, different recipient and long messages...)
@Kaperstone that's totally understandable, and I'm quite biased as not only I got familiar with the C codebase immediately to start tweaking it (missing PVars, can you imagine
it's that old!) so I don't feel scared of the bugs, but also as ****** pointed I'm rather familiar with Python.
Also, I'm not suggesting people port their legacy codebase, that would indeed be a behemoth of a task. More of an easy way out when you don't have a way to do something in pawn and could easily do it in Python: someone wanted HTTPS with the native HTTP handler recently, and I was sad to tell him that it wouldn't work, when really in Python it would have been quite easy to do (and developing a C plugin just for this sounds silly).
That whole Java/Python debate is a different story really, and one that I'd really love to keep outside of this thread - but we can certainly discuss it more in-depth through PM if you want! Basically, Java has unbeatable corporate advantages that only .NET could (and is trying very hard) to match, for example when you're outsourcing development.
I will re-release the plugin at one point anyway, but the reason for this thread is simply for me to see if it's worth documenting it properly or not beforehand - otherwise, it would have been a quiet release without even a notice on the SA-MP forums, which BTW was the original plan before I just "came back".
EDIT: Thinking about it, it would also help that someone with a working Windows toolchain could compile the updated version of the plugin before I start writing anything, I don't feel like most people would be happy to do that themselves.
@Kaperstone that's totally understandable, and I'm quite biased as not only I got familiar with the C codebase immediately to start tweaking it (missing PVars, can you imagine
it's that old!) so I don't feel scared of the bugs, but also as ****** pointed I'm rather familiar with Python.Also, I'm not suggesting people port their legacy codebase, that would indeed be a behemoth of a task. More of an easy way out when you don't have a way to do something in pawn and could easily do it in Python: someone wanted HTTPS with the native HTTP handler recently, and I was sad to tell him that it wouldn't work, when really in Python it would have been quite easy to do (and developing a C plugin just for this sounds silly).
That whole Java/Python debate is a different story really, and one that I'd really love to keep outside of this thread - but we can certainly discuss it more in-depth through PM if you want! Basically, Java has unbeatable corporate advantages that only .NET could (and is trying very hard) to match, for example when you're outsourcing development.
I will re-release the plugin at one point anyway, but the reason for this thread is simply for me to see if it's worth documenting it properly or not beforehand - otherwise, it would have been a quiet release without even a notice on the SA-MP forums, which BTW was the original plan before I just "came back".
EDIT: Thinking about it, it would also help that someone with a working Windows toolchain could compile the updated version of the plugin before I start writing anything, I don't feel like most people would be happy to do that themselves.