8,869 karma · joined November 20, 2016
Good on him for reporting what he saw. He also went to the police the next day and reported it directly. But now the media machine is going to make him regret he ever said anything, which is unfortunate.
To quote Oliver Babish, "In my entire life, I've never found anything charming." Yet I miss Claude's excessive attempts to try.
Docker has security issues if you're not careful, and it's frankly kind of a shitshow out of the box with defaults. Maybe that's part of the reason. But I struggle to see how a bespoke solution like this is the right answer.
The biggest challenge is that they basically have hands. He would climb up the kitchen cabinets, grab a box of cereal, open it up and sit there eating out of it like a toddler.
We only had him for a few months before reintroducing him to the woods behind the house. I've wanted a pet raccoon again ever since.
It's my understanding that building Rust applications still requires a C toolchain, and packages are still going to be dependent on things like having the openssl dev headers/libraries installed. That's fine, that's normal for building software, but it's not as trivial as "just git-clone this Rust source repo and run one command and everything will work".
I'm certain I could get up and running quickly. I'm also certain I'd have to install a bunch of stuff and iterate past multiple roadblocks before I was actually able to build a Rust application. And finally I'm certain I could get Claude or Codex to do it all a lot faster than if I muddled through it myself for half an hour.
I might learn Rust some day. At the moment, I don't need the mental clutter.
I will happily copy-paste this from any source I trust, for the same reason I'll happily install their software any other way.
And while some people might be intimidated by it, it's not a huge lift to make your own images. I don't mean to trivialize it, because it's at best inconvenient, and can be challenging. In many cases it's only a few minutes of work to bundle something up. LLMs are great at this. For a Golang app like Minio, it's a piece of cake, since you don't have to install a zillion dependencies manually.
What Minio is doing wrong here is thinking too highly of themselves. Their product is a fine implementation of S3-compatible object storage. It has some features that make it attractive for selfhosting. It's far from the only solution, though. The harder they make it to use, the more people are going to switch to easier alternatives.
A lot of companies try to lock down their popular open source/free products once they have a large market share. It always backfires.
Hashicorp did this. There's no reason to use Terraform anymore; OpenTofu is a drop-in replacement that is just as good for almost everyone, and all the community support will shift to it such that it will inevitably be far superior to Terraform.
Redis became Valkey. MySQL became MariaDB. OwnCloud became Nextcloud.
There are countless examples. Yeah, the commercial entities continue to exist. For companies that need support and contracts, there will still be a market. But they are destroying their pipeline for new customers. Why would anyone use a closed commercial project with no community contribution when there's a free, open source option that's either a 100% compatible drop-in replacement or a low-effort pivot to a functionally-equivalent solution without vendor lock-in and burdensome restrictions?
Minio is shooting themselves in the foot. Most people don't give a crap what's backing their object storage, so long as it works.
The reason third-party things are in the critical path is because most of the time, they are still more reliable than self-hosting everything; because they're cheaper than anything you can engineer in-house; because no app is an island.
It's been decades since I worked on something that was completely isolated from external integrations. We do the best we can with redundancy, fault tolerance, auto-recovery, and balance that with cost and engineering time.
If you think this is bad, take a look at the uptime of complicated systems that are 100% self-hosted. Without a Fortune 500 level IT staff, you can't beat AWS's uptime.
It really is a single point of failure for the majority of the Internet.
I use Neovim in tmux in a terminal and haven't changed my primary dev environment or tooling in any meaningful way since switching from Vim to Neovim years ago.
I'm still changing code AIs as soon as the next big thing comes out, because you're crippling yourself if you don't.
I just want consistent tooling and I don't want to have to think about what's going on behind the scenes. Make it better. Make it better without me having to do research and pick and figure out what today's latest fashion is. Make it integrate in a generic way, like TLS servers, so that it doesn't matter whether I'm using a CLI or neovim or an IDE, and so that I don't have to constantly switch tooling.
This is a DIY power bank. You can buy professionally-made ones from Bluetti, Jackery, EcoFlow, and many other companies. Including with solar panels. They've been around in some form or another for decades. Modern ones use LiFePO4 batteries, which have a solid safety profile compared to older-generation lithium batteries.
Or you can buy components and build your own, hopefully more safely than the article shows.
Go hang out on r/SolarDIY or check out Will Prowse on YouTube.
There a many problems with this article, but the fact that it includes a battery charger is not one of them.