Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2470BDD6B for ; Mon, 22 Oct 2012 14:29:21 +0000 (UTC) Received: (qmail 46396 invoked by uid 500); 22 Oct 2012 14:29:20 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 46366 invoked by uid 500); 22 Oct 2012 14:29:20 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 46341 invoked by uid 99); 22 Oct 2012 14:29:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 14:29:19 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of braden@google.com designates 209.85.223.175 as permitted sender) Received: from [209.85.223.175] (HELO mail-ie0-f175.google.com) (209.85.223.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 14:29:15 +0000 Received: by mail-ie0-f175.google.com with SMTP id c13so3590778ieb.6 for ; Mon, 22 Oct 2012 07:28:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :x-system-of-record; bh=XYUiHUreTYuU5ERycf0ia8oU832LBFyTP7icMOMZ2jQ=; b=DDXRTqNjVE5AJs2zyZ1nwzXwwI1EK3Pwbxg2rZeVpcmwltooEwf+eroAY2ISygICpj VnWpNxFXc9rKj8kIf+ROs3S2RfI9iHD/15sY2pMqGhfdYA/b/BXzQNss/0u4MTy0eZvI U4IoaumlsQFcNwSB4pr5oANEZWtjOXWcb/KXm1aSE+JnRYRjQ8No6mV+w6oGPeoPH6Ct Oj5QICW2phYjcafpgi593jf65eRs6J750GX9rtJEjvueWYY3aJbyx0BR1oS3pFbmwy/q fIiOv+f0ZKCszfcHhP7+jQYv5u36XvPo44/lmtKSRFEarN5DpILZx2CrGM+7TQBxK4gN t09g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :x-system-of-record:x-gm-message-state; bh=XYUiHUreTYuU5ERycf0ia8oU832LBFyTP7icMOMZ2jQ=; b=JomC2zw34kNoJdX4NIq3G1fEVrNiyVTUgo14u5dCaTOOoNK+wZnk8QqFM4YXuM+h95 tdLyoiat4oWW2THnGN5K2nqPCQvMH9bNDVIhDaVyunZ0hKs71JXr67UT4a2bV59bPOYu LpMTROsQ0TlUcDEM8FLLgKoC40h5gkRmQrHmiLhfnhJIx8UN+J6a6cC5oaLaISZl+vKl jPTzOzGTxybBCYGlP1ba+JdRIz+DdkS+KgrG/oPuaxaD/l34i3vNOrjY4Wp6MUMAgdd8 9VquXaUjG+kLGkdGm8NeqGhySDyC12lTlx8FXuqxHJ6ubg0ZAODnu2Gr5YEwKk9f1rYX 40cQ== MIME-Version: 1.0 Received: by 10.50.213.73 with SMTP id nq9mr16679388igc.27.1350916135576; Mon, 22 Oct 2012 07:28:55 -0700 (PDT) Sender: braden@google.com Received: by 10.231.221.2 with HTTP; Mon, 22 Oct 2012 07:28:55 -0700 (PDT) In-Reply-To: References: Date: Mon, 22 Oct 2012 10:28:55 -0400 X-Google-Sender-Auth: UPZ2MIPWGCfKZD18ln2CueT41yc Message-ID: Subject: Re: sweet.js and TypeScript From: Braden Shepherdson To: callback-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae93405f361e35b04cca6acba X-System-Of-Record: true X-Gm-Message-State: ALoCoQlEHFWeaa2P3fpiF5zHlJySrMvwoBiJLnyoQ1e8uAt+dLB2XqEy/gNukTVwZAf+Os+cl9uGqbgt1NAsnWsFvBXPDuQeJh0fykZmZJ6x5ym2C6WDx8zkytG7M/aeu5aK6EurMj2uDL7daVucunR2pxew3mz6paIMAkE3M7Dr/R9/fD4LKE/oOC9KCCDJBjG7MOjh3V6LxhEh7PhyzB0INfnpY9Kbng== X-Virus-Checked: Checked by ClamAV on apache.org --14dae93405f361e35b04cca6acba Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable >From my indirect knowledge of TypeScript, I think one of its major points is that it's a strict superset of JS. That means that normal JS is valid TypeScript, so it can be used with other libraries and tools that are plain JS. On Mon, Oct 22, 2012 at 10:05 AM, Andrew Grieve wrote= : > Sounds like a fun discussion :) > > There are two things about sweet.js that make me iffy about it: > 1. Looks like it might make our code look not like JS, and contributors > would need to learn a new language to figure out what's going on > 2. It might make it easier to write bloated code > > I think if we really wanted something like sweet.js, something like > Traceur >might > be a better place to start. > > I'm well accustomed to writing typed JS from my past experience with > Closure Compiler. I haven't looked enough at TypeScript yet to know which > tool might give better type checking, but if people are interested in typ= e > checking, it'd be worth considering Closure Compiler as well. > > > > On Mon, Oct 22, 2012 at 8:14 AM, Patrick Mueller > wrote: > > > There was some chit-chat on Twitter this weekend about using the sweet.= js > > [1] macro processor in Cordova. Somehow. Not quite sure how. Also, a > - I > > believe trolling - mention of using TypeScript [2]. Somehow. > > > > I'd be interested in hearing more about either. > > > > w/r/t TypeScript - note that Isaac Schlueter has mentioned using > TypeScript > > with node.js [3]: > > > > "It=92d be a great idea to write up a TypeScript header file > > for the API surface in Node. Then, we could automatically > > test for API deviations, validate and flesh out our > > documentation, etc. Static typing does confer some very > > relevant value." > > > > I spent a frustrating couple of hours writing code with TypeScript - > didn't > > come away impressed; but as an interface definition language - maybe. N= ot > > sure what the reflective capabilities are there in terms of the output > tho. > > > > [1] http://sweetjs.org/ > > [2] http://www.typescriptlang.org/ > > [3] http://blog.izs.me/post/32697104162/thoughts-on-typescript > > > > -- > > Patrick Mueller > > http://muellerware.org > > > --14dae93405f361e35b04cca6acba--