Viewing profile — explaininjs

Verizon after 60GB is 600kbps on 5G/4G but up to 3Mbps on UWB. Pretty reasonable IMO. It’s AT&T that’s the holdout, 128k regardless of plan, after 60GB.

I did in fact follow the link. I actually went further than you, all the way to the GitHub, where I saw that it was actually just a web app. All TS. And you can 100% load PWAs offl…

That’s a web app, it’s on them if they don’t want to offer their services without requiring me to let them out of the web sandbox.

As someone who does a ton of networking/routing at the link layer for a day job, I can definitely see why they’re taking measures to reduce bandwidth hogs - to the extent I might a…

Curious what you want from a jailbreak at this point? It seems all of the old things that were actually helpful have found them into first party software, or at least in the sancti…

I should not need to explain to you that the problem is when b itself is internally an (m b’). Or when it is a sum of many types, of varying m-nests. I can assure you that JS libra…

This is all besides the root topic though, which is that CPS and Monads are isomorphic. Which is true. Promises are a different thing.

We might consider promises “applied monads” or “engineered monads”. Monodic in inspiration and they solve the same core problem, but they aren’t straightjacketed into the ivory tow…

There is one particular edge case in which they do not satisfy the laws. That happens to make them much more practical in day to day coding than a strict interpretation would be.

If you’re fine with manually checking a standard interface to see if you should abort, JS’s answer is the AbortController. This is supported by features like the “fetch” function f…

Show me a JS library that allows you to swap a non-async call for an async one in a non-async context^ and I’ll eat my hat. ^Without any non-local changes, obviously.

No… I fear you’ve missed the entire point of the matter, which is that async/await requires that you must go all the way up the call stack explicitly “await”ing things when you hav…

No… that’s the whole point. If you change them to be async, the language forces you to go and rethink what implications that has for the callers. This is a good thing, dumbly seque…

That sounds a lot like async/await. Any errors thrown in an async context bubble to the callsite awaiting it.

Indeed. And breakpoints and stepping across concurrent context actually works in JS, which is nice.

Yes. That blog has probably done more to negatively impact the industry than any other written work I know.

F# first actually. Then C#. Then Haskell. Then Python. Then TypeScript. Parent just has an axe to grind.

Coming from a heavy TS background into a go-forward company, I’d say the main thing you get with async is it makes it incredibly obvious when computation can be performed non-seque…

> You basically have to give up on the idea of ever having any real evidence for one thing over another Exactly. We agree. > best explanations we could find We have no tested expla…

That is the belief that leads to evolutionism, not the exact definition of evolutionism. A necessary precondition. I don’t have time to explain basic mathematics. Suffice to say, t…

The evidence is clear to anyone with eyes: the intricately designed statue. It should be obvious to anyone that it was created, as it was for millennia across the entire world. It’…

Why are you assigning malice? Just because the omnipresent being designed things a particular way but wishes to be known on faith rather than an explicit name tag doesn’t mean he’s…

Go on then, explain this nondifferentiable constant case I was missing.

> people will notice What does this mean? People who don’t know what they’re talking about will get their feathers all ruffled and start rambling about missing the case of nondiffe…

It would seem we are in agreement. Your science cannot find the designer if the designer does not wish to be found by your science. That doesn’t mean we can say they do or do not e…