Skip to content

Instantly share code, notes, and snippets.

View nerdfiles's full-sized avatar
⚕️
bringing about the end-times of the philosophy

aha hah nerdfiles

⚕️
bringing about the end-times of the philosophy
View GitHub Profile
##
# Wifi WEP cracking cheat sheet.
#
# Original link: http://www.aircrack-ng.org/doku.php?id=how_to_crack_wep_with_no_clients
##
# monitor mode
airmon-ng start <IFACE>
module('myApp.directives',[])
.directive('rawInclude', [
'$http', '$templateCache', '$compile',
function ($http, $templateCache, $compile) {
return {
restrict: 'ECA',
terminal: true,
scope: false,
compile: function (telement, attr) {
var srcExp = attr.rawInclude || attr.src;

I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.

From Require.js - Why AMD:

The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"

I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.