<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Jan 6, 2017 at 2:37 AM, Brady Eidson <span dir="ltr"><<a href="mailto:beidson@apple.com" target="_blank">beidson@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><span class="gmail-"><div>On Jan 5, 2017, at 12:48 AM, Yusuke SUZUKI <<a href="mailto:utatane.tea@gmail.com" target="_blank">utatane.tea@gmail.com</a>> wrote:</div><br class="gmail-m_3976865605891839724Apple-interchange-newline"></span><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-">On Thu, Jan 5, 2017 at 5:43 PM, Darin Adler <span dir="ltr"><<a href="mailto:darin@apple.com" target="_blank">darin@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I understand the appeal of “org.webkit” and structured names but personally I would prefer to read names that look like titles and are made up of words with spaces, like these:<br>
<br>
“WebKit: Image Decoder”, rather than “org.webkit.ImageDecoder”.<br>
“WebKit: JavaScript DFG Compiler” rather than “org.webkit.jsc.DFGCompiler”.<br>
<br>
Not sure how well that would generalize to all the different names.<br>
<br>
I like the idea of having a smart way of automatically making a shorter name for the platforms that have shorter length limits.<br></blockquote><div><br></div><div>One interesting idea I've come up with is that,</div><div><br></div><div>1. specifying "org.webkit.ImageDecoder"</div><div>2. In Linux, we just use "ImageDecoder" part.</div></span><div>3. In macOS port, we automatically convert it to "WebKit: Image Decoder”</div></div></div></div></div></blockquote><div><br></div><div><div>Why do we specify “org.webkit.ImageDecoder” if only the “ImageDecoder” part is ever going to be used?</div></div><div>Is that because Windows could use “org.webkit.”?</div><div><br></div></div></div></blockquote><div><br></div><div>Yup, we can drop this part. Originally, I was considering about "<span style="font-size:12.8px">com.apple.IPC.ReceiveQueue" in WebKit2 thread => "Apple WebKit: xxx".</span></div><div><span style="font-size:12.8px">But I think just using "WebKit: " is OK.</span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><div></div><div>Again, back to Darin’s point, I don’t see any particular value in ever seeing “org.webkit.”</div><div><br></div><div>Additionally, the way this proposal treats “ImageDecoder” as multiple words, presumably separated on case-change, is problematic.</div><div><br></div><div>e.g. “IndexedDatabaseServer” would expand to “Indexed Database Server”, different from today.</div><div>e.g. “IndexedDBServer”, which is probably what this should be called, would expand to “Indexed D B Server"</div><div>e.g. “GCController” would expand to “G C Controller”</div></div></div></blockquote><div><br></div><div>If we recognize the [UpperCharacter]*[LowerCharacter]* as word, we can split it as "GC Controller".</div><div>But anyway, it causes a problem when we encounter a name like "XMLDBController".</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><div><br></div><div>—</div><div><br></div><div>Taking your proposal and running with it, I think we could do this:</div><div><br></div><div>1 - Specify the feature name with spaces: “Asynchronous Disassembler”</div><div><br></div><div><div>2 - On Linux, it gets collapsed and truncated to 15: “AsynchronousDis”</div><div>2a - It could get truncated with ellipses: “AsynchronousDi…" </div></div></div></div></blockquote><div><br></div><div>I think we should not truncate the name for Linux.</div><div>My automatic shortening is based on the fact that "<a href="http://org.webkit.MODULE.NAME">org.webkit.MODULE.NAME</a>"'s NAME part is always <= 15 characters. So we do not truncate.<br></div><div><br></div><div>But if we have names like "Asynchronous Indexed Database Server" and "Asynchronous Indexed Database Client", the both become "AsynchronousIndex" in Linux.</div><div>It is not helpful.</div><div><br></div><div>However always using 15 characters names effectively limits the ability of macOS's thread names.</div><div><br></div><div>So now, I like Geoff's idea, having 2 names, long name and short name.</div><div>For example, we have "Asynchronous Disassembler" and "AsyncDisasm".</div><div>Then, in macOS, use "WebKit: Asynchronous Disassembler".</div><div>In Windows, use "WebKit: AsyncDisasm".</div><div>In Linux, use "AsyncDisasm".</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><div><div><div><br></div><div>3 - On Windows, it gets “WebKit: “ added and is truncated to 30: “WebKit: Asynchronous Disassemb”</div></div><div>3a - It could get truncated with ellipses: “WebKit: Asynchronous Disassem…”</div><div><br></div><div>4 - On macOS/iOS, it gets “WebKit: “ added: “WebKit: Asynchronous Disassembler"</div></div><div><br></div><div>Addendum: If we see value in having somethings flagged as “JSC” instead of “WebKit”, we just augment the input to include that.</div><div>The above could be “JSC.Asynchronous Disassembler”, and a WebKit specific feature could be “WebKit. IndexedDB Server”</div></div></div></blockquote><div><br></div><div>Yeah, we can add JSC prefix in long name part if we want.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><div><br></div><div>Thanks,</div>~Brady</div></div></blockquote></div><br></div></div>