leobalter

test262-harness --hostPath=`which d8` --hostType=d8 --hostArgs='--harmony_regexp_property' $(git diff --cached tc39/master --diff-filter=AM --name-only test/) -t 4

test262-harness --hostPath=`which d8` --hostType=d8 $(git diff --name-only)

test262-harness $(git grep --name-only --extended-regexp 'verify(Not)?Enumerable' test/) # uses node by default

test262-harness --hostPath=`which d8` --hostType=d8 $(git diff --cached --name-only) # added files only

time test262-harness --hostType=jsshell -t 4 --hostPath=`which js` $(git grep --name-only -E 'features\: \[*+object-(rest|spread)' test/language)

caiolima

First you need to build JSC. Since it is a module in WebKit, you can follow these instructions to get the code and learn how to build it.

https://webkit.org/getting-started/#building-webkit

After the machine setup, you can build JSC as a stand-alone CLI program running

```<path_to_webkit>/Tools/Scripts/build-jsc —release```

It will build jsc into ```<path_to_webkit>/WebKitBuild/Release```

mikeal

Children are created, raised, cared for and we hope that they will live a long and proud life only to end long after their creator's has ended. They are their creator's legacy.

Your code is not your child, it is an animal raised for slaughter. Your code will die. It will die before your death. Your code's entire purpose is to die. Your code enables some new function and if successful that new function will grow, it will mature, it will eventually outlive the usefullness you've provided. When successful your code creates value that outlives it and the faster the better. When unsuccessful a mercy killing is most appropriate.

Believing that our code is our children makes us territorial, protective. Nobody is allowed to kill it, only improve it. The idea that our code can be perfect, that it can change to handle so many new concerns leads to the birth of frameworks and plugin systems. These systems brutalize creativity by forcing new value to conform to the standards of our aging children.

davidsonfellipe

#CSS FTW My way to face the challenge: Maintainable + Efficient + Optimized

##General

• YSlow + Page Speed (Performance Rules)…
• CSSLint Rules…
• Don’t use too many web fonts talk to your designer, and explain the impact of loading many sources.

##Tools

rwaldron

(function( exports ) {

  function EventEmitter() {}

  EventEmitter.prototype.emit = function() {
    var type, handlers, args, listeners;

    type = arguments[0];
    args = [].slice.call( arguments, 1 );

rwaldron

<pre>
# Just Markdown, Yo.

So, I wanted to try to write the simplest webpage possible, [Max Ogden][1]
style. If you have JavaScript, you get something pretty. If not, then you see
[Markdown][2] text, which is fine too.

[1]: http://maxogden.com
[2]: http://daringfireball.net/projects/markdown/
</pre>

porcelli

Intro

Vou iniciar este post com uma breve visão do que EU entendo sobre os principais XDD para em seguida discutir o motivo pelo qual não os acho relevante. Gostaria também de ressaltar que posso SIM ter uma visão limitada ou equivocada destes XDD’s, porém não vamos minimizar esta discussão com argumentos simplórios como “falta de conhecimento”, “falta de prática” ou coisas do gênero... pois o que será discutido aqui é um pouco mais conceitual e filosófico do que as técnicas/processos em si.

Com isso dito, vamos lá:

TDD (Test-driven development)

Esta técnica (ou processo) que visa obter uma maior qualidade na arquitetura/código, pois guindo o desenvolvimento por testes além de se ter um resultado mais assertivo, você também obtém uma arquitetura desacoplada. Geralmente se aplica este processo (NovoTeste->Falha->Implantação->Sucesso->NovoTeste...) em pequenos ciclos.

Meu ponto de vista:

hltbra

Slides usados na SCTI 2011:

http://www.slideshare.net/hugobr/quero-serprogramadorcomofas


Eu separei alguns links que eu acho interessante pra quem estava na palestra.
Alguns estão nas referências dos slides, outros não:


* Teach Yourself Programming in Ten Years

RamonPage

function supports_input_placeholder() {
  var input = document.createElement('input');
  return 'placeholder' in input;
}

dukex

String.prototype.reverse = function(){	
  return this.split("").reverse().join("");
}