Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Mark H Harris <harrismh777@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: OT: This Swift thing
Date: Tue, 03 Jun 2014 16:00:03 -0500
Organization: Aioe.org NNTP Server
Lines: 19
Message-ID: <lmld0f$v2b$1@speranza.aioe.org>
References: <34564700423508781.788278sturla.molden-gmail.com@news.gmane.org> <mailman.10639.1401819979.18130.python-list@python.org>
NNTP-Posting-Host: eSF12mcVRIwL+eMIMJ03mA.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.python:72548

On 6/3/14 1:26 PM, Skip Montanaro wrote:
>>From Apple's perspective, there's always platform lock-in. That's good
> for them, so it must be good for you, right? :-)
>

http://www.theregister.co.uk/2014/06/02/apple_aims_to_speed_up_secure_coding_with_swift_programming_language/

The key to this "Swift thing" is the same for the "Julia thing"... LLVM.

Swift is getting huge performance boost from LLVM, not to mention that 
its not bloated, nor is it designed by committee. ehem.

This has less to due with lock-in per se, and more to do with quality 
control and consistency. OTOH, it has A LOT to due with reinventing the 
wheel. I love it. Every time a product comes out like Julia, or Swift, 
the committee needs to take notice, and perhaps adapt.

marcus