The "O" in TOML is not deserved in my opinion.

I tend to disagree a bit. In the early days, most scams at least pretended to have some non-pump-and-dump usecase. Like Dentacoin or Filecoin. You could at least pretend to "buy filecoin today so you can store PB's worth of data in a year" or "buying Dentacoin now because in a year you need some dental work done".

Nowadays all new tokens/coins have 0 usecases attached and only exist to be pancake swapped and pumped and separating other people from their money. It's all about lending, yielding, farming, interest rates, staking, ...

I found one Austrian source ( https://www.vol.at/wo-die-produktion-urlaub-macht/3314076 ) mentioning the issue and I can see how it would make sense for some industries to need some maintenance time each year.

[1] https://www.wikiwand.com/en/Common_Gateway_Interface

What options do I as a "normie" have to give feedback? Is there really only one way, to use the ancient Bugzilla and hopefully finding a ticket somewhere?

[1] https://www.youtube.com/c/firefox/videos

I for one could live without go get alltogether. In 99% of cases it boils down to a simple git clone anyway, which could (should?) be done by the package manager anyway.

Maybe it's time to re-evaluate the existence of go get, now that we're seeing that "just clone master and hope nothing breaks" has obviously not worked for everyone outside of Google? Maybe bundling Go (the compiler and linker) with tools for fetching source code wasn't such a good idea after all?

Just my 2 cents...

[Edit: Ah, the chain is incomplete, see https://www.ssllabs.com/ssltest/analyze.html?d=www.equifaxse...]

That being said, we did run into a few issues that forced us to go back to older Caddy versions, like broken websocket support or the timeout issue in 0.9.5. Also, sometimes the documentation is a bit lacking and unclear. DNS resolution seems to be flaky sometimes (we're using alpine-based containers and sometimes Caddy just won't resolve names of other containers, even though a curl inside the container can resolve the names just fine).

So if you've got a working nginx setup, I'd say stick with it. For new projects it is worth to check out Caddy. The issues we ran into occured early in our development process, they didn't just suddenly happen in production, so once you've tested everything, Caddy just works.

Sadly you missed out on the major advances that happened in the PHP ecosystem, like properly namespaced code, massive performance gains since PHP 5.3, Composer, modern frameworks, the PSR initiative (even though one might not agree with all their "standards") and so much more. So I would not judge PHP's evolution by that one proposal ;) A lot more were accepted, implemented and released, from type annotations to the spacechip operator. Personally I'm thankful that nobody further pursued the idea of tainted strings for PHP.

    gzip -9: 27.574s, 48MiB output
    zstd -9: 14.182s, 41MiB output

[1] http://www.ilikebigbits.com/blog/2015/2/9/the-myth-of-ram-pa...

    { delete: "me" }

[EDIT: See also this YouTube video, where Douglas Crockford explains it himself: https://youtu.be/-C-JoyNuQJs?t=5m]

[1] https://www.youtube.com/watch?v=wQS910WVlKc