EuAndreh

You can get to gigantic success and extraordinary scale by growing vertically, without needing to add a very complex layer that kubernetes is.

Think of the many literal millions of lines of code, and thus, potential bugs and liabilities one inherits by "just using kubernetes".

It's not a requirement, neither problematic. Its simply unnecessary for anything remotely resembling a "one-person tech startup".

Besides unnecessary features like horizontal scaling, necessary features like restarting a service already exist, and most likely are already installed in the base distro and being used by the rest of the system. Its not like this couldn't be done before, all kubernetes provides is a conveniet and streamlined package for all that, at the cost of black-hole levels of extra complexity via several added indirections.

FTFY

Thanks for the improvements on POSIX, I've read many issues and discussions raised by you in the past couple of years.

If fact, I think it was one of yoir comments on make(1)'s dynamic dependency graph that reassured me I had a correct grasp on its execution model!

https://github.com/pyjarrett/simple_regex

I have my copy of "Practice of Programming" about to be delivered. Is your regex implementation available somewhere?

What's wrong with p-code bundled with an interpreter?

Some libc+cc combos add some code to do things the target architecture doesn't support natively, like ints of certain sizes. From this to the example you said, where in this spectrum do you consider it not to be compiled anymore?

Unless you're debugging the emitted binary instructions, why does the compiled output matter if it reaches the desired CPU and memory requirements?

Wouldn't that mean that, when using encrypted backups, secrets would have to be shared across multiple clients?

If I'm understanding it correctly, it sounds like an anti-feature. Do other backup tools do that?

A good language-specific package manager should know how to resolve its dependencies and maybe install them locally, but most importantly provide this information to the system package manager (apt, rpm, etc.) to handle.

Having "pip install x" is a poor man's ad-hoc system package manager.

    $ cat Makefile
    a\ file: ; echo 123 > '$@'
    $ make
    echo 123 > 'a file'
    $ cat a\ file
    123

Past all email limitations, a simple mbox archives everything. It works offline, is decentralized, etc.

As the saying goes, Jira is fine, the only problem is that it is Turing-complete.

After that, what you can do is ruin it, targetting a webpage for a specific screen size.

For instance, consider someone who has limited access to desktop computers and have to go by with a mobile device. These individuals do exist, and their access is as legitimate as any other.

    ... | ssh server.com dd of=out.tag.zstd

In this example, "mam_" is effectivelly a NIH namespace.

    C-x C-e

>In a C program taking the same approach (...)

"Writing C" and "rushing" is a strategy that cannot give you correct, robust software.

IMHO, the basic prosody setup is a bit simpler, but with the "extra" configuration such as retention policies, they're equal in setup effort.

On the other hand, prosody is an order of magnitute easier to maintain and administer. synapse is too brittle, and its not uncommon to use gigabytes of memory, while prosody's resource usage is barely noticible.

On the occasions that I wanted to look under the hood and skim the code, I felt more confortable understanding and hacking on prosody.

Overall, I found synapse to be needlessly complex and big. I don't know if that's because it's the first implementation and it accumulated a bunch of legacy code, or that's something that comes with Matrix itself.

I didn't get that. Won't this only happen to those using `-Werror` or something similar? If so, aren't they responsible for their breakage, and not the ecosystem?

  cut -d: -f2-