shakesbeard

What a lot of folks are struggling to understand (myself included) is how this actually reflects on the quality of life?

You're more productive? Nice ... for you or your business/employer? Do you also get more free time out of it? With all this free time you could actually travel and do a language school for 3 months. That sounds like an improvement in quality of life to me. Not better translations in that language.

The life of my family (we have a good life) hasn't become significantly improved with LLMs. We still struggle with the same problems as before. These companies don't solve the big problems of societies and that's why I feel like their value is not justified.

Slack (canvas and huddles), Circle CI and Bitbucket are also reporting issues due to this.

Same. Clicked around. Was annoyed that a single click on an icon opened the window and not a double click. Used the navigation a bit and left.

No idea what they do.

That's literally how any representative democracy work, just at a different level? The Free State of Bavaria could say the same about the Federal Republic of Germany.

We've only made good experiences with layered architecture (onion architecture in particular, which is quite straight forward). We also never built it with the idea in mind to ever replace the storage engine. No, the big, big benefit has been that we can test everything without ever mocking a single class.

I also don't get the point about "going back to IoC" ... how is that mutually exclusive from using a layered architecture. This section was weird and didn't offer any good alternative.

> and now 20 years later we are still stuck with the same garbage.

and it hasn't been an issue ever. because all userland code lives in its own namespaces.

That's just not true. It's not JS. Composer will install exactly one version of every package. If your dependencies have incompatible dependencies themselves, then Composer will refuse to install the package. And this fact has led to PHP packages actually being maintained and kept compatible with each other. Of course, sometimes you run into dependency issues, but it's worth it because you'll always have quite clean, flat and small vendor directory. Compared to the node_modules horror it's great for maintenance.

I loved Flattr ~10 years ago. You said "I have $40/month" and then these funds were allocated based on which things you flattr'd during the month (there were little buttons on the websites/blogs). Of course you could also say "include this content creator every month".

It was so simple and elegant. As a consumer I had cost control, too. Plus there were no micro-transactions, only one charge to me.

You shouldn't deploy .env files to production. You should set the actual environment variables on production. .env files are intended for convenience on non-prod systems.

wow, now that's a website I haven't thought of in a while

They provide monthly torrents. Can't imagine that to be too slow unless there's literally no one seeding.