They even had a post about it, too: https://stripe.com/blog/globe
Still, given that the "form" is well established, it is always interesting to me at least to see how they chose to represent the data. When Blekko was running Bryn Dole had done a visualization based on this theme were query requests were highlighted as streams from their point of origin (more queries, taller stream as I recall).
FWIW I'm currently running a Twitter poll to see whose globe people like better. 8 hours in the votes are running 60% Github, 40% Stripe:
I'm also not forgetting Microsoft's checkered history with open source, or their current deals with government agencies like ICE and the DoD.
* I'm not saying they didn't build it themselves. For companies like Microsoft/GitHub, the design is the hard part and paying engineers is easy.
I also don’t think the ICE and DoD deals are relevant here at all (or to any of Microsofts’s other products)
Combine these two Wargames movie posters:
Globe: https://www.traileraddict.com/wargames/poster/1
Tracking: https://www.pinterest.com.au/pin/216876538281839025/
But sure.. it's all a MS conspiracy to steal credit.
I think the combination of timezone and language settings would work for the obviously problematic cases (eg, Australia vs Japan/China/Asia, and South vs North America. Africa is still a problem though.)
One thing I hadn't known about before was Github Discussions (beta): https://github.com/home#home-community
It's still a heavy thing to add to any page IMO. Which shouldn't be downplayed.
But it is very neat and I still like it.
They optimized for hitting 60fps without any concern for the resources they were using as long as it fit in that budget
I agree that using this amount of resources in the browsers of visitors shouldn't be taken lightly (they could be on battery for example).
Please scroll down to where the globe image appears and click/tap it. Feel free to switch countries and click around. I would love to hear your feedback.
PS: We have open sourced all this stuff, so if anyone here wants to put a globe on their website, just load our Q.js from https://github.com/Qbix/Platform and then render the Q/globe tool and Places/countries selector tool with your own options. Unlike the GitHub globe, you can also have users click on countries in the globe to select them, and if you need you can pull in the flags, languages and all the other stuff per country.
Some kind of chernobyl event, possibly caused by the ICBMs in the globe image?
What is the octocat standing on top of? Abandoned silo? Or live silo about to go hot?
1: https://sma.nasa.gov/sma-disciplines/planetary-protection
(Full disclosure: I ported a prototype version of my company's globe data viz in 2013 using Three.js - it's terrific! Those folks are the real heroes in this story.)
Clearly the USA is more active during the day, as is India and Europe. Brazil on the other hand is backwards. Anyone know why that would be? I’ve worked with Brazilians before during the day so that struck me as really peculiar.
I recall Stripe's globe was built using that.
To answer your question, the failIfMajorPerformanceCaveat flag allows sites to turn off their hardware accelerated features when hardware acceleration is off.
A recent thread that turned out to be a lightdm bug: https://www.reddit.com/r/archlinux/comments/kl9map/cant_run_...
This sounded like a joke, but I wasn't 100% sure.
It's a real thing (code from Stack Overflow):
const context = canvas.getContext("webgl", {
failIfMajorPerformanceCaveat: true,
});
* Woefully ambiguous and underspecified - what is "major"? A 12 FPS drop compared to desktop? Below 30 FPS? Frame jitter outside a certain standard deviation? It will depend on the app (fast-paced frame-perfect game vs. "well I just want the animation to be smooth" necessarily have different requirements for performance), but this flag leaves it up to the browser to decide.
* Oh, it's meant as a general term for checking whether software acceleration and frame readback (and other yet unknown possible bottlenecks) are engaged, those are the "performance caveats" - but those are either "yes" or "no", there's no way to quantify that with "major", totally meaningless. Unless it's conditionally choosing to succeed even with software rendering if some unspecified performance threshold is met. The 2 sentences of documentation about this flag means I wouldn't know.
* If you Google the name of the flag, near the bottom of the first page you'll find an email thread where someone brought up points like this and was ultimately shot down and the flag pushed through because "the Maps team really needs this." The technical equivalent of legislating from the bench. I wish I could create new browser features to solve all my inconveniences too. Why the Maps team couldn't figure out how to measure the canvas FPS and degrade on their own is a mystery to me.
* To round it all out, the name is also really bad. "failIfMajorPerformanceCaveat" is a weird negative tense - why not "requireUnhinderedPerformance"? That's consistent with the universal standard of "require" (not "failIf", how goofy) and is a lot clearer about the supposed intention of the flag (to try to ensure performance similar to native GL rather than this ambiguous "performance caveats" thing).
Sorry, just a rant about shovelware in the browser stack.
I've also tried to visualise worldwide COVID data on that globe, however performance degrades making it completely unusable.
looks so cool
I wonder if I'm just odd, or if people not realizing it's interactive is widespread.
Of course part of the art is that it is real time (ish). That may be harder to do with video. (But I guess it could be a live stream)
It's a common gotcha when embedding Google maps on mobile.
Here's a mobile capture for reference https://files.catbox.moe/e965m9.mp4