incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: sweet.js and TypeScript
Date Mon, 22 Oct 2012 18:32:12 GMT
If it's for making ES6 features work with older JS engines, then I'm for
it. The first example on sweetjs.org is for making JS look like python
though.

Are you saying you want to use syntax like
http://wiki.ecmascript.org/doku.php?id=harmony:modules_examples

and then sweetjs can be used in the compiling step?




On Mon, Oct 22, 2012 at 10:31 AM, Gord Tanner <gord@tinyhippos.com> wrote:

> Just a friendly nudge away from typescript ;)  Sweet.js has nothing to do
> with typescript.
>
> The idea is more for using macro's to add new and upcoming syntax support
> to our javascript layer.
>
> On Mon, Oct 22, 2012 at 10:28 AM, Braden Shepherdson <braden@chromium.org
> >wrote:
>
> > 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 <agrieve@chromium.org
> > >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<
> http://code.google.com/p/traceur-compiler/wiki/LanguageFeatures
> > > >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
> > type
> > > checking, it'd be worth considering Closure Compiler as well.
> > >
> > >
> > >
> > > On Mon, Oct 22, 2012 at 8:14 AM, Patrick Mueller <pmuellr@gmail.com>
> > > 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’d 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.
> > Not
> > > > 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
> > > >
> > >
> >
>
>
>
> --
> Gord Tanner
> Senior Developer / Code Poet
> tinyHippos Inc.
> @tinyhippos
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message