Steps are not clear enough. It looks to me it's a step by step guide but it missed at least 2 points :
- the search engine must be Google I think ? Mine is duckduckgo and it doesnot work
- I still dont know if my device is supposed to be in airplane mode or no for the test. In airplane mode, even with Google set as the search engine, it does not work. Pixel phone. If I am connected to internet, I do have the single result from the google search.
I guess we are expected to be pleasantly surprised by something, but since I don't know what to look for and it does not work, it's a miss for me.
Personally I prefer to have the explanation alongside the steps that way I know what I am doing and can correctly interpret the instructions. For me, learning the technical trick does not diminish my contentness.
Thanks for the detailed feedback — really appreciate it!
You're right that the demo relies on Google Search specifically (not DuckDuckGo), and that should probably be made even clearer in the instructions. I do mention “search Google” in step 3, but I’ll look into making that more explicit up front.
As for airplane mode: the idea is to go offline after Google has had time to prefetch the page. That’s why the instructions say to start with a stable internet connection — and the page does show a warning if you go offline too early. But I totally get how that could still be confusing, especially if it didn’t work the first time.
A tip: once you're on the "You're offline" page, wait at least 3 seconds and observe the dinosaur. Something may happen.
And good point about wanting to know what’s going on. I tried to keep the experience surprising for some users, but I see how having the technical context up front can enhance it for others. I’ll consider adding an “explain first” option in the future.
The Quest's Snapdragon GPU, like most mobile GPUs, uses a tiled rendering [1] architecture.
The basic technique for rendering gaussian splats is kryptonite for this architecture, essentially implementing every worse practice for rendering on a mobile GPU:
* Tons of overdraw (overlapping splats)
* Tons of alpha blending
* Millions of splats in the distance generate a lot of tiny triangles resolving to a single pixel
* Long thin splats in the foreground generate triangles that cover multiple tiles
These are all the ingredients you need to bring a mobile GPU to its knees! Any desktop GPU (including most laptops) will be far less sensitive to these issues, even if it's not very powerful. It's a fundamental issue of architecture rather than one of raw FLOPs.
The quest is underpowered (it's basically a midrange Android phone you wear.) More efficient coding or a simpler model would help. Inside the Scaniverse does something similar with a high framerate but the models are simple and don't look very good.
I had to power cycle mine to get out, but boy was the view great despite the motion sickness.
no much advice i can provide from the other side of the ocean but good luck to you and start looking for a job now to have money coming in sooner.
Any litigations will take time and not sure there is money anyway.
I remember reading about Xerox people forecasting the smartphones and tablets. We have a picture of their brainstorming and they used small pages to model a handheld computer.
Science fiction was and still is full of more and more integrated computer with human.
Technology is driven by imagination more often than not.
Also, the visualization let you think that all the leftmost teenagers are the same ones stacking the bad things. That might be true, but I doubt it is. The part around Highschool was especially unclear.
Are they the same teenagers getting all the bad stuff. That would be plausible but not to the extend the visual displays I guess.
In other news, I hate that trend of scrolling to animate to get content.
india has many languages and many state languages are unique to the state...
if i speak my state's language - highly likely i don't speak language of the neighboring state, but OP painted india with one broad brush
As said before about in the post "BIG DATA is just data", a lot of information is worthless after 1 or 2 years and most after 5 years. Long term value data seems to be stored in IT systems' DBs rather successfully.
And I have so far always find important emails (notably because important topics are easily found emails chains and far more often than not in the dedicated meeting report).
Structuring data is cultural so you should rather learn to use the system used by your organization. Only super small teams and solo-founders need to think about how to store data. Most workers should follow their community to let other people find the information.
Folders, drawer, cabinet have been around for 3 centuries at least and imho, we are not gonna reinvent the wheel with this or that way to structure information.
If your organization has a system, by all means use it.
The whole point of Johnny.Decimal is that most organizations have absolutely no system to organize information. It’s tossed into a huge pile.
Even organizations that have systems concern themselves only with organization-wide needs. Individuals still have needs that the organization does not address.
Steps are not clear enough. It looks to me it's a step by step guide but it missed at least 2 points :
- the search engine must be Google I think ? Mine is duckduckgo and it doesnot work
- I still dont know if my device is supposed to be in airplane mode or no for the test. In airplane mode, even with Google set as the search engine, it does not work. Pixel phone. If I am connected to internet, I do have the single result from the google search.
I guess we are expected to be pleasantly surprised by something, but since I don't know what to look for and it does not work, it's a miss for me.
Personally I prefer to have the explanation alongside the steps that way I know what I am doing and can correctly interpret the instructions. For me, learning the technical trick does not diminish my contentness.