241 karma · joined March 22, 2020
I’m feeling attacked. Here I was thinking my lifelong work of self sufficiency for my family was completely reasonable until you came along. Thanks a lot!
Every time I try to migrate my very large bookmark collection to another browser, it either misbehaves and partially loses some data or fails completely.
That waterway is flowing directly into the ocean, and upstream from a fishing village.
Consider the case of a team of people collaborating on a software stack - the prototypical use case includes Docker Compose at the simplest and a full K8s stack at the extreme. There is quite often a minimum of 3 containers here; frontend, API/Backend and a database server. If you start to add observability tools, async/batch/event execution, caching, automated integration testing, etc, the number of "layers" in the stack grows quickly. In addition, each component may have unique per-environment or even per-user customizations.
Often one ore two people will manage the stack itself and provide instructions on how to get the whole thing working for others using a specific defined selection of easy to use tools that essentially offer minimal prerequisite knowledge to use
"Install X, run Y, get to work."
It saves a lot of time for the intern on the UI team who just wants to add a component to one page and test it locally and not also have to learn how to deploy the entire stack from scratch.
I'm doubtful you meant what you wrote here. Using a readymade UI or API to perform an effectively magical task (for most of us) is an entirely different paradigm to "just train your own model."
In reality, for us non-ML model training mortals, we're actually probably better off hiring a human to do basic data entry.
"The simplest explanation is usually the best one."
Conspiracy theories are a logical reasoning black hole.
I personally feel it's generally best to avoid the mental Spaghettification.
I mean, who puts Verbs-InCommandNames? No one who wants to actually remember all of their CLI tools. That's who.
/shiverBut...
> Annoyingly, I host my blog on GitHub pages, which doesn’t support Brotli.
Is the glaringly obvious solution to this not as obvious as I think it is?
TFA went through a lot of round-about work to get (some) Brotli compression. Very impressive Yak Shave!
If you're married to the idea of a Git-based automatically published web site, you could at least replicate your code and site to Gitlab Pages, which has supported precompressed Brotli since 2019. Or use one of Cloudflare's free tier services. There's a variety of ways to solve this problem before the first byte is sent to the client.
Far too much of the world's source code already depends exclusively on Github. I find it distasteful to also have the small web do the same while blindly accepting an inferior experience and worse technology.
I basically need a very basic script interpreter.
The problem you're describing goes far beyond the build system. You're looking for a cross platform shell.It's far less great when working with anything else, like Go, Python, JS/TS, etc.
People want great tools that work well with the way their software and teams work. Seems logical to me.
After all, someone reinvented the build system when they created make to solve the problems of their time. What if they just stuck with csh or plain POSIX compatible build scripts?
Magic!
A simplistic example, if a given node was limited to 16GB of RAM 20 years ago, I would need 256 nodes to have 4TB of RAM for my system (not including overhead for each OS).
Compared to today, where a single node can have that entire 4TB all in one chassis.
The total cost of RAM chips themselves may not have changed, but the actual cost of using that RAM in a physical system has dropped dramatically.
Just FYI, you are (perhaps unintentionally) showing your lack of experience.
There are many thousands of brilliant engineers for every brilliant engineer who also is a author/speaker/publisher. These are very different skills.
Also, perhaps the author _is_ the next Martin Fowler? You never know...
BP monitoring requires a pressurized cuff which restricts (stops) arterial flow. The readings are the pressure of the cuff as it deflates when the blood starts flowing and when it can no longer be detected.
Plus, it's open source and the developer continues to improve it, so many years later.