<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 13, 2016, at 7:24 PM, Shyamal Chandra <<a href="mailto:shyamalc@gmail.com" class="">shyamalc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Could you give me examples of what I said was clearly "unprofessional”? </div></div></blockquote><div><br class=""></div><div>Well, starting with the title of the thread, as others have noted. You’re coming across as very confrontational and, well, entitled.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""> Two months for a bug because open source is "do it yourself". This sounds like a crappy support team by a large multinational company that open sources non-functional Linux ports of its language. </div></div></blockquote><div><br class=""></div><div>Open source does not imply full support. It’s just making the code available. My understanding is that most of the Linux work is being done by volunteers.</div><div><br class=""></div><div>Second, a lot of people here would disagree that the Linux version of Swift is “non-functional”. You’re extrapolating from one problem that you ran into; if a lot of people were hitting that problem, it would have been more of a priority to fix (and you’d see notes from other people on the bug report, or reports of duplicates), so I’m assuming you’re the only one. Yes, it’s frustrating to be hit by an apparently-rare issue, but that doesn’t mean the software is broken.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">I gave clear examples and bugs so I don't understand why you are getting defensive and hammering me with the "unprofessional" word. </div></div></blockquote><div><br class=""></div><div>Because your language and tone are confrontational and offensive. If you’re not willing to recognize that, I’m not sure what to suggest. Better communication skills will get you farther in the long run than just arguing louder and more vehemently.</div><div><br class=""></div><div><blockquote type="cite" class=""><span style="font-family: Alegreya-Regular;" class="">First, address the issues and the bugs; I gave you clear examples and you circumvent those issues and flag the post because you don't want to confront that the tooling is buggy and flaky.</span></blockquote><div><br class=""></div>You’ve pointed out <i class="">two</i> bugs that you filed. It’s good that you filed them! But that’s neither an impressive number to report, nor a ridiculous number of bugs in a product. So I’m not sure what you’re attempting to justify.<br class=""><br class=""></div><div>—Jens</div></div></body></html>