From | To | Expression |
---|
/**********************************************/ | |
/* | |
/* IR_Dark_Monokai | |
/* Designed and developed by Andres Pagella (@mapagella) | |
/* http://www.andrespagella.com/customising-chrome-devtools | |
/* | |
/* Based on Ben Truyman's IR_Black | |
/* which is... | |
/* Based on Todd Werth's IR_Black: | |
/* http://blog.toddwerth.com/entries/2 |
Authored by Peter Rybin , Chrome DevTools team
In this short guide we'll review some new Chrome DevTools features for "function scope" and "internal properties" by exploring some base JavaScript language concepts.
Let's start with closures β one of the most famous things in JS. A closure is a function, that uses variables from outside. See an example:
# Unofficial brew formula for proxychains 4 | |
# Instruction: | |
# $ git clone https://gist.github.com/gvlx/5441972 gist-5441972 | |
# $ brew install --HEAD gist-5441972/proxychains_formula.rb | |
# | |
# The default config file will be located in /usr/local/etc/proxychains.conf | |
# | |
require 'formula' | |
class ProxychainsFormula < Formula |
I've had a love/hate relationship with Java and in turn the JVM. I love to hate them both. Begrudgingly, I can acknowledge the performance and maturity of the JVM, especially when compared with the simplistic Ruby VM (MRI). Historically, Lookout has been a very Ruby-oriented company, I would estimate that 80%+ of our server-side code is Ruby-based (including Chef). It's tremendously easy to build Ruby projects at Lookout, but the deployment process, production performance leaves something to be desired.
People
![]() :bowtie: |
π :smile: |
π :laughing: |
---|---|---|
π :blush: |
π :smiley: |
:relaxed: |
π :smirk: |
π :heart_eyes: |
π :kissing_heart: |
π :kissing_closed_eyes: |
π³ :flushed: |
π :relieved: |
π :satisfied: |
π :grin: |
π :wink: |
π :stuck_out_tongue_winking_eye: |
π :stuck_out_tongue_closed_eyes: |
π :grinning: |
π :kissing: |
π :kissing_smiling_eyes: |
π :stuck_out_tongue: |
<NotepadPlus> | |
<UserLang name="Groovy" ext="groovy" udlVersion="2.1"> | |
<Settings> | |
<Global caseIgnored="no" /> | |
<Prefix Keywords1="no" Keywords2="no" Keywords3="no" Keywords4="no" /> | |
</Settings> | |
<KeywordLists> | |
<Keywords name="Comments">03/* 04*/ 00// 01 02</Keywords> | |
<Keywords name="Keywords1">abstract break case catch continue default do else extends final finally for if implements instanceof native new private protected public return static switch synchronized throw throws transient try volatile while strictfp package import false null super this true</Keywords> | |
<Keywords name="Keywords2">as assert def mixin property test using in it</Keywords> |
I needed a syslog server and had been reading about ELK for the past few months. I finally decided to throw together a basic implementation in my home lab. I've recorded my notes for this process in this document & dumped the notes online at the following locations:
The implementation I built is super basic, it's just in my lab for dev purposes atm - so I didn't finish securing or building the integrations - just needed it to visualize some syslog data ATM.
javascript:void((function(d){h=d.createElement('script');h.src='//cdnjs.cloudflare.com/ajax/libs/html-inspector/0.8.1/html-inspector.js';d.body.appendChild(h);})(document)); |