{ | |
"api:statuscode":0, | |
"api:duration":"0.004s", | |
"api:message":"OK", | |
"communityList":[ | |
{ | |
"status":0, | |
"endpoint":"star-vs-as-forcas-do-mal-pt-br", | |
"name":"Star Vs As For\u00e7as Do Mal PT/BR", | |
"modifiedTime":"2016-11-01T01:04:54Z", |
/src/parser/spider_monkey_ast.ml
: The type definitions for the AST. Tries to stay very close to ESTree/src/parser/lexer_flow.mll
: The ocamllex lexer logic/src/parser/parser_flow.ml
: The recursive descent JS parser
/src/typing/type_inference_js.ml
: Contains the "entry point" for inference (Function calledinfer_ast
)./src/typing/statement.ml
: Most of the inference logic (runs through the AST and generates the initial constraints)
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
,elem.offsetTop
,elem.offsetWidth
,elem.offsetHeight
,elem.offsetParent
package controllers; | |
import play.*; | |
import play.mvc.*; | |
public class Application extends JadeController { | |
public static Result index() { | |
return ok(render("index", "message", "Hello world!")); | |
} | |
} |
# -*- encoding : utf-8 -*- | |
set :assets_dependencies, %w(app/assets lib/assets vendor/assets Gemfile.lock config/routes.rb) | |
namespace :deploy do | |
namespace :assets do | |
desc <<-DESC | |
Run the asset precompilation rake task. You can specify the full path \ | |
to the rake executable by setting the rake variable. You can also \ |
Node.js core does its best to treat every platform equally. Even if most Node developers use OS X day to day, some use Windows, and most everyone deploys to Linux or Solaris. So it's important to keep your code portable between platforms, whether you're writing a library or an application.
Predictably, most cross-platform issues come from Windows. Things just work differently there! But if you're careful, and follow some simple best practices, your code can run just as well on Windows systems.
On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation