Ooh, well that’s wonderful. It’s like some grassroots thing. The inventors of the thing refuse to support it, but the people are adopting it on their own. ✊ I’m happy to hear these “news” (to me)! ❤️
Ooh, well that’s wonderful. It’s like some grassroots thing. The inventors of the thing refuse to support it, but the people are adopting it on their own. ✊ I’m happy to hear these “news” (to me)! ❤️
I mean, it’s still insignificant enough that it won’t matter yet, right?
But that’s still good. It’s on the right path. Google needs to get their head out of their ass on this one. Still no sign of it years later though.
“Apple” supports it? Which apps? Not that I care much, I have zero Apple products or devices. 👍
Are we JPEG XL yet?
Wow, I just saw this literally two posts above this one.
Haven’t heard of JPEG XL pretty much since it died. And now twice in a few minutes.
Thank you, universe.
Completely off-topic: I really enjoy the way you express yourself. Do you write a lot? Your text is just very easily consumable, yet not dumbed-down.
And now to make lighter EVs that don’t wear on the road so much.
I thought IIFE’s usually looked like (function (...params) {})(...args)
. That’s not the latest way? To be honest I never used them much, at least not after arrow functions arrived.
lol, you’d really have to go out of your way in this scenario. First implement a way to get every single permutation of a list, then to ahead with the asinine solution. 😆 But yes, nice one! Your imagination is impressive.
So there’s yet another level of quirkery to this bullshit then, it seems. 😆 Nice digging! 🤝
I also noticed that if you surround the curlies with parentheses, you get the same again:
> eval('{} + []')
0
> eval('({}) + []')
'[object Object]'
I guess, yeah, that’ll do it. Although that’d probably be yet one or a few extra factors involving n.
In node, I get the same result in both cases. "[object Object]"
It’s calling the toString()
method on both of them, which in the array case is the same as calling .join(",")
on the array. For an empty array, that results in an empty string added to "[object Object]"
at either end in the respective case in the picture.
Not sure how we’d get 0 though. Anybody know an implementation that does that? Browsers do that maybe? Which way is spec compliant? Number([])
is 0, and I think maybe it’s in the spec that the algorithm for type coercion includes an initial attempt to convert to Number before falling back to toString()
? I dunno, this is all off the top of my head.
My mental model of it is a chain, yes. But you can define it however you like. It’s just steps in some direction.
Maybe a cake would suit someone the best.
Well that’s good… 😳
Exactly. For every level of abstraction, the abstractor is the high level and the abstractee is the lower level. Those aren’t real words perhaps, but you get what I’m saying. It’s all relative along the chain of abstraction.
How in the hell does anyone f— up so bad they get O(n!²)? 🤯 That’s an insanely quickly-growing graph.
Curious what the purpose of that algorithm would have been. 😅
Not American here, but… you still get the joke, right?
I just ordered a Gan 3x3… I’m a beginner… Long way to go to beat this robot. 💀🙃
Are you saying they can’t fire a priest for being Muslim? More that is interesting. 😁
Very good points. 👌