[swift-evolution] Beyond Typewriter-Styled Code in Swift, Adoption of Symbols

[Robert Bennett]

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.

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.)

> On Aug 30, 2017, at 6:49 PM, Ryan Walklin via swift-evolution <swift-evolution at swift.org> wrote:
> 
> 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.
> 
> Ryan
> 
> August 31, 2017 8:40 AM, "John Pratt via swift-evolution" <swift-evolution at swift.org> wrote:
> Well, here is one question: 100 years from now do you think all computers
> should use vi?
> At what point would people ever have anything that ever slightly resembles
> something advanced?
> Do you ever want anything that
> slightly resembles science fiction, ever, in society? Or should everyone be
> using vi for the rest of civilization?
>> On Aug 30, 2017, at 5:32 PM, Eagle Offshore <eagleoffshore at me.com> wrote:
>> 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.
>> Just my $0.02
>>> On Aug 28, 2017, at 7:57 PM, John Pratt via swift-evolution <swift-evolution at swift.org> wrote:
>>> I sent a postal envelope to the Swift team with an article I wrote, arguing that
>>> symbols and graphics would push the programming language forward.
>>> Wouldn’t it be nice to have an actual multiplication matrix broken out into code,
>>> instead of typing, “matrix()”? It seems to me Swift has the chance to do that.
>>> Also: why does "<==" still reside in code as "less than or equal to” when
>>> there is a unicode equivalent that looks neat?
>>> Why can’t the square of x have a superscript of 2 instead of having “pow(x,2)?
>>> I think this would make programming much easier to deal with.
>>> I expound on this issue in my article:
>>> http://www.noctivagous.com/nct_graphics_symbols_prglngs_draft2-3-12.pdf
>>> Thank you for reading.
>>> -John
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170830/d254542c/attachment.html>