There may be a need for additional information, there just isn’t any in these responses. Using a basic JSON schema like the Problem Details RFC provides a standard way to add that information if necessary. Error codes are also often too general to have an application specific meaning. For example, is a “400 bad request” response caused by a malformed payload, a syntactically valid but semantically invalid payload, or what? Hence you put some data in the response body.
This should be done with font ligatures, not replacing character combinations with other characters that can’t be typed normally
I find it a little disturbing that YAML seems to be going nowhere, and appreciating JSON all the more, but it’s still interesting to read
It’s designed as a “data serialization language” but its primary use case seems to be a base syntax for a trillion different DSLs
Why would you need to set up a postgres db…? Unions are a fundamental set theoretic operation that are applicable to all set-like collections. You may as well say “an in memory hash map / list is absurdly inefficient compared to a relational db.” Is it efficient, to you, to spin up a postgres instance to hold a dozen key value pairs?
Sets aren’t just for databases
No, it’s not, because it’s irrevocable
The previous code exists under an irrevocable open source license, so they are entitled to it. Also, fuck off.
bullet_idx
Not true at all, lots of wireless mice with durable optional cables.
No, this is insanity. Mod-tap has an inherent delay. Using it for anything but the most rare operations (like “shutdown”) would drive me crazy. If you can’t reach mod keys, unless you’re arthritic or have otherwise reduced mobility, change your technique instead of doing this.
The only substitution I do is to replace Caps Lock with Super and Super with Escape, plus standard F key mappings when using a <75% and arrow key mappings on 60%.
The analytic continuation of KB(x) to the complex plane subject to a superconvexivity constraint is unique but doesn’t necessarily have a straightforward geometric interpretation
Yes… But ASP.NET Core kept the branding. Thus “Core” still exists, concurrently with the regular “.NET.”
I have no complaints about just calling it .NET. The distinction between .NET and .NET Framework isn’t much of a problem. It’s the fact that .NET and .NET Core aren’t actually different that’s odd. It underwent a name change without really being a different project, meanwhile the Framework -> Core change was actually a new project.
Not an intern, but this week I’ve unraveled some mysteries in ASP.NET MVC 5 (framework 4.8). Poked around the internals for a while, figured out how they work, and built some anti-spaghetti helpers to unravel a nested heap of intermingled C#, JavaScript, and handlebars that made my IDE puke. I emulated the Framework’s design to add a Handlebars templating system that meshes with the MVC model binding, e.g.
@using (var obj = Html.HandlebarsTemplateFor(m => m.MyObject))
{
Name: obj.TemplateFor(o => o.Name)
}
and some more shit to implement variable-length collection editors. I just wish I could show all this to someone in 2008 who might actually find it useful.
It falls under the Azure brand.
Excel is a brand name, Azure Blob Storage is a descriptive title. It’s Azure’s blob storage service.
I really don’t think it’s that bad. The only weird thing is .NET Core becoming just .NET in version 5.
Start a project with a good template and learn by tinkering. Some languages/frameworks have some canonical starter templates (.NET, Phoenix/Elixir) and most others you can find by googling “x boilerplate.”
Status 200 for errors is common for non-REST HTTP APIs. An application error isn’t an HTTP error, the request and response were both handled successfully.