I'm sure this will be downvoted but the fact that the front page of this site features photos of the organizers means to me, this is a promotional movement for these people, not a serious organization. Seeing their faces filling up large portions of the front page means the actual supposed point of their supposed purpose is being subverted for self promotion.
the front page does not feature the organizers, it features links to a video and a seminar, and the seminar and the video happen to feature the speakers. featuring speakers of a seminar is what i expect, because i want to know who is talking.
I guess I shouldn't be snarky - I appreciate the browser vendors claim they are working on getting all major browsers to behave the same. That said, I feel like they might be concentrating on the wrong areas. Like there are some super core areas that need to be covered.
Half a year ago made tiny "draw with pointer" demo. Tested on desktop Chrome/Safari/Firefox and iOS. Turns out it didn't work on Android. I don't have an Android to test on. But, it was literally the most basic pointerevent code. I wasn't doing anything out of the ordinary or near any edge cases.
I feel like seeing people disregard traffic laws fits this topic in some related way. They could be patient, they might arrive at their destination 1-3 minutes slower (or not), but in the moment they choose to break the law and put others at risk.
1. You see others do it and feel compelled not to be taken advantage of
2. You start with small things as escalate
3. You normalize the behavior in one context and then it expands to other context.
This feels like it's following similar patterns of normalization
Even if it's not direct death, which, with at 4000lb car is certainly a possibility, it can indirectly cause severe repercussions. If you ruin someone's car they might not be able to get to work. They lose value in their car even if repaired. Repairs are never 100%. They also have to deal with all the time dealing with the time dealing with accident itself and time dealing with repairs etc. Time they could have spent earning a living or taking care of loved ones.
Yesterday I was at a 1 lane road where there's enough room on the right to squeeze in for a right turn. A driver squeezed to that right turn area on the red. Then on the green they went through the light and illegally passed all other cars. I see this kind of stuff daily.
Another one I see regularly. There's left turn lane with a left turn arrow. The lane to the right of the left turn lane is NOT a left turn lane, yet random drivers turn left from it. It's more common to see them turn left when there's the green turn signal but I've seen them turn left when the left turn signal is red.
Another that escalated over the years is cutting across multiple lanes of traffic and the painted barrier to take a freeway exit at the last second.
Promises should not be a big overhead. If they are, that seems like a bug in JS engines.
At a native level (C++/rust), a Promise is just a closure added to a list of callbacks for the event loop. Yes, if you did 1 per streamed byte then it would be huge but if you're doing 1 promise per megabyte, (1000 per gig), it really shouldn't add up 1% of perf.
In Rust, a Future can have only exactly one listener awaiting it, which means it doesn't need dynamic allocation and looping for an arbitrary number of .then() callbacks. This allows merging a chain of `.await`ed futures into a single state machine. You could get away with awaiting even on every byte.
I'm fairly sure it's not Promises that are actually the heavy part but the `await` keyword as used in the `for await` loop. That's because await tries to preserve the call stack for debugging, making it a relatively high-level expensive construct from a perf perspective where a promise is a relatively low-level cheap one.
So if you're going to flatten everything into one stream then you can't have a for loop implementation that defensively awaits on every step, or else it'll be slooooooooow. That's my proposal for the change to the language is a syntax like
for await? (value of stream) {
}
which would only do the expensive high-level await when the underlying protocol forced it to by returning a promise-valued step.
You can find similar hype articles about the Palm Pilot, then all the neighsayers who said most people wouldn't want and had no need for computer in their pocket. And yet here we are.
It is fun but it's also not universal. While every house and apartment I've lived in in the USA had an oven, the default in Japan is no oven. 1 to 3 burners, and possibly a broiler is the norm.
https://www.microsoft.com/en-us/research/wp-content/uploads/...
reply