1,394 karma · joined March 22, 2014
Now what we really need is a functional dialect which compiles to TypeScript...
If a save is complete, that dot will go away. If there is no dot, the file is unmodified.
GET, for example, is an idempotent method [1], which means "the intended effect on the server of multiple identical requests with that method is the same as the effect for a single such request."
However, it is NOT true that sending the same GET request at different points in time would have the same effect - if a resource is deleted or moved, you might get a 404, 301 or 200 where previously you got something else.
When idempotence is talked about in these RFCs there's an implied caveat that the "multiple requests" they talk about happen at the same time, under the same network conditions. I think that's what they mean by "identical".
[1] https://datatracker.ietf.org/doc/html/rfc7231#section-4.2.2
Potentially, but not necessarily. It's possible also that if there is only one close match for the logic required, it may produce verbatim something it's already seen. GPT is known to do this for sufficiently precise inputs.
> I have a lot of open source code that I love to share for things like education or private stuff, but if you want to use it for something real, you need to hire me.
implies that they have code which they are sharing under that proviso. Do you read it differently?
You are right about the technical distinction of open source from source-available. I think that the GGP (and myself) were both using it colloquially as a shorthand for source-available.
The most obvious one that springs to mind is Traffic Manager, which allows you to go in and change the direction of any individual turning lane to maximise throughput and efficient road usage.
For examples, see https://haxeflixel.com/documentation/loading-the-tilemap/ .
Of course it is. What does regulation do if not prevent an undesirable class of actions?
For what it's worth, I live in the UK which has similar woes to how you describe Canada's two-party system. However we do normally get seen quickly for things which are a threat to life---but elective operations can take much longer. Mental health issues are also dealt with sluggishly at best.
> If you get hand wavy and tell me its too complicated [...]
Unfortunately, it really is too complicated. A doctorate in economics might get you a decent way towards understanding the good that taxation provides, but given that economists still have differences of opinion, maybe not a complete understanding.
[^0]: Well it is, but only a tiny proportion.
Because the externalities are not always visible, and people do not have enough free bandwidth to spend the time understanding them.
In most programming languages, the pain points they describe are real - how do we know that a program will give back exactly what we put in?
The answer is to provide it with an appropriately restrictive type such that any output is necessarily of the right shape. Types allow us to do this exact kind of "offloading", so that we simply trust the compiler to know when we are plumbing things together correctly.
Language purity is really helpful with trusting that a piece of code does what it says it does, and nothing else. If our language is impure then the scope of any given function is essentially unbounded. With purity, it can only perform computations based on the things that are locally available to it, and that severely bounds the amount of leeway a programmer has in its implementation - and hence the number of ways things can go wrong.
In short, an effective, ergonomic, statically-typed programming language can solve most or all of the author's woes. I hope they find one that fits their needs.
It seems a bit odd to offer per-category leaderboards only, especially on the front page, especially if it's going to randomise which one to show with only minimal feedback that it's doing that.
Is that the only thing anyone makes any more? Surely there have to be some actual products in the world to be marketed?
I normally wouldn't bring this up but the article is very specifically talking about the benefits of using this web framework, so it seems apropos.
A protocol should never, never, ever be defined in any way by its implementations. The entire purpose of a protocol is to abstract away the common interface such that it is entirely implementation-agnostic.
Indeed, you might say that a protocol prescribes exactly the intersection of all implementations.
Are you labouring under the misapprehension that there were no civil rights leaders before the 1950s, and this was not exactly what happened to them?