639 karma · joined August 10, 2017
Do you happen to know what those techniques might be called? Kinda hard to search for these kinds of things without knowing the right terms.
This version does everything in webgl shaders and keeps all state for the simulation in textures / uniforms. This allows it to simulate and draw more particles. Unfortunately it may not run on all devices because it uses some less supported webgl extensions.
This appears to be untrue: https://en.wikipedia.org/wiki/Global_Social_Mobility_Index
Germany ranks 11th on social mobility, while the us ranks 27th.
If you test everything at the same time, some values are bound to be outside of the normal range, just because you’re measuring so many things at once. Doing any kind of procedure to further investigate or treat the symptoms has a risk associated with it.
In the end, doing a full body scan, with current medical technology (both in terms of the test equipment as well as our means to treat anything that comes up as a result of the test) is a risky thing to do. It sounds nice in theory, but unfortunately we do not live in the utopia you speak of.
When we reach that point, anyone's job will be at risk. Give that AI an AWS account and a credit card and it'll take over the world, not build websites when someone asks it to.
It's interesting to see that these face detection models have been getting a lot better over the past couple of years, making it easier to stable and cheap webcam-based tracking.
That said, if you look closely at the videos in the original article, there's some noticeable delay between the camera moving and the program responding. The original wii controller based prototype that this was based off doesn't suffer from this delay because it used infrared LEDs. It's annoying to have to place those somewhere near your face, but once you have them there the face tracking because basically instant.
And while it's true that there are methods for extracting a surface from a NeRF, achieving a high quality result can be challenging because you have to figure out what to do with regions that have low occupancy (i.e. regions that are translucent). Should you consider those regions as contained within the surface, or outside of it? Especially when dealing with things like hair, it's not obvious how to construct a surface based on a NeRF.
Some nice things:
- Anyone can host their own Matrix homeserver, which can then sync its data within a federation, allowing users pretty fine-grained control over what data they share and with whom.
- Add end-to-end encryption, and it becomes even better: data stored somewhere in the cloud (i.e. the user doesn't have to manage a server), but the server knows almost nothing about what you've stored aside from some metadata.
For those people it's very helpful to first get a sense of what it all means (even if it means that initial mental model is somewhat imprecise), because it makes understanding the equations easier.
Sometimes making software more user-friendly may even cause the code to get more "ugly", because instead of a nice and elegant piece of software that only solves the core problem, you now have to deal with all the weirdnesses of how people perceive the problem as well. Taking away complexity on the user's side almost always adds complexity to the code. And if you're the developer, it's very easy to think that the tool you created is perfectly usable, because you understand everything about the mental model that went into it.
I find it hard to believe that this platform will be competing against Amazon Mechanical Turk on price, so they'll have to compete in other dimensions. Increasing worker motivation to improve the quality of the output is a win-win for all the stakeholders, so IMO it's worth pursuing.
This has a real impact on the people that live in those cities. Without it, there would still have been plenty of people that wanted to travel to these places, but without part of the housing supply meant for citizens going to tourism, the price of a room would simply go up.
This approach allows tailwind to be terser than raw inline styles, while giving you the ability to write a lot of your styling inside the markup, which prevents context-switching. It's a nice balance between many of the approaches that have come before it.
I can see the argument for JSX being more flexible, given that you can store little bits of JSX in js expressions, something you typically cannot do with the other component frameworks. But tools like svelte have their own DX improvements that make things like state management / reactivity arguably a lot easier than React.
So what should these people do instead? Stay where they are and get paid much less?