DCoder

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.

It's mildly amusing to see kudos for a solution that lacks any <noscript> support.

> 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.

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

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.

Mozilla runs a DB of their own: [0]. Although their IRC network closed down recently, so this might not last long either.

And there's also XKCDB [1].

[0]: http://quotes.burntelectrons.org/browse

[1]: http://www.xkcdb.com/

This is like asking "vim or emacs". You'll never change anyone's mind on the matter, but you'll get the same old arguments from ~ten years ago [0] about how this is both "very simple†" and "pointless mental overhead" at the same time.

† (if you follow these rules I memorized to show off how smart I am).

---

[0]: https://github.com/twbs/bootstrap/issues/3057

Oh, that makes sense, thanks.

The guide also says you need to close Event Viewer before installing. I'm not sure I want to know why.

That reminds me of a vendor who wraps SAP Business One in their own webservice. This webservice has two business methods.

The first one, ExecuteXML, takes an <XmlBody> representing a regular SAP B1 XML request and passes it on to one of the real SAP services. We have to find our own XSDs for the inner part, because they sure as hell don't have those.

The second one is ExecuteSQL. It lets us run raw SQL against the SAP database. It doesn't have any support for prepared parameters. What it does have is a blacklist to prevent DDL and other funny business, such as semicolons. This blacklist runs on the raw string you send, and doesn't understand any escape characters. To send a string containing a literal semicolon, I had to turn it into CONVERT(VARCHAR(MAX), 0x...).

TypeScript spoiled me. I want PHP to have generics and all the type-system goodness that TS brings.

W3C recommends the same pattern: [0].

[0]: https://www.w3.org/International/questions/qa-personal-names

> Can I possibly even start the discussion at why the hell these things are being named in this way?

This reminds me a lot of Perl with its creative naming for things, e.g. promises giving you a `Vow` object that you can `keep()` or `break()`. Or how you `bless` an associative array into becoming an object of a certain class.

On the one hand, it is good to have precise and specific terms without reaching for a thesaurus or overloading the same term (e.g. the many meanings of `static` in C).

On the other hand, if every framework and language invents its own terms for everything under the sun, that will not help polyglots or newcomers.

(On the third hand, we have foreigners trying to spot a difference between a "promise" and a "vow".)

Promises are my favourite example of this, because just between C++, C#, JavaScript, and Perl, I can find three-and-a-half different taxonomies for the same functionality.

Ghostery already does this kind of forging for many blocked gadgets.

What are the odds that those hacks have been broken by Chrome updates since then?

New printer next year: "Hmm, I can't contact my telemetry server with these internet settings… time to connect to any open Wi-Fi I can find nearby!"

The behaviour you're referring to is actually a global property `window.event` [0]. Although it's part of the DOM spec, it's only there for historical reasons and should definitely be avoided.

[0]: https://developer.mozilla.org/en-US/docs/Web/API/Window/even...

I wrote up one example that was particularly frustrating when I realized it [0].

[0]: https://www.reddit.com/r/programming/comments/ar1qj1/_/egl52...

TypeScript was and still is a very necessary addition over plain JS, but everything else you said is spot on. This ecosystem is very much a Red Queen's race, you have to learn all sorts of tooling that will be deprecated and forgotten in two years or less.

> It's worth remembering that history is fluid, and we have to update the facts constantly. Churchill's war diaries were taken as fact until about 1990, when it became apparent that he had lionised himself to some degree.

It should be noted that the Soviet state was very aggressive in whitewashing themselves and marring their opponents. "Who needs your damned truth if it makes our lives more difficult", one of their leaders said. Their documents should not be taken at face value.

Moreover, some archives were destroyed a) to prevent them from being captured during the war, especially in the 1941 defense of Moscow, and b) to cover up whatever the leaders considered too sensitive later. This second portion also includes docs relating to post-WW2 events like the Totskoye nuclear exercise [0], destroyed decades after the fact because "the archives ran out of space".

[0]: https://en.wikipedia.org/wiki/Totskoye_nuclear_exercise

I can't comment for sure if they still have the source, but I know that EA made changes to those games when they released The First Decade [0] to make their CD-checks accept the new DVD. Most of the games were recompiled (so source was available) for that.

---

But the RA2: Yuri's Revenge binary was just patched where needed. This distinction was made because at the time YR already had some hardcore fans decompiling it and enhancing it, EA's community manager heard about this and made sure that community effort was not destroyed. I was one of those fans, and taking it apart was one hell of an adventure. We didn't decompile all of it, but we figured out many details, and added a lot of bugfixes and enhancements. It's not the same thing as the real source code, but you can see what we got in [1]/[2]/[3] (unfortunately those haven't been updated in a while).

[0]: https://en.wikipedia.org/wiki/Command_%26_Conquer:_The_First...

[1]: https://github.com/Ares-Developers/YRpp

[2]: https://github.com/Ares-Developers/Ares

[3]: https://www.modenc.renegadeprojects.com/Contributing_to_Ares

Browser vendors are paying less and less attention to EV anyway [0].

[0]: https://www.troyhunt.com/extended-validation-certificates-ar...

> the keepass entropy estimate presumably […] tries

KeePass sources are available [0], you can see the specific algorithms it uses in [1].

[0]: https://sourceforge.net/projects/keepass/files/KeePass%202.x...

[1]: https://fossies.org/windows/misc/KeePass-2.42.1-Source.zip/K...