| /* | |
| * John Conway's Game of Life. | |
| * | |
| * This is written for POSIX, using Curses. Resizing of the terminal is not | |
| * supported. | |
| * | |
| * By convention in this program, x is the horizontal coordinate and y is | |
| * vertical. There correspond to the width and height respectively. | |
| * The current generation number is illustrated when show_generation is set. | |
| * |
a gist to recap the current status, also available as library picker!
do one thing only and do it well
I find myself in a tempest in a toaster. Yesterday I (and much of the web standards world) learned about two possible new HTML elements proposed by Google, std-toast and std-switch. I had no idea what “toast” meant in the context of the web, a problem shared my many other people. It turns out it’s a UI pattern, those little notices that pop up and then disappear without user interaction.
But wow, new HTML elements! This is the holy grail. In my part of the web we don’t even dream about new HTML elements. Oh, we’ve tried, but Hixie didn’t much care for footnote, WICG didn’t much care for list titles, and no one much cared about author. Just last week the author of the extensible web manifesto warned me to never expect new HTML elements, due to the difficulty of changing the parser.
But my concern wasn’t so much about the nature of the new elements, but of how we learned about them and what that says about how web standardization works. My [first tweet](https://twitter.com
| const publicPath = 'public'; | |
| // Node os module | |
| // The os module provides a number of operating system-related utility methods. | |
| // It can be accessed using: | |
| const os = require('os'); | |
| // Using a single monolithic configuration file impacts comprehension and | |
| // removes any potential for reusability. | |
| // As the needs of your project grow, you have to figure out the means to manage | |
| // webpack configuration more effectively. |
| /* NOTICE: THIS WAS MADE BACK IN 2017, OF COURSE IT'S NOT GOING TO WORK WELL NOW THAT TWITTER'S FUCKED THINGS UP */ | |
| @namespace url(http://www.w3.org/1999/xhtml); | |
| @-moz-document domain("twitter.com") { | |
| [data-component-context="suggest_recap"], | |
| [data-component-context="suggest_who_to_follow"], | |
| [data-component-context="suggest_activity"], | |
| [data-component-context="suggest_activity_tweet"], | |
| [data-component-context="suggest_recycled_tweet_inline"], | |
| [data-component-context="suggest_recycled_tweet"]{ |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title></title> | |
| <link rel="stylesheet" href="./style.css"> | |
| </head> | |
| <body> |
