programmeruser2

Angular: Just say no

A collection of articles by AngularJS veterans, sometimes even core committers, that explain in detail what's wrong with Angular 1.x, how Angular 2 isn't the future, and why you should avoid the entire thing at all costs unless you want to spend the next few years in hell.

Reason for this: I'm getting tired of having to explain to everyone, chief of which all the indiscriminate Google Kool-Aid™ drinkers, why I have never believed in Angular, why I think it'll publicly fail pretty soon now (a couple years), and why it's a dead end IMO. This gist serves as a quick target I can point people to in order not to have to parrot / compile the core of the articles below everytime. Their compounded reading pretty much captures 99% of my view on the topic.

This page is accessible through http://bit.ly/angular-just-say-no and http://bit.ly/angularjustsayno, btw.

I won't be using Angular for my next project...and neither should you. • Robe

"Scar Tissues Make Relationships Wear Out"

04/26/2103. From a lecture by Professor John Ousterhout at Stanford, class CS142.

This is my most touchy-feely thought for the weekend. Here’s the basic idea: It’s really hard to build relationships that last for a long time. If you haven’t discovered this, you will discover this sooner or later. And it's hard both for personal relationships and for business relationships. And to me, it's pretty amazing that two people can stay married for 25 years without killing each other.

[Laughter]

> But honestly, most professional relationships don't last anywhere near that long. The best bands always seem to break up after 2 or 3 years. And business partnerships fall apart, and there's all these problems in these relationships that just don't last. So, why is that? Well, in my view, it’s relationships don't fail because there some single catastrophic event to destroy them, although often there is a single catastrophic event around the the end of the relation

Source: man syscall

Architecture calling conventions

Every architecture has its own way of invoking and passing arguments to the kernel. The details for various architectures are listed in the two tables below.

The first table lists the instruction used to transition to kernel mode, (which might not be the fastest or best way to transition to

	import leveldb

	db = leveldb.LevelDB('./db')

	db.Put('hello', 'value')
	db.Put('world', 'value')

	for k in db.RangeIter(include_value = False):
	print 'K', k

	<?php
	if (file_exists($_SERVER['SCRIPT_FILENAME'])) {
	return false;
	}

	$_SERVER['DOCUMENT_ROOT'] = empty($_SERVER['DOCUMENT_ROOT']) ? $_SERVER['PWD'] . '/www' : $_SERVER['DOCUMENT_ROOT'];
	$htaccess = $_SERVER['DOCUMENT_ROOT'] . '/.htaccess';
	$rewrites = array();
	if (file_exists($htaccess)) {
	$fp = fopen($htaccess, "r");

	# --------
	# Hardware
	# --------

	# Opcode - operational code
	# Assebly mnemonic - abbreviation for an operation

	# Instruction Code Format (IA-32)
	# - Optional instruction prefix
	# - Operational code

	#include <stdio.h>
	#include <stdlib.h>
	#include <string.h>
	#include <dlfcn.h>

	int main(int argc, char** argv)
	{
	void *handle;
	void (func_print_name)(const char);

	// I had problems getting mouse movement events working in ncurses, but after
	// some research, it seems as if this is how you can do it. The magic is in the
	// printf("\033[?1003h\n") which was the missing piece in the puzzle for me
	// (see console_codes(4) for more information). 1003 means here that all events
	// (even position updates) will be reported.
	//
	// This seems to work in at least three X-based terminals that I've tested:
	// xterm, urxvt and gnome-terminal. It doesn't work when testing in a "normal"
	// terminal, with GPM enabled. Perhaps something for the next gist version? :)

	#!/usr/bin/env node
	// run with: node sequencehunt_server.js
	// info page: http://localhost:8080/info
	// correct values: http://localhost:8080/check?val0=4&val1=12&val2=77&val3=98&val4=35

	var http = require('http');
	var url = require('url');

	var TimingAttackProtectionSeconds = 3;

	def decode_flask_cookie(secret_key, cookie_str):
	import hashlib
	from itsdangerous import URLSafeTimedSerializer
	from flask.sessions import TaggedJSONSerializer
	salt = 'cookie-session'
	serializer = TaggedJSONSerializer()
	signer_kwargs = {
	'key_derivation': 'hmac',
	'digest_method': hashlib.sha1
	}