It's the capability of a program to "reflect" upon itself, I.E. to inspect and understand its own code.
As an example, In C# you can write a class...
cs
public class MyClass
{
public void MyMethod()
{
...
}
}
...and you can create an instance of it, and use it, like this...
cs
var myClass = new MyClass();
myClass.MyMethod();
Simple enough, nothing we haven't all seen before.
But you can do the same thing with reflection, as such...
cs
var type = System.Reflection.Assembly.GetExecutingAssembly()
.GetType("MyClass");
var constructor = type.GetConstructor(Array.Empty<Type>());
var instance = constructor.Invoke(Array.Empty<Object>());
var method = type.GetMethod("MyMethod");
var delegate = method.CreateDelegate(typeof(Action), instance);
delegate.DynamicInvoke(Array.Empty<object>());
Obnoxious and verbose and tossing basically all type safety out the window, but it does enable some pretty crazy interesting things. Like self-discovery and dynamic loading of plugins, or self-configuration of apps. Also often useful when messing with generics. I could dig up some practical use-cases, if you're curious.
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.
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.
What the actual fuck is this? A constitution neither defines nor repeals laws, it defines rights and powers, of the citizenry, and the government. Is there just more to the story that the article isn't covering?
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.
"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."
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.
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.
Anyone else this there's actually nothing at all wrong with the "New" row of icons? Except for the triangle one, which is terrible in its "Original" version as well, as it indicates absolutely nothing about its app (I believe it's Google Drive, right?). All the rest are clearly distinguishable, and have relevance to what the app does.
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".
Slight distinction, though maybe not so much a practical one: it was more "Don't do that with our weapons, Russia will get mad at us, instead of just you."
It's not that he has to have a residence in New York, it's that the address that he listed as his residence, in New York, on the application for candidacy submitted to New York, isn't really his residence. The article mentions other states may follow suit with the applications he submitted to them.
It's the capability of a program to "reflect" upon itself, I.E. to inspect and understand its own code.
As an example, In C# you can write a class...
public class MyClass { public void MyMethod() { ... } }...and you can create an instance of it, and use it, like this...
var myClass = new MyClass(); myClass.MyMethod();Simple enough, nothing we haven't all seen before.
But you can do the same thing with reflection, as such...
var type = System.Reflection.Assembly.GetExecutingAssembly() .GetType("MyClass"); var constructor = type.GetConstructor(Array.Empty<Type>()); var instance = constructor.Invoke(Array.Empty<Object>()); var method = type.GetMethod("MyMethod"); var delegate = method.CreateDelegate(typeof(Action), instance); delegate.DynamicInvoke(Array.Empty<object>());Obnoxious and verbose and tossing basically all type safety out the window, but it does enable some pretty crazy interesting things. Like self-discovery and dynamic loading of plugins, or self-configuration of apps. Also often useful when messing with generics. I could dig up some practical use-cases, if you're curious.