Gustavo de Paula gustavo-depaula

AOE2HD - For Mac OSX

Estimated time: 10 minutes

Notice

This configuration worked for macOS High Sierra, Version 10.13.6.

According to the original Gist, PlayOnMac does not work on macOS Catalina, and issues have been reported with the latest version of Steam. Updating is in progress, read more here.

Everything I Know About UI Routing

Definitions

Location - The location of the application. Usually just a URL, but the location can contain multiple pieces of information that can be used by an app
1. pathname - The "file/directory" portion of the URL, like invoices/123
2. search - The stuff after ? in a URL like /assignments?showGrades=1.
3. query - A parsed version of search, usually an object but not a standard browser feature.
4. hash - The # portion of the URL. This is not available to servers in request.url so its client only. By default it means which part of the page the user should be scrolled to, but developers use it for various things.
5. state - Object associated with a location. Think of it like a hidden URL query. It's state you want to keep with a specific location, but you don't want it to be visible in the URL.

Here's a list of mildly interesting things about the C language that I learned mostly by consuming Clang's ASTs. Although surprises are getting sparser, I might continue to update this document over time.

There are many more mildly interesting features of C++, but the language is literally known for being weird, whereas C is usually considered smaller and simpler, so this is (almost) only about C.

1. Combined type and variable/field declaration, inside a struct scope [https://godbolt.org/g/Rh94Go]

struct foo {
   struct bar {
 int x;

Plain JavaScript objects are better than classes when they can be used, and many popular modern frameworks have adopted their use.

Consider that in React a component can be created as either a class or as an object.

// using a class
class Welcome extends React.Component {
  render() {
 Hello, {this.props.name}

How do I dropdown?

This is how you dropdown.

<details>
<summary>How do I dropdown?</summary>
<br>
This is how you dropdown.

First couple things I thought about when migrating after reading the docs

So migrating my existing app wasn't as troublesome as I originally thought. First thing I did was take a look at my router and routes and figure try to make a mental model of all the files where I had nested routes in the existing app because those components/containers will contain {this.props.children}. So I need to replace those with the nested <Match /> components.

So just to give an example:

In v2:

<Router history={history}>
  <Route path="/" component={App}>

	import PropTypes from 'prop-types';

	type Omit<T, K> = Pick<T, Exclude<keyof T, K>>;

	type Defined<T> = T extends undefined ? never : T;

	/**
	* Get the type that represents the props with the defaultProps included.
	*
	* Alternatively, we could have done something like this:

	function logColor(color, args) {
	console.log(`%c ${args.join(' ')}`, `color: ${color}`);
	}

	const log = {
	aliceblue: (...args) => { logColor('aliceblue', args)},
	antiquewhite: (...args) => { logColor('antiquewhite', args)},
	aqua: (...args) => { logColor('aqua', args)},
	aquamarine: (...args) => { logColor('aquamarine', args)},
	azure: (...args) => { logColor('azure', args)},

	The question was asked why I (as a programmer who prefers dynamic languages) don't consider static types "worth it". Here
	is a short list of what I would need from a type system for it to be truely useful to me:

	1) Full type inference. I would really prefer to be able to write:

	(defn concat-names [person]
	(assoc person :full-name (str (:first-name person)
	(:second-name person))))

	And have the compiler know that whatever type required and produced from this function was acceptible as long as the