<div dir="ltr">Thank you everyone for contributing. I don't mean to talk more on this issue.<div>If anyone at Apple wants to contact me to do things that go beyond typewriter code,</div><div>you are welcome. Otherwise... well I guess you'll be copying Noctivagous later.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 30, 2017 at 8:28 PM, Saagar Jha via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><br><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">Saagar Jha</div>
</div>
<div><span class=""><br><blockquote type="cite"><div>On Aug 30, 2017, at 16:42, Robert Bennett via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br class="m_-2448279786388746887Apple-interchange-newline"><div><div dir="auto"><div></div><div>But countless editors have popped up since vi(m) first appeared. If anything, this is a testament to the fact that old, “crusty” technology can remain relevant forever, even as new technologies offering better ergonomics enter the market.</div><div><br></div><div>Also, could someone tell me how ImageLiteral and similar types are represented in the file? What appears when you open it in TextEdit? This same sort of thing — presumably some ascii delimiters signifying specially formatted data (I don’t have access to a computer) — could enable the desired matrix, sqrt, etc functionality in Xcode. (Unless Xcode is doing preprocessing of those types before compiling.)</div><div><br></div></div></div></blockquote><div><br></div></span><div>It’ll show up as #imageLiteral([file name here]). Xcode will detect these automatically and fill it in with an image.</div><div><div class="h5"><br><blockquote type="cite"><div><div dir="auto"><div>On Aug 30, 2017, at 6:49 PM, Ryan Walklin via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div style="font-family:arial,sans-serif;font-size:13px">I think we've possibly moved beyond the scope of swift-evolution. Skim-reading the OP's manifesto demonstrates nothing relevant to general purpose programming languages or Swift in particular.<br><br>Ryan<br><br>August 31, 2017 8:40 AM, "John Pratt via swift-evolution" <<a href="mailto:%22John%20Pratt%20via%20swift-evolution%22%20%3Cswift-evolution@swift.org%3E" target="_blank">swift-evolution@swift.org</a>> wrote:<br> <blockquote><div><div style="word-wrap:break-word"> <div>Well, here is one question: 100 years from now do you think all computers</div> <div>should use vi?</div> <div></div> <div>At what point would people ever have anything that ever slightly resembles</div> <div>something advanced?</div> <div></div> <div>Do you ever want anything that</div> <div>slightly resembles science fiction, ever, in society? Or should everyone be</div> <div>using vi for the rest of civilization?</div> <div></div> <div> <blockquote type="cite"> <div>On Aug 30, 2017, at 5:32 PM, Eagle Offshore <<a rel="external nofollow noopener noreferrer" href="mailto:eagleoffshore@me.com" target="_blank">eagleoffshore@me.com</a>> wrote:</div> <div><div style="word-wrap:break-word">While I am in theory a fan of literate programming and enjoy integrated programming environments when they are integrated into a complete literate system (Smalltalk browsers, LISP environments, HyperCard, etc...)...In practice if its just a language and not a complete holistic system, and I can't command the entire thing with God's own editor (I speak of vi - because its "there" and it is the only editor guaranteed to be "there" on any system I am ever likely to try to access), I'm not gonna use it.<div></div> <div>Just my $0.02</div> <div> <div><div><blockquote type="cite"> <div>On Aug 28, 2017, at 7:57 PM, John Pratt via swift-evolution <<a rel="external nofollow noopener noreferrer" href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div> <div> <div style="word-wrap:break-word">I sent a postal envelope to the Swift team with an article I wrote, arguing that<div>symbols and graphics would push the programming language forward.</div> <div></div> <div>Wouldn’t it be nice to have an actual multiplication matrix broken out into code,</div> <div>instead of typing, “matrix()”? It seems to me Swift has the chance to do that.</div> <div></div> <div>Also: why does "<==" still reside in code as "less than or equal to” when</div> <div>there is a unicode equivalent that looks neat?</div> <div></div> <div>Why can’t the square of x have a superscript of 2 instead of having “pow(x,2)?</div> <div>I think this would make programming much easier to deal with.</div> <div></div> <div>I expound on this issue in my article:</div> <div></div> <div><a rel="external nofollow noopener noreferrer" href="http://www.noctivagous.com/nct_graphics_symbols_prglngs_draft2-3-12.pdf" target="_blank">http://www.noctivagous.com/<wbr>nct_graphics_symbols_prglngs_<wbr>draft2-3-12.pdf</a></div> <div></div> <div>Thank you for reading.</div> <div></div> <div></div> <div>-John</div> </div>______________________________<wbr>_________________<br>swift-evolution mailing list<br><a rel="external nofollow noopener noreferrer" href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a rel="external nofollow noopener noreferrer" href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a> </div> </blockquote></div></div> </div> </div></div> </blockquote> </div> </div></div></blockquote> <u></u><u></u><br> </div>
</div></blockquote><blockquote type="cite"><div><span>______________________________<wbr>_________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a></span><br></div></blockquote></div>______________________________<wbr>_________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br></div></blockquote></div></div></div><br></div><br>______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br></blockquote></div><br></div>