I mean, REST-ful JSON APIs can be perfectly type-safe, if their developers actually take care to make them that way. And the self-descriptive nature of JSON is arguably a benefit in really large public-facing APIs. But yeah, gRPC forces a certain amount of type-safety and version control, and gRPC with protobuf is SUCH a pleasure to work with.
Give it time, though, it’s definitely gaining traction.
#4 for me.
Proper HTTP Status code for semantic identification. Duplicating that in the response body would be silly.
User-friendly “message” value for the lazy, who just wanna toss that up to the user. Also, ideally, this would be what a dev looks at in logs for troubelshooting.
Tightly-controlled unqiue identifier “code” for the error, allowing consumers to build their own contextual error handling or reporting on top of this system. Also, allows for more-detailed types of errors to be identified and given specific handling and recovery logic, beyond just the status code. Like, sure, there’s probably not gonna be multiple sub-types of 403 error, but there may be a bunch of different useful sub-types for a 400 on a form submission.
My god, this speaks to me.
That inserter issue has been annoying for so long.
A man should get violent and angry and protective when someone hits on his woman.
I’ve had a lot of success with this guy.
https://www.liito-kala.com/page92?product_id=6&brd=1
Supports a variety of different battery sizes, can charge at different rates, goves voltage readouts, and can run full capacity tests.
I was originally only looking for an 18650 charger, but I got way more than I bargained for.
Lol, no. I have family members that actively called him a n****r while he was in office.
Main difference there being that switching cities means probably switching ISPs. You can absolutely carry over your IP address when you move between the same provider, if that’s part of your service plan, and that may well happen with some ISPs even without it being part of your plan. There just isn’t really much of a need for people to carry a static IP, except for some businesses, and I’d say the main reason is that people don’t visit websites by memorizing and typing in an IP. They do memorize and type in phone numbers.
They do, it’s called an IP address.
Phones get numbers assigned to them by a cell service provider, in order to communicate on their network, which is basically the exact process for computers and IP addresses.
If you’re asking about the equivalent of like a SIM card, in the computer/internet world, that’s handled at higher layers, by digital certificates. And again, the process is almost exactly the same, except they don’t (usually) get put on physical chips.
MLB 66
You mention Bally and baseball, mlb66 was my go-to last year.
Generally speaking, fault protection schemes need only account for one fault at a time, unless you’re a really large business, or some other entity with extra-stringent data protection requirements.
RAID protects against drive failure faults. Backups protect against drive failure faults as well, but also things like accidental deletions or overwrites of data.
In order for RAID on backups to make sense, when you already have RAID on your main storage, you’d have to consider drive failures and other data loss to be likely to occur simultaneously. I.E. RAID on your backups only protects you from drive failure occurring WHILE you’re trying to restore a backup. Or maybe more generally, WHILE that backup is in use, say, if you have a legal requirement that you must keep a history of all your data for X years or something (I would argue data like this shouldn’t be classified as backups, though).
Why the hell is a professional tech business not relying almost-exclusively in ethernet, anyway?
Discord gained popularity and maintains it, in spite of the many reasons to avoid it, because of usability and feature richness. Slack, Teams, Matrix, Telegram, they are miles ahead of everyone else in the live-chat space, when it comes to user experience.
This was an interesting article about some tech I’ve never heard of before, but it has little to nothing to do with Discord’s overall success.
In addition to everything else mentioned, in your scenario, you would also need to pull 2 neutrons from somewhere. A helium nucleus has 2 protons and 2 neutrons, but each H nucleus (generally) is just 1 proton. The 2 neutrons are critical in holding nuclei together.
rsync, for sure. That’s what I used when I had to migrate a 10TB datastore to a new machins.
I don’t. I don’t think you can grow to that kinda size without engaging in growth and profit chasing. We don’t need a Blizzard that behaves like Larian, we need lots of Larians.
Off the top of my head, it would be getting a Super Nintendo for Christmas and thinking my parents must’ve sold the car to pay for it.
A DNS Proxy/Forwarder server? That’s where you would configure how your .internal domain resolves to IPs on your internal network. Machines inside the network make their DNS queries to that server, which either serves them from cache, or from the local mappings, for forwards them off to a public/ISP server.
Practice getting up in response to your alarm.
Seriously.
Once or twice a day, in the middle of the day, go lay down in bed, like you’re going to sleep, and set your alarm for maybe 5-10 minutes. The moment it goes off, shut it off and stand up. Teach your body the habit of standing up, immediately, in response to the alarm. So long as you’re getting enough sleep, you’ll start doing it in the morning, on reflex.