Porting an application across platforms is never particularly easy, nor very interesting. In fact, it's usually a terrible idea: in general, if it ain't broke, don't fix it. But sometimes you have to do it. Maybe a new platform has a feature you believe you can't live without, or the project scope is expanding in directions that make you feel like your original platform choice might not have been the best, or maybe it's just necessary to port for political reasons. Whatever.
For more information about Nix, please, read Domen's introduction to Nix package manager.
Usage:
$ nix-env -i -f default.nix
$ instance fg
{ | |
"name": "Speak Thai", | |
"description": "Reads out selected thai text", | |
"version": "0.1", | |
"permissions": ["contextMenus"], | |
"background": { | |
"scripts": ["speak-thai.js"] | |
}, | |
"manifest_version": 2 |
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important
or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
This is where any fun you might have been having ends. Now it’s time to get serious and talk about rules.
Writing CSS is hard. Even if you know all the intricacies of position and float and overflow and z-index, it’s easy to end up with spaghetti code where you need inline styles, !important rules, unused cruft, and general confusion. This guide provides some architecture for writing CSS so it stays clean and ma
#!/bin/bash | |
# | |
# Wrapper script for trello cli that appends default arguments as well as reads | |
# additional arguments from a file if it exists in the cwd. It is assumed | |
# the file contains a text string of arguments to append to the command. | |
# | |
# See https://github.com/brettweavnet/trello_cli/issues/22 for more details | |
# | |
# For example, the file .trellocli existing in a directory with the content: | |
# |
#!/system/bin/sh | |
# What is this? | |
# PSD (Pin to the SD card), is an auxiliary script that keeps your Apps "staying" on your SD card. | |
# "staying" is quoted because what it actually do is moving your app back to the SD card again after an update. | |
# Why? | |
# a. Since Android Lollipop, the apps you moved to the SD card will back to internal storage after an update. | |
# b. My phone has a small internal storage and running Android Lollipop. | |
# c. I am not going to buy another phone or downgrade to Kitkat. |
# Autogenerated input type of AddComment | |
input AddCommentInput { | |
# A unique identifier for the client performing the mutation. | |
clientMutationId: String | |
# The Node ID of the subject to modify. | |
subjectId: ID! | |
# The contents of the comment. | |
body: String! |
I want to write software that helps kill people.
Please, before you call the police and get my github account put on lockdown, allow me a moment to explain. What I really want to do is work on projects that advance the human condition and improve people's lives. I've been in a mad dash to learn how to program for the past four or five years exactly because I realized how much good I could do for the world with a computer.