android:clickable="true"
android:background="?attr/selectableItemBackground"or
| # Greatest common divisor of 1 or more numbers. | |
| from functools import reduce | |
| def gcd(*numbers): | |
| """ | |
| Return the greatest common divisor of 1 or more integers | |
| Examples | |
| -------- |
| /* | |
| * Copyright (C) 2014 skyfish.jy@gmail.com | |
| * | |
| * Licensed under the Apache License, Version 2.0 (the "License"); | |
| * you may not use this file except in compliance with the License. | |
| * You may obtain a copy of the License at | |
| * | |
| * http://www.apache.org/licenses/LICENSE-2.0 | |
| * | |
| * Unless required by applicable law or agreed to in writing, software |
Picking the right architecture = Picking the right battles + Managing trade-offs
| // No Security | |
| { | |
| "rules": { | |
| ".read": true, | |
| ".write": true | |
| } | |
| } |
| FROM containership/alpine-node-yarn | |
| COPY internals/scripts myappname/internals/scripts | |
| COPY package.json myappname/package.json | |
| COPY yarn.lock myappname/yarn.lock | |
| COPY build myappname/build | |
| COPY server myappname/server | |
| WORKDIR myappname/ |
Check comments below, this is only my opinion and a choice specific to my use case
We've architected a SPA to be universal-ready. It grew a lot, when we introduced code splitting we realised converting to CSS in JS was unavoidable in order to have pre-rendering and not load all our CSS up front. We've procrastinated on looking at CSS in JS properly, prioritasing immediate business needs, but kept an eye on industry evolutions.
Our CSS solution for components was a CSS companion file per component, imported with style / postCSS loader (with webpack) but no CSS modules: we were missing a tighter coupling between component rendering and styles. We were at the bottom of the CSS and componentization ladder, the following links have influenced us in choosing the right solution for us:
| #!/usr/bin/env bash | |
| set -x | |
| shopt -s extglob dotglob | |
| cd "$HOME" | |
| rm -rf "$HOME/TEMP_DIR" | |
| mkdir "$HOME/TEMP_DIR" | |
| cd "$HOME/TEMP_DIR" | |
| git init |
Note:
When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.
If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code: