ZUGFeRD is part of EU's creatively titled eInvoicing [0] project, compatible implementations should exist in other EU countries sooner or later.

[0]: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eInv...

You can also tell git that the .git dir is completely separated from the working dir:

    alias dogit='GIT_WORK_TREE=/path/to/src/dir GIT_DIR=/path/to/dotgit/dir git'
    dogit pull remote treeish

---

I set this up as a "poor man's version control" on a large client's server back in 2016-ish. I was lost for words when last year I saw my colleagues still using Ctrl-R to rerun that alias line.

Yes, that's roughtly what I am doing in my post-receive hook:

    export GIT_DIR=/path/repo
    export GIT_WORK_TREE=/path/working-directory
    git checkout -f

> they make the 'http://' not visible in the bar. What confusing signaling!

In recent versions of Chrome, you can right-click the bar and choose "Always show full URLs" to fix that particular stupidity.

Yeah, nowadays most of the sites are suffering from div-ititis that has no semantics, massive blackholes of JavaScript that have to be loaded and processed before you can even see plain text, and CSS class names that are randomly hashed with each deployment in the name of modularity.

General accessibility be damned.

<noscript> fallback messages be damned. (Except when snitching on your page views to Google Analytics, that's too important to be neglected! I wonder if GA has any default marker to let their customers distinguish these views from normal ones, or if that's still left to each customer to implement manually.)

UI customizations in the form of browser extensions and styles be damned.

Ad blocking be damned.

> use either an <a> or a <button>

Generally, it should be noted that an <a> tag is only appropriate if it makes sense to right-click this element and get options to "open in new tab" or "add to bookmarks". All the stupid "buttons" implemented as <a href="#"> + e.preventDefault() need to die.

Yea I use <a> if it's a navigation button for react-router. But it still shows up like a URL because we're using the Browser history (it just updates the URL and renders the new page, each route has a URL and resource id's are in the url). As opening the URL directly should work (if authenticated) it makes sense to use <a> tags.

I think what they mean is this: if you're dissatisfied with invoice PDFs generated and sent by Stripe, it's fairly common to disable the sending and use an integration [0] to generate/send them out instead. And then if you cancel that integration, oops, your customers no longer get their invoices.

[0]: https://stripe.com/partners/apps-and-extensions/invoicing

Hmm, interesting. They must know that I (we) are not using this, because I didn't even know this feature exists and our customers are happy getting sent Stripe invoices.

And if you thought that was not challenging enough:

https://rampion.github.io/RegHex/

> I don’t know any other language with lambdas which requires me to spell out explicitly which variables it should close over

PHP closures have to specify which variables they close over, and whether it's done by-val or by-ref [0].

Nowadays there's also a shorthand single-expression-closure syntax that closes implicitly and by value [1].

[0]: https://www.php.net/manual/en/functions.anonymous.php#exampl...

[1]: https://www.php.net/manual/en/functions.arrow.php

I'd say that Symfony reads like Java, whereas Laravel reads like a weird copy of Rails.