<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); 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; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Saagar Jha</div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Aug 30, 2017, at 16:42, Robert Bennett via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class=""></div><div class="">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 class=""><br class=""></div><div class="">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 class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>It’ll show up as #imageLiteral([file name here]). Xcode will detect these automatically and fill it in with an image.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class="">On Aug 30, 2017, at 6:49 PM, Ryan Walklin via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div data-html-editor-font-wrapper="true" style="font-family: arial, sans-serif; font-size: 13px;" class="">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 class=""><br class="">Ryan<br class=""><br class="">August 31, 2017 8:40 AM, "John Pratt via swift-evolution" <<a target="_blank" tabindex="-1" href="mailto:%22John%20Pratt%20via%20swift-evolution%22%20<swift-evolution@swift.org>" class="">swift-evolution@swift.org</a>> wrote:<br class=""> <blockquote class=""><div class=""><div style="word-wrap: break-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space" class=""> <div class="">Well, here is one question: 100 years from now do you think all computers</div> <div class="">should use vi?</div> <div class=""></div> <div class="">At what point would people ever have anything that ever slightly resembles</div> <div class="">something advanced?</div> <div class=""></div> <div class="">Do you ever want anything that</div> <div class="">slightly resembles science fiction, ever, in society? Or should everyone be</div> <div class="">using vi for the rest of civilization?</div> <div class=""></div> <div class=""> <blockquote type="cite" class=""> <div class="">On Aug 30, 2017, at 5:32 PM, Eagle Offshore <<a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" href="mailto:eagleoffshore@me.com" class="">eagleoffshore@me.com</a>> wrote:</div> <div class=""><div style="word-wrap: break-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space" class="">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 class=""></div> <div class="">Just my $0.02</div> <div class=""> <div class=""><div class=""><blockquote type="cite" class=""> <div class="">On Aug 28, 2017, at 7:57 PM, John Pratt via swift-evolution <<a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div> <div class=""> <div style="word-wrap: break-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space" class="">I sent a postal envelope to the Swift team with an article I wrote, arguing that<div class="">symbols and graphics would push the programming language forward.</div> <div class=""></div> <div class="">Wouldn’t it be nice to have an actual multiplication matrix broken out into code,</div> <div class="">instead of typing, “matrix()”? It seems to me Swift has the chance to do that.</div> <div class=""></div> <div class="">Also: why does "<==" still reside in code as "less than or equal to” when</div> <div class="">there is a unicode equivalent that looks neat?</div> <div class=""></div> <div class="">Why can’t the square of x have a superscript of 2 instead of having “pow(x,2)?</div> <div class="">I think this would make programming much easier to deal with.</div> <div class=""></div> <div class="">I expound on this issue in my article:</div> <div class=""></div> <div class=""><a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" style="" href="http://www.noctivagous.com/nct_graphics_symbols_prglngs_draft2-3-12.pdf" class="">http://www.noctivagous.com/nct_graphics_symbols_prglngs_draft2-3-12.pdf</a></div> <div class=""></div> <div class="">Thank you for reading.</div> <div class=""></div> <div class=""></div> <div class="">-John</div> </div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a> </div> </blockquote></div></div> </div> </div></div> </blockquote> </div> </div></div></blockquote> <signature class=""></signature><br class=""> </div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></blockquote></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>