- version 3.6
Check those constraints:
$this->anything()
| #!/bin/sh | |
| echo "What should the Application be called (no spaces allowed e.g. GCal)?" | |
| read inputline | |
| name="$inputline" | |
| echo "What is the url (e.g. https://www.google.com/calendar/render)?" | |
| read inputline | |
| url="$inputline" |
| eXtreme Go Horse (XGH) Process | |
| Quelle: http://gohorseprocess.wordpress.com | |
| Übersetzung ursprünglich von https://gist.github.com/Neffez/f8d907ba8289f14e23f3855011fa4e2f | |
| 1. Ich denke, also ist es nicht XGH. | |
| In XGH wird nicht gedacht, es wird das erste gemacht, was in den Sinn kommt. Es gibt auch keine zweite Option, die erste ist schneller. | |
| 2. Es gibt 3 Wege ein Problem zu lösen: den richtigen Weg, den falschen Weg und den XGH Weg, welcher exakt wie der falsche ist, aber schneller. |
| from random import randint | |
| #----Step 1 | |
| # First, choose two random primes. | |
| # In real world, they should be really big primes (hundreds of digits). | |
| p, q = 41, 47 | |
| #----Step 2 | |
| # From them we have n=p*q and phi(n)=(p-1)*(q-1). |
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:
This is an adjusted version of EC2 CloudWatch stats for Dashing which is not bound to EC2 metrics but a generic widget for cloudwatch graphs. Visualization is done by Rickshawgraph as in the original example.
A while ago I did some rage tweeting about job ads. Here is a list of helpful things people sent me to read then and since:
"How do I get started with Node?" is a commonly heard question in #Node.js. This gist is an attempt to compile some of the answers to that question. It's a perpetual work-in-progress.
And if this list didn't quite answer your questions, I'm available for tutoring and code review! A donation is also welcome :)
Before you get started learning about JavaScript and Node.js, there's one very important article you need to read: Teach Yourself Programming in Ten Years.
Understand that it's going to take time to learn Node.js, just like it would take time to learn any other specialized topic - and that you're not going to learn effectively just by reading things, or following tutorials or courses. _Get out there and build things!
| 'use strict'; | |
| /** | |
| * Created by Milan Karunarathne | |
| * Email: [email protected] | |
| * May be freely distributed under the MIT license | |
| */ | |
| import EventEmitter from 'events'; | |
| class Single extends EventEmitter { |
| Page explaining this regex: http://danieloaks.net/irc-regex/ | |
| Raw regex: | |
| ^(?:@([^\r\n ]*) +|())(?::([^\r\n ]+) +|())([^\r\n ]+)(?: +([^:\r\n ]+[^\r\n ]*(?: +[^:\r\n ]+[^\r\n ]*)*)|())?(?: +:([^\r\n]*)| +())?[\r\n]*$ | |
| Sample IRC messages: | |
| foo bar baz asdf |