Pascal Maniraho murindwaz

Why I hate TypeScript

Warning: These views are highly oppinated and might have some slightly incorrect facts. My experience with typescript was about 2 weeks in Node and a week in angular2.

Not Standard

TypeScript is implementing their own take on JavaScript. Some of the things they are writing will likely never make it in an official ES* spec either.

Technologies that have competing spec / community driven development have a history of failing; take: Flash, SilverLight, CoffeeScript, the list goes on. If you have a large code base, picking TypeScript is something your going to be living with for a long time. I can take a bet in 3 years JavaScript will still be around without a doubt.

Its also worth noting that they have built some things like module system and as soon as the spec came out they ditched it and started using that. Have fun updating!

Full Disclosure: I'm a member of the AVA team

Q: How much faster is AVA than Mocha (tap, tape, ...).

A: It depends.

First things first:

I should start by saying there are lots of reasons to choose AVA, and I don't think speed is (necessarily) the most import one. Other good reasons include:

Creating the post-commit file

Note: If you want to use your personal Twitter account to post commits, go to Step 2

Create a new Twitter account for your commit messages. Example
Go to http://dev.twitter.com and Sign In with your Twitter account you are posting commit messages to.
Hover over your username in the top-right corner after signing in and select "My Applications"
Create a new application
The name, description, and site can all be whatever you want, but leave Callback URL empty
Under "Application Settings" click "modify app permissions" next to "Access level"

I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.

TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).

Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

How-to setup a simple git push deployment

These are my notes basically. At first i created this gist just as a reminder for myself. But feel free to use this for your project as a starting point. If you have questions you can find me on twitter @thomasf https://twitter.com/thomasf This is how i used it on a Debian Wheezy testing (https://www.debian.org/releases/testing/)

Discuss, ask questions, etc. here https://news.ycombinator.com/item?id=7445545

On the server (example.com)

JavaScript Static Analysis Tools

Most people are familiar with these three tools:

[JSHint][1]
[JSLint][2]
[Google Closure Linter][3]

The first one is more popular among developers because it is style-agnostic. The other two enforce rules of [Crockford Style][4] and [Google Code Style][5] respectively.

Deploying a subfolder to GitHub Pages

Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.

For the sake of this example, let’s pretend the subfolder containing your site is named dist.

Step 1

Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).

	/* jshint strict: false */
	/* globals require, console */
	var gulp = require('gulp');
	var exit = require('gulp-exit');

	var browserify = require('browserify');
	var watchify = require('watchify');
	var babelify = require('babelify');

	var source = require('vinyl-source-stream');

	#!/usr/bin/env node

	var program = require('commander');
	var request = require('request');
	var chalk = require('chalk');

	program
	.version('0.0.1')
	.usage('[options] <keywords>')
	.option('-o, --owner [name]', 'Filter by the repositories owner')

	// <input id="my-input-element" type="text" value="foo"/>
	var evt, node = document.getElementById('my-input-element');

	// Have to use dispatchEvent/fireEvent because jQuery.trigger will not
	// fire an event attached via addEventListener. Each environment has an
	// unusual way to trigger a keyup event.
	if (node.dispatchEvent) {
	// Sane browsers
	try {
	// Chrome, Safari, Firefox