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.
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.
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
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.
This is actually a take most SRE's would / should believe.
Every added 9 to the reliability increases the price exponentially. Finding the correct level of reliability is something most companies should focus more on, because sometimes a single physical machine that could go down once a year for a few hours is perfectly capable of providing all the resources a medium seized business could need. Proper backups, monitoring and recovery runbooks can even decrease the downtime of such a simple system to minutes, while easily saving you maybe thousands per month.
In Dutch companies it’s done by Justis, a separate government agency that basically tells companies if you’re fit to do a certain job.
It’s based on what job you’re going to perform, so people that have money laundering convictions probably are still allowed to volunteer for the local Boy Scouts.
There are several levels and categories and it’s usually returned within a few days.
Is this about the AI or about the use of regular technology that could hurt citizens? Facial recognition and pattern recognition both seem like tech that isn't necessarily AI but are mentioned in the article.
If it's about AI, where is the line? Does reinforcement learning count? What about deep learning? Neural networks? 5 clever if statements?
I don’t think this should surprise anyone. Go is an excellent language for quick prototyping and easy distribution.
The investment to become fluent in Go might literally be an order of magnitude less than becoming fluent in rust.
Rust might be the perfect language in terms of capabilities and safety, but it is far from a simple language.
The function signatures from even some simple methods have become ridiculous. I’ve seen enough examples where it was needed to unpack a value two or three times to get the value you want.
The perfect language probably doesn’t exist, but go is one of the easiest compiled and strongly typed languages to learn. And that in itself is quite an achievement.