Overall we're seeing with pixelation and MSCHF's Big Red Boot a reclaiming of video game and cartoon aesthetics where the clothes you purchase feel more like Fortnite "skins", and an attempt to make the real world feel more like the simulation.
511 karma · joined December 14, 2012
Overall we're seeing with pixelation and MSCHF's Big Red Boot a reclaiming of video game and cartoon aesthetics where the clothes you purchase feel more like Fortnite "skins", and an attempt to make the real world feel more like the simulation.
Originally from Airbnb. Very powerful and flexible OS frontend BI tool
And, as another commenter noted, also for cities design. There are actually a few versions of this: I worked on one called Delve https://www.sidewalklabs.com/products/delve
Typically they use constraints optimization or wave function collapse under the hood, on top of some sort of procedural generation pipeline. A few others are Spacemaker, Hypar, and Testfit.
It may work near a major avenue or political boundary or an event like a parade where there are "dispatch walls" set up or where there are two city areas that meet - think Reno / Tahoe.
Look at Amazon's facial recognition, for instance. OpenCV and the like have existed for years but by tightly integrating with AWS, we've now unlocked brand new use cases and customer bases -- say, startups and researchers on one hand and police departments and authoritarian governments on the other. The pool of qualified developers, and by definition number of developers who might be willing to implement a facial recognition database for dissidents, goes up significantly as the technology becomes easier to use.
For a map data format, you might make life easier for people drilling wells in remote rural villages, but you might also be designing a data format for bomb strikes.
Also take a look at Streetscape.gl [2] which is designed for visualizing AV data
Disclaimer: I work on Uber's data vis team but not on AVs.
[0] https://streamlit.io/docs/api.html#streamlit.deck_gl_chart [1] https://deck.gl/#/documentation/deckgl-api-reference/layers/... [2] https://avs.auto/
The crux of the problem is that visualizing uncertainty is hard (remember the NYT 2016 election needles?) especially in a geospatial context where screen X and Y are meaningful. Animation can certainly help but interaction is even better.
No issues came up but I've since felt vindicated in doing a close reading of anything more important than an EULA.
I think this is a classic case of the Innovator's Dilemma: you start by making something worse than existing products on the market but that completely address the features your customers care about most. Eventually your customers demand more features and you have to turn a profit, so the product gets bloated and the p90 experience suffers.
To your point, I think we shouldn't be shaming people for a bad commit, but we should help the next coder (or myself 6 months down the line) find the issue and solve a bug in as little time and with as little headache as possible.
That said, I tried to create a demo application and it seems like the require / exports / global situation isn't 100% yet. Any tips from the team on what to do here?
I'm currently working on a JS-powered geospatial exploration app that is meant to be run either standalone or embedded into a Jupyter notebook. We often run into questions around how much the embeddable app should be scriptable or how much user control to allow. This would seemingly solve many of our needs.
Mike, Jeremy, and Tom, this looks awesome. I'm looking forward to put it through the paces.
Baku is full of me-too projects like the 2nd tallest flagpole in the world (behind Tajikistan and now Saudi Arabia), the flame towers (one of which was broken to the point of uninhabitable) and the mentioned Khazar Islands which build off the concept of Dubai's Palm Islands but nobody seems to want.
The sad thing is there is actual amazing culture and interesting architecture in Azerbaijan. But the modern stuff is just atrocious.
https://en.m.wikipedia.org/wiki/Hispanic–Latino_naming_dispu...