I know… this is going to be ‘another one of those threads’; however, I feel the need to make some very distinct clarifications here. First of all, some of you may or may not have been keeping up with the Brad fiasco. He continuously bashes Xojo and its employees on his personal blog… the late of which is an issue he has with Greg and the sslSocket (more specifically, a blog he created detailing the configuration of such). Early this year, after some personal trouble with Firefox complaining about my security certificate I found an issue where Xojo was not properly relaying the intermediate certificates. I published my findings on the forums, and filed a feedback indicating my findings (with some resistance). I thought nothing much about this afterwards, until I seen Greg’s recent reply in the thread stating browers he has tested ‘appear to be working fine’ thus validating there likely isn’t anything wrong with the socket. This, along with no forward movement on my ticket got me upset, because in my feedback submission and forum posts about this… I thought I made it very clear that you can’t test this issue using solely the brower’s response, and gave multiple tools to test with (any one of them takes a few seconds, and will let you know specifically what the SSL certificate issue is… which was clarified by how quickly Travis was able to verify the issue). My ‘rant’ had nothing to do with Brad, his feelings about Xojo, nor do I agree with his remarks… although I can understand PART of his frustrations.
That said, I enjoy using (for the most part) Xojo, and will likely continue to do so… baring that these kinds of resistance on possible bug entries aren’t quickly to appear. We’re encouraged to submit bug reports (and I feel the lack of doing so has been the focus point on regressed issues by employees in the past [ie. Why hasn’t somebody tested this before and filed a report?]). I have a regressed bug filed (linux distributed console applications will not run ANY threads except the main thread if .isDaemonized is used; therefore, my application will only run properly when appending & to the filename and removing any .isDaemonized calls within the code) that has been sitting in feedback for weeks without even a review. If you want us to submit these tickets, don’t be quick to give us resistance that we’re wasting our time ‘because it’s not really a bug’ without even taking the steps to verify it first. If I have to take my time to put as much information to replicate an issue, along with tools to test the bug, multiple times… and they get ignored… I get pissed, as I think anybody else would. It makes me wonder why I’m even bothering and wasting my time submitting.
Unlike Brad, I think Greg was quick on the draw and made an honest mistake (I don’t think he intentionally lied or misdirected anybody). Whether it be lack of experience (we’ve all been there, and still are… I’m all the time making stupid mistakes and learning things), or some other issue… I think it’s very clear he’s an asset to the Xojo community, and appreciate his support in the forums.
And now, a quick message to Brad… because I know he’s lurking. I think what you’re doing is, at the least, borderline childish. You’ve toyed the line with free-speech and have, very clearly, over stepped that into defamation of character against Greg (and possibly other employees). I would advise you to stop, but don’t think you will. Just know, anything you say and do can and will likely be used against you. You can tell yourself that there’s no way that could/would happen; however, your intent is very clear on what you’re trying to accomplish… and that’s to give Xojo and it’s employees a bad rep. Stating facts about a product or service, or an issue you have/had with it is one thing… but intermingling it with personal attacks makes it defamation. Is your dislike worth the risks?