preseinger

my comment in no way takes the thread into a flame war, and i'm pretty frustrated that it's being judged that way

it's commonly totally sufficient for IDs to represent a rough sort order

millisecond precision is great for a lot of use cases

the point isn't that issues and PRs exist, it's that the maintainers don't seem to know what they're doing

this is self-evident from a cursory review

link me any 3 non-trivial merged PRs and i'm happy to point out the problem i'm describing

and what does your experience tell you about applications which are not written in PHP, and which need to handle more than 1000 concurrent users?

code generators are programs written in an existing programming language, which produce target language source code as output

macros are programs written in a separate, unique, often turing-complete meta-language, which is implemented entirely in the compile phase of the language which supports them

they're in no way equivalent

usually, code generation is preferable to metaprogramming, mostly because it is easier to understand and maintain

metaprogramming is not a virtue

programming languages do not themselves need to be programmable

and a government warrant bypasses all of that

there was this whole thing with edward snowden a few years ago, maybe you remember?

where does all of that hardware live?

unless it's in your home, it's not trustable

bare metal has high capex and low opex

cloud vms have low capex and high opex

which one is more expensive is a function of many variables

how do you know your network is trusted and/or private?

trick question: you can't

even the network links between hosts in a single rack in a DC can be vulnerable

no, it isn't

it's an unsatisfiable requirement, and unnecessary to substantiate the legal claims

it's dumb to talk about

yes, really

feeding input to a program is pretty clearly categorically different than providing source material to a human being