Jesse Clark gearsandcode

Rational

The TypeScript 2.0-typescript branch seems to be lagging and isolated, with all components having 2.0-preview branches yet the 2.0-typescript README has not even been changed from the 2.0-preview text. Until a proper Polymer/TypeScript workflow is recommended and supported by the Polymer team, the basic idea is to maximize on the use of the essential features that TypeScript offers and not invest too much into hard-core features that require the workflow to be tightly coupled with late-bound transpilation of complex TypeScript projects (with modules / loaders). Another thing to address is how Hydrolysis fails to analyze and iron-component-page fails to document TypeScript-based components, not making good use of the elegant property declarations and decorators used in TypeScript. For now, a temporary workaround is needed to ensure that properties are defined and documented with proper types and default values, but the workaround needs to be easily replaceable once we have better Polymer/TypeScript

General

Templates written a giant string in components.

This tutorial demonstrates this: https://angular.io/docs/ts/latest/tutorial/toh-pt1.html you don't get syntax coloring, or any benefits you'd get from a good html/templating tool.

(( flashbacks to inline html strings in C++ ))

Tag bloat with ngDirectives (such as ngFor)

from an angular.io example:

Mac web developer apps

This gist's comment stream is a collection of webdev apps for OS X. Feel free to add links to apps you like, just make sure you add some context to what it does — either from the creator's website or your own thoughts.

— Erik

	version: 2

	# Re-usable blocks to reduce boilerplate
	# in job definitions.
	references:
	container_config: &container_config
	docker:
	- image: my-company/circleci:gcloud # We use a custom Alpine Linux base image with the bare minimum
	working_directory: /tmp/workspace
	restore_repo: &restore_repo

	// Async/Await requirements: Latest Chrome/FF browser or Babel: https://babeljs.io/docs/plugins/transform-async-to-generator/
	// Fetch requirements: Latest Chrome/FF browser or Github fetch polyfill: https://github.com/github/fetch

	// async function
	async function fetchAsync () {
	// await response of fetch call
	let response = await fetch('https://api.github.com');
	// only proceed once promise is resolved
	let data = await response.json();
	// only proceed once second promise is resolved

	/* Material Design Adaptive Breakpoints */
	/*
	Below you'll find CSS media queries based on the breakpoint guidance
	published by the Material Design team. You can choose to use, customise
	or remove these breakpoints based on your needs.

	http://www.google.com/design/spec/layout/adaptive-ui.html#adaptive-ui-breakpoints
	*/

	/* mobile-small */

	<!doctype html>
	<html>
	<head>
	<!-- Web Component Polyfill for old browsers -->
	<script src="https://www.polymer-project.org/platform.js"></script>
	<!-- Release candidate of next React -->
	<script src="http://fb.me/react-with-addons-0.12.0-rc1.js"></script>
	<script src="http://fb.me/JSXTransformer-0.12.0-rc1.js"></script>

	<!-- Import a web component -->

	// ----
	// Sass (v3.3.4)
	// Compass (v1.0.0.alpha.18)
	// ----

	// Capitalize string
	// --------------------------------------------------------------------------------
	// @param [string] $string
	// --------------------------------------------------------------------------------
	// @return [string]

	// ----
	// Sass (v3.3.0.rc.2)
	// Compass (v1.0.0.alpha.17)
	// ----

	//
	// map-fetch($map, $keys)
	//
	// An easy way to fetch a deep value in a multi-level map. Works much like
	// map-get() except that you pass multiple keys as the second parameter to