It might not be a feature, but it is a selling point. It conveys that it was written relatively recently, is more likely to support modern features in the shell, runs reasonably fast and is reasonably portable.
If it was written in JS or python I'd already start worrying about what package manager to install it with in which environment, installing it globally is an anti pattern but symlinking it to .local/bin might complicate it.
So IMHO, the language something is written in is not just an implementation detail, it informs me in how well it will perform.
It's a prompt. Writing anything for that purpose is code gardening, but hey it's in rust so I'm supposed to be excited?
That, in essence is the problem "X in rust" normally means "I've written something of low value IN RUST. Gimmee upvotes". Come back when the project is interesting regardless of the language.
GDO: Garage door Opener, a passkey enabled web interface to trigger opening my garage door. It's basically just a 2 button website, 1 button opens and closes the door with a delay, the other just opens/closes the door.
It uses a passkey auth proxy which allows me to toggle user access.
They could easily make the device accept 10 or even 20 devices at a time, with a simple LED on for each indication progress. Just check up once an hour and move done iPhones to the done stack and place todo iPhones in the device. Set it up on route to the toilet or next to the coffee machine and it's next to effortless.
It can be embedded in a program, but it doesn't automatically manage devices on a tailnet; i.e. there's no way to add all users of an app to the same tailnet (they have to explicitly create a Tailscale account and sign in and share and join) - AFAIK.
If only that was true, the only way to remain cloud agnostic seems to be to use Kubernetes and some kind of managed sql database. Once you factor in some things like pubsub, SNS, dynamodb or firebase you quickly lock yourself in. Running the same server less application across clouds gets even more complicated
Anyone who thinks that using K8s and running everything on your own makes “cloud agnosticism” realistic has never dealt with large scale migrations and the institutional complexity behind it. (Yes I’m agreeing with you)
Yes I work for AWS Professional Services now. But I’ve seen the same with Azure and on prem in previous jobs. It hardly ever makes business sense not to go all in on whatever your infrastructure decisions are.
I'd say most of these patterns are supported by NATS, it can do pub/sub but actually also has excellent support for RPC and in the latest iteration it also has a KV store baked in. I've been using it for a few pet projects so far and it has never been the weakest link.
Words and their usage change over time. The cloud has become a term for a place where you can easily rent compute power, in some way or another. That ease of use (you just provide your credit card, click a few times and you get a VM) has become synonymous with the cloud, now package that all up for private use within a company and you have a private cloud, perfectly sensible.
It's not about misleading you, it feels more like they have a definition in their general use you don't agree with. And I hate to bring it to you, but don't expect those meanings to change to what you think it should be.
The origin of the word television is that you see (vision) something that is far (tele). But you can also use it to see stuff that is near, or games, or use it as a screen to read a book. It's still called a television though.
