-
console1984 — Privacy-aware Rails console that records sessions and protects encrypted data. Blog: Privacy-aware Rails consoles
-
audits1984 — Auditing interface for console1984 sessions. Blog: [Privacy-aware Rails
To use media keys on the Ducky One 2 Skyline, you must record a macro to bind the media function to a hotkey combination, i.e. Fn plus some key.
Important: In the instructions below, "Press X+Y+Z" means press and hold key X, press and hold key Y, press and hold key Z in that order, and then release all three.
As an example, to bind Fn+PgUp to the play/pause media function:
| <?php namespace App\Http; | |
| use Illuminate\Foundation\Http\Kernel as HttpKernel; | |
| class Kernel extends HttpKernel | |
| { | |
| protected $middleware = [ | |
| \App\Http\Middleware\NewRelicPatch::class, | |
| //... your other middlewares | |
| ]; |
| function gh --description 'Open the webpage for the current github repo/branch' | |
| set -l fetch_url (command git remote --verbose show -n origin ^/dev/null | command grep Fetch | cut -c 14- ) | |
| #did we get an exit status? | |
| if [ $status -gt 0 ] | |
| echo 'Not a git repo.' | |
| return 1 | |
| end | |
| if [ -z $fetch_url ] |
- end-of-stream - specify a callback to be called when a stream ends (which is surpsingly hard to get right)
- duplexify - compose a Duplex stream from a Readable and a Writable stream
- pump - pipe streams together and close all of them if one of them closes
- pumpify - combine an array of streams into a single duplex stream using pump and duplexify
- through2 - tools for making Transform streams
- from2 - tools for making Readable streams
| 'use strict'; | |
| var React = require('react'); | |
| React.Component.extend = require('extendible'); | |
| var MyComponent = React.Component.extend({ | |
| state: { | |
| what: 'extend' | |
| }, | |
| render: function () { |
Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward discussions repo
- io is a fork of node v0.12 (the next stable version of node.js, currently unreleased)
- io.js will be totally compatible with node.js
- the people who created io.js are node core contributors who have different ideas on how to run the project
- it is not a zero-sum game. many core contributors will help maintain both node.js and io.js
- If you rename a field, then your users are fucked. Convert with a hardcoded array structure.
- Most DB drivers [for PHP] will show integers as numeric strings and
falseas"0", so you want to typecast them. - Unless you're using an ORM with "hidden" functionality, people will see passwords, salts and all sorts of fancy codes. If you add one and forget to put it in your
$hiddenarray then OOPS!
- Use the query string for paired params instead of
/users/id/5/active/true. Your API does not need to be SEO optimised. ?format=xmlis stupid, use anAccept: application/xmlheader. I added this to the CodeIgniter Rest Server once for lazy people, and now people think it's a thing. It's not.
(tl;dr DOM builders like [domo][domo] trump HTML templates on the client.)
Like all web developers, I've used a lot of template engines. Like most, I've also written a few of them, some of which even [fit in a tweet][140].
The first open-source code I ever wrote was also one of the the first template engines for node.js, [a port][node-tmpl] of the mother of all JavaScript template engines, [John Resig][jresig]'s [micro-templates][tmpl]. Of course, these days you can't swing a dead cat without hitting a template engine; one in eight packages on npm ([2,220][npm templates] of 16,226 as of 10/19) involve templates.
John's implementation has since evolved and [lives on in Underscore.js][underscore], which means it's the default choice for templating in Backbone.js. And for a while, it's all I would ever use when building a client-side app.
But I can't really see the value in client-side HTML templates anymore.
