factotvm

I love that this is open source, thank you. I'm not a fan of TypeScript on Node for this solution space. For a payment gateway, I'd want a program that can't modify itself from external sources. Programs in this runtime can rewrite themselves while running, and the Dockerfile doesn't lock it down. So as it stands, nothing at the runtime level prevents prototype pollution. And a config defect is the kind of bug that keeps on giving.

No, it’s a lost sale.

It probably started with the Third Amendment to the Constitution, continued with the Posse Comitatus Act, and was alive and well last November under the leadership of Mark Kelly.

The important words are, American citizens. In times past, the thought of "waging war" against your own citizens would be a bad look.

> In order to fix this, we might start sending out satellites in every direction

Minor correction: Satellites don't go in every direction; they orbit. Probes or spaceships are more appropriate terms.

The laughable thing here is the "argument" that one cannot judge the societal impact of the FBI unless one has worked in law enforcement.

Read The Fine Prompt, more or less, right?

Don’t forget that most modern version control systems are distributed. The same can not be said for ticketing systems.

Not to mention, the best commit messages are about the code that isn’t there.

As you say, we know what’s there. I need the author to tell me why it’s there, and perhaps what other alternatives were abandoned because they didn’t work.

You know, so I don’t waste a day finding out for myself why you didn’t just do ${obvious}.

> 2. Margin of commit messages is often too small for documenting the rationale - this job is better left for tickets.

The commit message lives with the code. The number of times in my career that a company has migrated, changed, consolidated, or otherwise made all those links in commit messages obsolete, well I don't quite yet need two hands. But I see a lot of dead ends to context in code bases.

Only if gun manufacturers are liable for murders.

I read Head First Design Patterns years and years ago. I'm a fan of the series. It's less for dummies and more using ideas from psychology to help you learn the material. I'll forever recall the power and conciseness of the Decorator pattern for computing the price of coffee drinks when there are as many variations as there are people. Starbuzz...

From my memory banks after close to 20 years:

    SoyDecorator: CoffeeDecorator {
        price: Cents { price + 90¢ } // Soy adds 90 cents to the price
    }

Edit: My regret is lending it to someone and never getting it back. I believe I might get this bundle.

You can disambiguate two types with the same name from different libraries, e.g. `Factotvm.URL` and `Foundation.URL`. Do you mean something more full-featured? You are not prefixing types with three letters, if that's what you think has to be done.

I don't know if it's still the case, but there was an annoyance where you couldn't have a type with the same name as the package. But that is hardly a lack of namespaces.

I'd like to see the difference in bug detection between "pull requests" vs. "over-the-shoulder code reviews".

Edit: or, rather, in my experience the author of the code often finds the bugs when explaining it to the person standing next to them. This goes away in the GitHub-style pull request.

I would imagine consciousness shrinks in the presence of an all-powerful god.