I'm interested in reading more information as it comes out, but a lot of the comments claiming it's "just vibrations" are being a bit reductionist. These devices are controlled by complex algorithms, and they take a lot of time and money to create. Why shouldn't this company enjoy the same IP protections that Apple enjoys on their work?
I'm trying to understand how to "vote with my money" for not being recorded by these glasses in public. My best interpretation would be financially supporting private establishments that have banned these devices... Which feels like exactly what you're arguing against.
I feel like this has been a talking point for as long as off-the-shelf printers aimed at hobbyists have existed. Calling them AI factories is a bit off the mark imo, there are plenty of hobbyists that learn CAD and want to make their own stuff, but don't want to build their own printer. The kind of people who are interested in reprap are absolutely still around, and I really don't see that community going dissolving because of the rise of capable commercial printers.
I remember a story where some big wall climbers were stuck waiting for a storm to pass, and one of them had brought a paperback book to pass the time. Once he'd finished the first half he cut it in half so the other climbers could have something to do during the wait.
Meaningful decompositions have got to be my favorite subject in linear algebra, and SVD is the king of these. Another location this pops up is "eigenfaces", an early form of compression (and correlation) of images of faces.
Years ago I did a write up of how the SVD relates to singularities of a robotic manipulator:
Comparing OpenSCAD to CadQuery is super apples-to-oranges in the first place. CQ works directly with NURBS curves via the Cascade engine, and OS functions by performing CSG operations. Both certainly have their place, but for engineering applications NURBS are decidedly more powerful.
This is what it comes down to for me as well. If Apple has somehow magically solved the reliability issues this will be fantastic, if they are just fad chasing it'll be DOA
I love these kinds of problems, because they try to produce what humans perceive as random instead of something truly random. Another great example of this is blue noise
I see your point, but in this scenario how do you handle the problem of levying an accurate tax? I suppose we could rely on banks to value assets instead of the government, but since the banks are the ones giving out the loans to pay the tax this feels a bit circular
I guess I'm in the weird position of being a leftist who is generally against wealth taxes. Taxing non-liquid wealth like this requires the government to be able to accurately assess the value of these assets and that's an unrealistic burden IMO. I would rather address the "Buy, Borrow, Die" paradigm from other angles, like restricting the classes of assets one can borrow money against to force liquidation and therefore be subject to a traditional capital gains tax instead. That way the market takes care of the problem of pricing the asset and society can impose a tax on that valuation.
This appears to be a retelling of another well-known process for volume computation: sum together the signed volumes of the tetraheda formed by each face with the origin (or any other fixed point WLOG). Very cool derivation though!
At this point, does precedent even matter? Based on recent rulings, I feel like this exact scenario could play out again and the result would be the exact same.
It really revealed how much he relied on the gift of hindsight when writing his earlier books. Nothing wrong with that per se, but it's something he should have been aware of when doing a book on an ongoing event.
I have started using AI a bit, but I'm still trying to be careful in that if I ever lose access I can still perform my job at pre-AI ability. My understanding is that tokens are still heavily subsidized, and when that well runs dry I don't want it to be some nightmare to go back to the way I was doing my work in like 2022.
When I worked in robotics, it always pissed me off that our recruiters ignored game devs as candidates. There's such a huge overlap in the two fields in terms of the math underpinning the systems
This dovetails into one of my favorite CS sub-fields: approximation algorithms. In many cases NP-Hard problems may be approximated with a guaranteed lower bound of accuracy. For example, solving the euclidean version of the travelling salesman problem using a minimum spanning tree finds solutions that are no worse than 1.5 times the true minimum length, and there are heuristics with weaker guarantees that consistently perform better in practice.
Welcome to the lucky 10,000! SIMD is actually a pretty integral part of how GPUs are able to work efficiently, it's part of why there's such a strong focus on branchless programming in the field.
Where would you draw the line between someone advocating for their belief vs shoving it down your throat? Does the "extremeness" of the belief factor into the judgement? If so, how are we not back at the original question of the definition of what an extreme belief is?
I agree with a lot of this, and the framing is new to me and I really appreciate it. I especially appreciate the acknowledgement that there isn't necessarily anything wrong with having extreme beliefs; "extreme" is a label most often applied by antagonists of such beliefs. But I definitely feel like there can be a pipeline where one extreme belief may lead to others simply because they are also labelled extreme and not for a more recognizable reason.
Yeah, this take is wildly out of touch. Sure, it's great when you're able to derive philosophical meaning from your work, but at the end of the day the vast majority of people are here for the paycheck.
Are vertex insertion and deletion also supported/accelerated?
What compromises are keeping this constrained to 32-bit? It seems like you could cut back on quantization error by increasing bits, but if you're doing some manual SIMD magic to get this performance I can understand sticking with 32 bits.