Chris mayinx

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!

Dynamic Dispatch
Dynamic Method
Ghost Methods
Dynamic Proxies
Blank Slate
Kernel Method
Flattening the Scope (aka Nested Lexical Scopes)
Context Probe
Class Eval (not really a 'spell' more just a demonstration of its usage)
Class Macros

	<script setup>
	import { ref, onMounted } from 'vue';
	import AppForm from './components/AppForm.vue';
	import AppList from './components/AppList.vue';
	import AppLoading from './components/AppLoading.vue';

	import useFetch from './use/useFetch';

	const rootUrl = 'https://my-json-server.typicode.com/tq-bit/use-fetch-json-mock';
	const { loading, results, getJson } = useFetch(rootUrl);

	import React, { useState, useEffect } from "react";
	import axios from "axios";

	const App = () => {
	const [username, setUsername] = useState("");
	const [password, setPassword] = useState("");
	const [user, setUser] = useState();

	useEffect(() => {
	const loggedInUser = localStorage.getItem("user");

	/*
	* Handling Errors using async/await
	* Has to be used inside an async function
	*/
	try {
	const response = await axios.get('https://your.site/api/v1/bla/ble/bli');
	// Success 🎉
	console.log(response);
	} catch (error) {
	// Error 😨

	/* Flexbox
	// ================================================== */
	.d--f { display: flex; }
	.d--if { display: inline-flex; }

	/* Flex direction */
	.fd--r { flex-direction: row; } /* Default */
	.fd--rr { flex-direction: row-reverse; }
	.fd--c { flex-direction: column; }
	.fd--cr { flex-direction: column-reverse; }

	{% macro input(name, value, type, attributes) %}
	<input name="{{ name }}" type="{{ type }}" value="{{ value }}"{% for attr, value in attributes %} {{ attr }}="{{ value }}"{% endfor %}{% if not attributes.id is defined %} id="{{ name }}"{% endif %}/>
	{% endmacro %}

	{% macro text(name, value, attributes) %}
	{% from _self import input %}
	{{ input(name, value, "text", attributes) }}
	{% endmacro %}

	{% macro password(name, value, attributes) %}


	/*
	##Device = Desktops
	##Screen = 1281px to higher resolution desktops
	*/

	@media (min-width: 1281px) {

	/* CSS */

	HTTP status code symbols for Rails

	Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings.

	Status Code Symbol
	1xx Informational
	100 :continue
	101 :switching_protocols
	102 :processing

	<snippet>
	<content><![CDATA[module ${1:${TM_FILENAME/(?:\A\|_)([A-Za-z0-9]+)(?:\.rb)?/(?2::\u$1)/g}}
	extend ActiveSupport::Concern

	included do
	$2
	end
	end]]></content>
	<tabTrigger>mod</tabTrigger>
	<scope>source.ruby, source.ruby.rails, source.rails</scope>