DiegoJeptha

/**
 * CodeMirror NPM dynamic language module loader.
 * To be used with WebPack.
 *
 * @example
 * loadCodeMirrorModule(codeMirrorLanguages.JavaScript.codeMirrorMode)
 *
 * @author rigwild <https://github.com/rigwild>
 * @see https://gist.github.com/rigwild/ce6b4c6a893c3a95f75cc0aca633f037
 * @license MIT

alekseykulikov

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

• SUIT CSS naming conventions + SUIT CSS design principles;
• PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
• Flexbox is awesome. No need for grid framework;
• Normalize.css, base styles and variables are solid foundation for all components;

paulirish

What forces layout / reflow

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.

Element APIs

Getting box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

awangenh

/* ============================================================================= *
 *      COMPUTE AND DRAW A BICUBIC SURFACE PATCH USING FORWARD DIFFERENCES       *
 *                                                                               *
 * This code implements and provides corrections to the algorithm named          *
 * DrawSurfaceFwdDif presented in Fig.11.46 at page 525 of the book              *
 * Computer Graphics - Principles and Practice 2.ed in C by Jamed D.Foley et.al. *
 * This algorithm was neither corrected nor repeated in the 3rd (present)        *
 * edition of Foley et.al.'s book.                                               *
 *                                                                               *
 * The algorithm, as stated in the book, does not work: There is one error and   *

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

tonussi

{
    tonussi = {
        "first": "Lucas",
        "last": "Tonussi",
        "age": 23,
        "sex": "M",
        "registered": false,
        "class": "Mage", // se achou o gandalf
        "interests": [ "Reading", "Mountain Biking", "Hacking" ],
        "phrases": ["vamo ae", "da pra fazer miséria"],

julianshen

/*
 * Copyright 2014 Julian Shen
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software

filipw

using System;
using System.Linq.Expressions;
using System.Reflection;
using WebApi.Delta;

namespace Hst.Deals.API.Infrastructure
{
    internal class CompiledPropertyAccessor<TEntityType> : PropertyAccessor<TEntityType> where TEntityType : class
    {
        private Action<TEntityType, object> _setter;