Aleh Kashnikaў mkusher

#Understanding MVC And MVP (For JavaScript & Backbone Developers)

Before exploring any JavaScript frameworks that assist in structuring applications, it can be useful to gain a basic understanding of architectural design patterns. Design patterns are proven solutions to common development problems and can suggest structural paradigms to help guide us in adding some organization to our application.

I think patterns are exciting as they're effectively a grass roots effort that build upon the collective experience of skilled developers who have previously faced similar problems as we do now. Although developers 10 or 20 years ago may not have been using the same programming languages for implementing patterns, there are many lessons we can learn from their efforts.

In this section, we're going to review two popular patterns - MVC and MVP. The context of our exploration will be how these patterns are related to the popular JavaScript framework Backbone.js, which will be explored in greater detail later on.

I use tmux splits (panes). Inside one of these panes there's a Vim process, and it has its own splits (windows).

In Vim I have key bindings C-h/j/k/l set to switch windows in the given direction. (Vim default mappings for windows switching are the same, but prefixed with C-W.) I'd like to use the same keystrokes for switching tmux panes.

An extra goal that I've solved with a dirty hack is to toggle between last active panes with C-\.

Here's how it should work:

Here's a more in depth explanation of Angular's DI, RequireJS, and what's coming up in Angular 2.0 and ES6 modules.

Angular DI is not a module loader! It injects objects that have already been loaded using script tags. It does not do lazy-loading. Angular 2.0 will use ES6 import for module loading. Angular 2.0 will also add a DI layer that runs after the modules load.

I need to go over Java's import vs. JavaScript's require/import and Java singletons to further explain what Angular's DI is doing.

Java's import allows you to access another package's types without fully qualifying the package name. JavaScript's import loads a module and creates references to the module's exported objects. These are very different operations. JavaScript's import is powerful stuff! You have the objects, not just aliases to a package's types.

Singleton is a pattern, not the object itself. In Java you start with a type and have to create an instance. The singleton pattern ensures you have only 1 instance of that t

Currently considering https://github.com/webdriverio/webdrivercss

Core Goals:

Can test in up-to-date versions of all major browsers
Can test on up-to-date versions of all major OSes
Can test in IE9 (because Bootstrap v4 will support IE9+)
Don't want to have to setup/maintain our own cluster of VMs running all the necessary OSes (and all the versions of Windows)
Workflow for management of reference/baseline/norm screenshots

Procedural PHP Manifesto

We are web site developers (a.k.a. webmasters) and we just want to get stuff done. We don't need Object Orientation and we don't need Design Patters and other boring and not easy to learn and understand stuff to get in our way to get our sites up and running.

And that's why our values are:

Procedural Code over Object Orientation

No one actually needs OO to develop web applications
Classes with only static functions are ok, since it's just a way to keep functions in one place. And is still procedural

Explicitly load what you need over autoloaders

TDD: https://en.wikipedia.org/wiki/Test-driven_development
TDD profit graphs http://www.webcitation.org/61G4kow2C and http://www.agilemodeling.com/essays/costOfChange.htm
Unit testing: https://en.wikipedia.org/wiki/Unit_testing
Test classification: http://habrahabr.ru/company/npo-comp/blog/223833/
Testing mind map: https://github.com/polarnik/TypesOfTesting

And a ton of literature that doesn't directly mentioned in the presentation, but it still has a big influence on my speech:

http://habrahabr.ru/post/119465/ (rus)
https://blog.8thlight.com/uncle-bob/2014/04/30/When-tdd-does-not-work.html (eng)
http://img105.job1001.com/upload/adminnew/2015-02-05/1423102064-STSV0KT.pdf (eng and book!)

Разбираемся с синтаксисом шаблонов в Angular2

Многие впервые увидев синтаксис шаблонов Angular2 начинают причитать, мол ужас какой сделали, неужто нельзя было как в Angular1 хотя-бы. Зачем нужно было вводить это разнообразие скобочек, звездочек и прочей ерунды! Однако при ближайшем рассмотрении все становится куда проще, главное не пугаться.

Так как шаблоны в AngularJS являются неотъемлемой его частью, важно разобраться с ними в самом начале знакомства с новой версии этого фреймворка. Заодно обсудим, какие преимущества дает нам данный синтаксис по сравнению с angular 1.x. Причем лучше всего будет рассматривать это на небольших примерах.

Данная статья во многом основана на материалах этих двух статей:

Angular2: синтаксис шаблонов

	data IOAction a = Return a
	\| Put String (IOAction a)
	\| Get (String -> IOAction a)

	get = Get Return
	put s = Put s (Return ())

	seqio :: IOAction a -> (a -> IOAction b) -> IOAction b
	seqio (Return a) f = f a
	seqio (Put s io) f = Put s (seqio io f)

	"use strict";

	// Domenic needs a Tweeter
	function Domenic(tweeter) {
	this.tweeter = tweeter;
	}
	Domenic.inject = ["tweeter"];

	Domenic.prototype.doSomethingCool = function () {
	return this.tweeter.tweet("Did something cool!");

	{-# LANGUAGE TypeFamilies #-}

	import Data.Function (on)
	import Control.Applicative

	data EventData e = EventData {
	eventId :: Int,
	body :: Event e
	}