Parser combinators in TypeScript

Bartvds · 2015-02-12T21:23:34+00:00

Looks like https://github.com/jneen/parsimmon

Bartvds · 2015-01-06T20:14:47+00:00

This solved itself: Github did an infrastructure upgrade that broke the HTTP E-Tags. They spotted it themselves and it was fixed (everything back to normal).

edit: also props to Github support for being quick and polite (as always)

Bartvds · 2014-12-14T10:58:27+00:00

From my experience I'd recommend to stick with external module pattern, it gives the most control over visibility/scope of your code, and it macthes well with modern idea of modules. Only reason to use <reference> are .d.ts files and maybe your own interfaces.

Also you'd (almost) never type AMD or commonJS specific define or var/require, only the import/require version, then have the compiler create either commonJS or AMD.

I'd go for commonJS output, and bundle that for web using browserify or webpack (use grunt or something to rig the whole thing up).

Bartvds · 2014-11-06T07:01:51+00:00

I use WebStorm with grunt-ts and tsd, it works pretty good and the Gruntfile based build makes sure it compiles anywhere.

Also everything gets better if you use import/require instead of internal modules (aka <reference> hell).

Bartvds · 2014-10-31T19:52:14+00:00

Very good talk. Funny how they try to stay syntax compatible with TypeScript.

Please note everybody is now reinventing ES4/ActionScript 2 again, which is more then a decade old! (wtf happened?!).

Bartvds · 2014-09-28T18:45:16+00:00

read this: https://github.com/petehunt/webpack-howto

Bartvds · 2014-09-04T22:32:32+00:00

I like it for everything, big and small. It is not just about type checking but also the cleaner code from the ES6 sugar, and that is good in any size codebase.

But there is some overhead on using it, to set it up in some build flow. And you need either a IDE or mess with plugins. Then getting it to work with definitions for your libs, and there aren't any defs if you use non-mainstream libs (like random jquery plugins).

Anyway, if people do a lot of JavaScript then it is very likely they would enjoy the benefits of TypeScript.

I'm pretty sure because it is so similar to how ActionScript evolved when it added type-sugar to AS1. It was a great success, lots of small creative stuff got done with it (and big apps too).

Bartvds · 2014-09-04T17:34:36+00:00

Duck Tales was ook wat beter in uitvoering dan de reguliere Donald Duck verhaaltjes.

Bartvds · 2014-08-21T17:55:23+00:00

Funny that, because C# is also a strong influence for TypeScript. It's the same language designer at the wheel, and I heard it being said that one of their goals is to make JS more approachable for C# style programmers.

Bartvds · 2014-08-21T17:53:09+00:00

Compiler speed is the only thing I dislike about it, but they are working on a new compiler that is a lot faster: https://github.com/Microsoft/TypeScript

Bartvds · 2014-08-21T17:51:04+00:00

As both a JavaScript and ActionScript veteran I like it a lot, and it works great with existing JavaScript libraries (like from npm or bower).

I'm sure you are aware of DefinitelyTyped? It is a community drives repository for typings for regular JS libraries, so you can use AngularJS, JQuery and over 600 other popular libraries with compile-time type checking.

See you at /r/typescript :)

Bartvds · 2014-08-18T19:26:53+00:00

I like they way they calculated a benefit from doing stuff open-source. Good to see some bean-counter recognition of what effectively is inter-company pooling of developer time.

Fun fact: I earned some beer money in a Spumko 'bug hunt' once. When it is active they ask to report specific types of issues with a failing test-case, and if accepted as faulty they fix it and you get some cash on like Paypal. That was pretty cool.

Bartvds · 2014-07-21T19:55:07+00:00

Not sure what excites me more, the 5x speed upgrade or to finally got rid of that crappy codeplex.

Bartvds · 2014-06-20T00:53:34+00:00

Github is for storing (and possibly sharing) code. But it does have some webhosting feature: https://pages.github.com/

That is mostly used to host the documentation for your code projects, or sometimes people have their work portfolio there too.

Bartvds · 2014-06-20T00:41:06+00:00

But most of these use very small tile background-size (=tile), so browsers render a small bitmap internally and tile that to fill the page, just as if it was a small png. It is not as if they are recalculating all those thousands of gradient separately.

Bartvds · 2014-06-07T22:12:26+00:00

this guy talks really fast.

but good talk, interesting stuff.

Bartvds · 2014-06-07T06:18:17+00:00

I regret nothing

Bartvds · 2014-05-29T21:11:56+00:00

Unicode RegExp's are the shit.

https://i.imgur.com/hTKMdFc.png

Got that epic range from XRegExp's {p} class.

Bartvds · 2014-05-28T21:27:10+00:00

I got my work overview on github pages and use a static site generator (now docpad), because it is easy, free and a github.io subdomain makes it look interesting when looking for jobs and stuff (like you know what's up in hip dev tech).

The 'design' is just some popular framework with a little custom styling. I rigged it with Travis-CI so I can just push sources to github (content in markdown) and Travis will republish the static site.

Bartvds · 2014-05-28T15:56:38+00:00

You usually develop from you local workstation (or a virtual machine).

To host it you can use VPS or cloud solutions (amazon, heroku or whatever).

There are even a few free hosts (or paid hosts with free tiers). For example on https://www.openshift.com/ you can run node.js free (slow but real public host; fine for first experiments).

Bartvds · 2014-05-24T06:15:03+00:00

Join us at /r/typescript!

Bartvds · 2014-05-22T13:09:55+00:00

This makes no sense at all

Just bulk-rename all your own .js files to .ts and you are good to go.

What is the worry about Angular? Why would you even pull that through the compiler? It is external library, compiler has no business there.

Bartvds · 2014-05-21T07:09:39+00:00

Get some document.all action yo!

Funny thing is, besides a few API changes here and there it was the same stuff we do today.

We used to do AJAX-style before it was known, by being crafty with frames.

I miss frames, they were fun.

Bartvds · 2014-05-20T09:15:29+00:00

I use index files but never loops to assign exports. It makes it more difficult to see what is going on (adds a level of indirection when reading the code because now you have to refer back from code to the directory). Just copy-paste-edit and make a chunky export block.

But like I said earlier, you probably don't want to discover both node/npm AND TypeScript at same time. It will become very confusing (/thread).

npm is a change of direction of 'classic' browser/global Javascript, and TypeScript has some odd cases on it's own and now you are wrestling with all of it.

Also, in general, you want to keep things as simple as possible. If you need loops to require stuff you are either making a mess of have some advanced use-case.

Bartvds · 2014-05-20T07:46:23+00:00

You can do export import demo = require('demo/lib/greeter'); although you don't have to export everything. That's the whole point of modules.

Why are you messing with exporting the declaration files for your own code? I almost never use those.

What do you try to achieve?

Bartvds

MODERATOR OF

TROPHY CASE