I appreciate the “carrot with a bit out of it” icon.
I appreciate the “carrot with a bit out of it” icon.
If you’re interested in detail, I can recommend this book: https://play.google.com/store/books/details?id=ncGVPtoZPHcC.
I think the big reasons for most people boil down to one or both of two things:
A) People having 0 trust in Google. I.E. people do not believe that paying for their services will exempt them from being exploited, so what’s the point?
B) YouTube’s treatment of its content creators. Which are what people actually come to YouTube for. Advertisers and copyright holders (and copyright trolls) get first-class treatment, while the majority of content creators get little to no support for anything.
Because Nintendo made one. They published the “official” timeline like a decade ago, and then made a TON of references to it in Breath of the Wild. Not our fault they then decided to shit on it with Tears of the Kingdom.
I mean, I’m paraphrasing, too.
Even better quote, I love using this one.
“So, with AI writing code for us, all we need is an unambiguous way to define, what all our business requirements are for the software, what all the edge cases are, and how it should handle them.”
“We in the industry call that ‘code.’”
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.
They took the genre and distilled it down to the purest gameplay-focused form that they could. And for an Early Access title, it could absolutely be a full release today. No bugs, no performance issues, nothing feels missing or incomplete, except maybe a few minor QoL bits. The success is deserved.
Yeah, you need a way to specify what you want with a high degree of both flexibility and specificity. We have a term for that in the industry, it’s called “writing code”.
The hell does “single-capacity” mean here? The article doesn’t specify.
My god, this speaks to me.
Is it just me, or does this seem like a reasonable solution? Assuming it’s technically feasible.
Don’t take this the wrong way, but this made me bust out laughing…
When you hold stock, don’t you need to sell it/liquidate it in order to make money?
Boy, if that isn’t just a perfect example of the perversion of our economic system. “You can’t make ACTUAL money with it, you can only make money by participating the meta gambling game.”
No, stock entitles you to dividends, which is just a fancy way of saying “a share of the profits”. Like, a company brings in A amount of money (gross income) in a year, spends B of that on payroll and whatnot (expenses), maybe puts away C of that into a savings or spending account, and everything that’s left, D, gets given to the owners. If you have stock in the company, that’s you.
Of course, dividends are generally very small (like, think savings interest) compared to what you can make trading and speculating, so it’s never good enough for the rich.
It’s also rather common for companies to pay no dividends, because they just put all the leftover money into C. Which isn’t even necessarily bad, it’s generally built on the idea that keeping the money in the company will give the company more room for growth, I.E. raising the stock price, with the assumption that that will be worth more than the dividends may have been. But for so many companies, that just never ends. Sooner or later, the growth won’t be sustainable, and many companies just collapse under their own weight, leaving the stock worthless.
Shit, this is a cool idea. I might have to steal this.
That inserter issue has been annoying for so long.
Let’s say it’s a cipher, but with a twist.
For one, Ōkami was supposed to have a bigger story, but the team ran out of time and ended midway through what Kamiya wanted to do.
WHAT?! The game’s campaign is already obnoxiously long.
First game I ever played where I was like “yo, I actively WANT to do the speedrun achievement, and the deathless achievement.” So, first game where I ever did those things. Maybe I’m just crazy, but I found them way easier than I expected.
Also, a prime example of storytelling through music.