justhelpingout
Otherwise, we definitely agree. We are fallen creatures and will drive earth to hell, regardless of which car we decide to drive there in. Only external help can save us from ourselves.
If, on the other hand, moral rules and ethics are due to the natures of things then there must be someone who intended things to exist in the manner they are intended to exist. That being must be a person because of the principle of sufficient cause (since we exist). Faith is the response to communication from this person. It does not require abandoning of reason, but simply picks up where reason cannot ascend to because of its lack of perspective.
[1]: https://www.win.tue.nl/~aeb/linux/hh/thompson/trust.html> This new runtime allows you to take advantage of Python's vibrant ecosystem of open-source libraries and frameworks. While the Python 2 runtime only allowed the use of specific versions of whitelisted libraries, Python 3 supports arbitrary third-party libraries, including those that rely on C code and native extensions. Just add Django 2.0, NumPy, scikit-learn or your library of choice to a requirements.txt file. App Engine will install these libraries in the cloud when you deploy your app.
You are spot on. This system must exist in-itself. That is, it must be so simple that its existence cannot be separated from its nature (to use Aristotelean terms). In other words, I AM WHO AM.
sqlite3 .tup/db 'select name from node where type=4' | xargs echo rm -f
[1]: https://github.com/gittup/tup/issues/120#issuecomment-64832104but the former is more like INFO while the latter is more like `man builtins` (that is, it assumes you already know a lot about the system)
The best tagging mechanism these days is `Nominal<T>` (which has no emit) or `As<T>` (which has a minimal amount of emit):
interface Nominal<T> {
'nominal type tag': T
}
class As<T> {
private tag: T
}
Both are used in the same manner: const enum SomeTag { }
type Something = number & As<SomeTag>
// or
type Something = number & Nominal<SomeTag>
You can even avoid the boilerplate of `const enum` if you make the `T` of `As` or `Nominal` `T extends string`: type Something = number & As<'some:unique:string:tag'>
In both cases, the values are not unified, so: type Something = number & As<'kind1'>
type SomethingElse = number & As<'kind2'>
var x: Something = 123 as Something;
var y: SomethingElse = 456 as SomethingElse;
x = y; // Type 'SomethingElse' is not assignable to type 'Something'.