[swift-users] Swift and Xcode along with Playgrounds is full of bugs

Shyamal Chandra shyamalc at gmail.com
Wed Nov 2 01:27:08 CDT 2016

Hi Jens,

1. I think you have me confused; I am not yelling.  I didn't flame Tim Cook
or Chris Latter.
2. Github would be a great place to use for the extensible documentation.
3. Volunteers are great because they might get jobs from Apple or become
great evangelists for knowing industry-quality code
4. They could sell Venmo or PayPal support and build an ecosystem of
support at lower prices that are super fast with nanopayments (e.g.
Muhammad Yunus).
5. Everyone should be on first name basis with Tim because he is going to
help us in some way with his hands-on and administrative decisions both in
policy and implementation.  Wait, I sent a letter once to Satya Nadella and
he sent me a better grade headset.  Customer engagement should be personal,
not hierarchical.
6. From my limited MSM perspective and Walter Isaacson's book on Steve
Jobs, I cannot comment on the "nail my head to the floor".  This type of
anecdotal way of circumventing the issue might be best addressed with a
phone number.  I included my phone number. :-)
7. My CPU is not being used 100%; even then, why is the app still loading
and not doing on-the-fly compilation (I am unsure what it is doing without
debug mode.)?  Do you use design patterns or concurrency patterns to fully
utilize the number of cores with an adequate number of processes and
threads in the background and foreground.  I wish I had a Mac Pro (I have a
3-year-old iMac) and even if I upgrade, would the performance scale and
speed up?



Shyamal Chandra
shyamalc at gmail.com
Linkedin: http://www.linkedin.com/in/shyamalc
Phone: 620-719-9064

On Wed, Nov 2, 2016 at 1:03 AM, Jens Alfke <jens at mooseyard.com> wrote:

> On Nov 1, 2016, at 9:50 PM, Shyamal Chandra via swift-users <
> swift-users at swift.org> wrote:
> Why don't you make the Playgrounds open source so I can investigate?
> I’ve been hearing people tell Apple “why don’t you make ___ open source”
> for as long as the term ‘open source’ has existed. Sometimes it happens,
> but the decision doesn’t seem to be based on factors like ‘people on the
> Internet are yelling at us to open-source this’, or ‘this feature sucks,
> let’s dump the source code on Github and let volunteers fix it for us for
> free!’
> I’m being sarcastic here, but if you’d ever run an open source project —
> or worse, open-sourced an existing code base — you’d have some idea of the
> complexity of what you’re asking. Open source is a commitment, and it can
> be a ton of work just getting the code ready, especially when it has
> dependencies on private APIs from other components that shouldn’t be
> exposed. Even comments and identifiers need to be scrubbed of references to
> internal/secret/embarrassing information, like “// we’re commenting out
> this feature until the 2017 Mac Pro ships in March”, or “// Workaround to
> make Photoshop compile, no thanks to those morons at Adobe”. (Yes, I went
> through stuff like this in one project in the ‘90s.)
> As for Playgrounds, I’m not aware of Apple open-sourcing GUI-level
> application code. Ever. (Someone correct me if I’ve forgotten something.)
> You should tell this to Tim Cook as soon as possible.
> Because everyone at Apple is on a first-name basis with Tim Cook and feels
> free to drop into his office and tell him what to do. 🙄 Back when I worked
> at Apple I used to drop in on Steve and tell him the metal UI appearance
> sucked. He’d chuckle in his kindly way, and then nail my head to the floor.
> —Jens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20161102/56f94a63/attachment.html>

More information about the swift-users mailing list