| javascript:[].forEach.call(document.querySelectorAll('.evt-lk,.cbrdcc,.cloc'), (e) => e.innerHTML = ''); [].forEach.call(document.querySelectorAll('.cbrd, .rb-n'), (e) => { e.style.backgroundColor = '#9ea0ff'; e.style.borderColor = '#3d40d9'; e.style.color = '#1d1d1d' }); [].forEach.call(document.querySelectorAll('.rb-ni > div'), (e) => e.style.borderColor = 'transparent #9ea0ff'); [].forEach.call(document.querySelectorAll('.cbrd .mask'), (e) => e.parentNode.removeChild(e)); void(0) |
| function blockEnter(evt) {return true;} | |
| function validarNoUsarTecladoReal_OnKeyPress(_object){return false;} |
Hi there! In November 2014, We began with the idea of create a Node SchoolGirls chapter in Medellin - Colombia with the help and encouragement of MedellinJS community. The objective was to spread Node knowledge among women and it resulted in a very interesting experiment.
We have learnt a lot! at the beginning we only used the self guide workshop, but the frustration and struggle to finish it was so high, that the outcome was a lot of desertions. We started with 25 assistants, between teenagers, beginners and girls from different backgrounds like, biology, artistics, psychology, senior engineers that wanted to catch up with the new technologies, among others. After the second workshop (and after a lot of tears and frustrating faces), 8 girls remained, and the other ones never came back even with coaching and motivation attempts.
![Primeras reuniones del año Javascripting - Learnyounode](https://cldup.com/YD0rjo4JxY.jpg "Primeras versiones del año Javascripting -
| #!/bin/bash | |
| replacements=( | |
| "NanAsyncWorker/Nan::AsyncWorker" | |
| "NanAsyncQueueWorker/Nan::AsyncQueueWorker" | |
| "NanCallback/Nan::Callback" | |
| "NanSetInternalFieldPointer/Nan::SetInternalFieldPointer" | |
| "NanGetInternalFieldPointer/Nan::GetInternalFieldPointer" | |
| "NanNewBufferHandle\\(([^;]+);/Nan::NewBuffer(\\1.ToLocalChecked();" | |
| "(NanNew(<(v8::)?String>)?\\(\"[^\"]*\"\\))/\\1.ToLocalChecked()" |
After publishing my article on ECMAScript 6, some have reached out to ask how I exactly I make it all work.
I refrained from including these details on the original post because they're subject to immiment obsoletion. These tools are changing and evolving quickly, and some of these instructions are likely to become outdated in the coming months or even weeks.
When evaluating the available transpilers, I decided to use 6to5, which has recently been renamed to Babel. I chose it based on:
| The bizantine generals problem - Lamport | |
| Why Do Computers Stop and What Can Be Done About It? - Jim Gray | |
| Why do Internet services fail, and what can be done about it? - Oppenheimer | |
| Lightweight Recoverable Virtual Memory - M. Satyanarayana | |
| Principles of Antifragile Software - Martin Monperrus | |
| Building on Quicksand - Helland, Campbell | |
| Crash-Only Software - Candea, Fox | |
| Fault Tolerance via Idempotence - Ramalingam, Vaswani | |
| Fundamental Concepts of Dependability - Avizienis, Laprie, Randell | |
| How Complex Systems Fail - Richard I. Cook, MD |
The final result: require() any module on npm in your browser console with browserify
This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.
Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5
These are all the JSConf 2014 slides, codes, and notes I was able to cull together from twitter. Thanks to the speakers who posted them and thanks to @chantastic for posting his wonderful notes.
The prep-script.sh will setup the latest Node and install the latest perf version on your Linux box.
When you want to generate the flame graph, run the following (folder locations taken from install script):
sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0