DragonI

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

require-from-twitter

Since Twitter doesn't have an edit button, it's a suitable host for JavaScript modules.

How to use

Source tweet: https://twitter.com/rauchg/status/712799807073419264

const leftPad = await requireFromTwitter('712799807073419264');

Why I hate TypeScript

Warning: These views are highly oppinated and might have some slightly incorrect facts. My experience with typescript was about 2 weeks in Node and a week in angular2.

Not Standard

TypeScript is implementing their own take on JavaScript. Some of the things they are writing will likely never make it in an official ES* spec either.

Technologies that have competing spec / community driven development have a history of failing; take: Flash, SilverLight, CoffeeScript, the list goes on. If you have a large code base, picking TypeScript is something your going to be living with for a long time. I can take a bet in 3 years JavaScript will still be around without a doubt.

Its also worth noting that they have built some things like module system and as soon as the spec came out they ditched it and started using that. Have fun updating!

Promises as EventEmitters

I was trying to understand JavaScript Promises by using various libraries (bluebird, when, Q) and other async approaches.

I read the spec, some blog posts, and looked through some code. I learned how to

The issue:

..mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.

(from a new defunct https://developers.google.com/mobile/articles/fast_buttons article)

touch-action CSS property can be used to disable this behaviour.

touch-action: manipulation The user agent may consider touches that begin on the element only for the purposes of scrolling and continuous zooming. Any additional behaviors supported by auto are out of scope for this specification.

	upstream websocket {
	server localhost:3000;
	}

	server {
	listen 80;
	server_name localhost;

	access_log /var/log/nginx/websocket.access.log main;

	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="utf-8">
	<title>vue inheritance</title>
	</head>
	<body>
	<my-student></my-student>
	<my-student first-name="Franz" last-name="Meier" :student-id="54321"></my-student>
	<my-professor first-name="Jared" last-name="Josey"></my-professor>

	# <type>: (If applied, this commit will...) <subject> (Max 50 char)
	# \|<---- Using a Maximum Of 50 Characters ---->\|


	# Explain why this change is being made
	# \|<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->\|

	# Provide links or keys to any relevant tickets, articles or other resources
	# Example: Github issue #23

	<?php

	namespace App\Http\Controllers\Auth;

	use JWTAuth;
	use App\Http\Controllers\Controller;
	use Tymon\JWTAuth\Exceptions\JWTException;
	use Tymon\JWTAuth\Exceptions\TokenExpiredException;
	use Tymon\JWTAuth\Exceptions\TokenInvalidException;

	Import-Module -Name D:\Temp\ACME-posh\ACMEPowerShell.psd1
	$domain = "mydomain.com"
	$certificiatePassword = "abcd1234"
	$email = "[email protected]"
	$vault = "D:\Vault\{0}\{1}" -f $domain, [guid]::NewGuid()
	mkdir $vault
	cd $vault

	Initialize-ACMEVault -BaseURI https://acme-v01.api.letsencrypt.org/
	New-ACMERegistration -Contacts mailto:$email