That's a very vague prediction that took decades to bear fruit. The concrete predictions behind the investments into companies like Pets.com and Webvan failed. It took the survivors like Ebay/Paypal and Amazon to build the digital payment and shipping infrastructure over decades until cultural acceptance hit critical mass.
I only use it to help hold together some complex assemblies when putting them together so I can't speak to it's strengths, but:
> Do you need a conductive substrate on both sides to apply the release voltage?
Yes, you attach VCC to the substrate you want to remain bonded and GND to the substrate you want to detach.
> How available is it for purchase if you aren't Apple or Samsung?
You can just call up your usual 3M distributor and request it. It's over $2,000 for a 100 meter roll so it's not something you'll usually find in stock at your local Grainger but it's not some super-secret material only available to the biggest manufacturers.
The vast majority of the time, you don't hear about it at all. Leveraged buyouts and the monopolistic strategies like buying out all the private doctors or veterinarians in a region get all the negative press but they're a tiny fraction of private equity.
The big money is in really boring industries like mining/oil/resource extraction, power plants, infrastructure, construction, and other industries that are predictable and in high demand everywhere. PE firms often get the best deals because they thrive on those kinds of connections and can offer up large amounts of capital on favorable terms in exchange for first dibs. The "rich get richer" is their primary strategy and it works without minmaxing exploitation because that's a bottom feeder strategy, not one that can guarantee steady returns on tens of billions of dollars.
CPU cache space for code is much smaller than GPU memory for models (and the former is more important for performance since many CPU operations like pipeline parallelism are latency bound, not compute bound).
>This. Why spend extra on x3d cpu when you can have a reasonable game size (not that it has large enough cache anyway)
Because game(SW) devs/publishers don't care about spending money to optimize for reasonable size, and the enthusiast gamers want to play the game either way and will gladly fork out the cash for the HW to play it, if anything for the bragging rights.
Remember "will it run Crysis?" vintage 2007? Yeah, enthusiasts will be enthusiasts.
I'm a fan of the free market here. Badly optimized games will hurt their sales and force the studios to change or go bust, if the market decides so.
The real power with these kinds of tools isn’t prompting one shotted models but giving agents the ability to do the full workflow. You give them a description of the part and how it’s supposed to mate with parts from McMaster, Misumi, existing parts libraries, etc and the agent downloads the models, asks any clarifying questions to clear up ambiguities (using available part configurations to provide options when applicable), uses measurement tools to validate the design, provide material details for FEA, read and use PDF drawings/datasheets, and so on.
At least, that’s the theory. The problem is that none of the existing CAD tools (almost all exclusively built on Parasolid) are set up to support agentic workflows. None have proper text based representations, with the possible exception of OnShape’s feature script which is too undocumented and proprietary to be of much use. Even if it was supported, Parasolid isn’t set up to provide the kind of detailed error reporting needed to provide agent feedback.
I’ve been experimenting with this in ECAD by giving agents the ability to edit Altium files directly and it’s been working very well (even with footprint drawings!), but my attempts to do it with MCAD have fallen flat on their face because it’d require developing a geometric kernel from scratch with this workflow in mind.
What's your opinion on FreeCAD's scripting abilities [1]? The link [1] claims
> FreeCAD has been designed so that it can also be used without its user interface, as a command-line application. Almost every object in FreeCAD therefore consists of two parts: an Object, its "geometry" component, and a ViewObject, its "visual" component. When you work in command-line mode, the geometry part is present, but the visual part is disabled.
That still sounds much slower than actually making it yourself. Also you have to take extra time to review the agent's work. The idea of it making subtle errors, hard to find, non-obvious errors is off putting.
> Curious to hear if people have use cases where they find 1M works much better!
Reverse engineering [1]. When decompiling a bunch of code and tracing functionality, it's really easy to fill up the context window with irrelevant noise and compaction generally causes it to lose the plot entirely and have to start almost from scratch.
(Side note, are there any OpenAI programs to get free tokens/Max to test this kind of stuff?)
Totally agreed. I’ve been reverse engineering Altium’s file format to enable agents to vibe-engineer electronics and though I’m on my third from scratch rewrite in as many weeks, each iteration improves significantly in quality as the previous version helps me to explore the problem space and instruct the agent on how to do red/green development [1]. Each iteration is tens of thousands of lines of code which would have been impossible to write so fast before so it’s been quite a change in perspective, treating so much code as throw away experimentation.
I’m using a combination of 100s of megabytes of Ghidra decompiled delphi DLLs and millions of lines of decompiled C# code to do this reverse engineering. I can’t imagine even trying such a large project for LLMs so while a good implementation is still taking a lot of time, it’s definitely a lot cheaper than before.
[1] I saw your red/green TDD article/book chapter and I don’t think you go far enough. Since we have agents, you can generalize red/green development to a lot of things that would be impractical to implement in tests. For example I have agents analyze binary diffs of the file format to figure out where my implementation is incorrect without being bogged down by irrelevant details like the order or encoding of parameters. This guides the agent loop instead of tests.
When I was developing my ghidra-cli tool for LLMs to use, I was using crackmes as tests and it had no problem getting through obfuscation as long as it was prompted about it. In practice when reverse engineering real software it can sometimes spin in circles for a while until it finally notices that it's dealing with obfuscated code, but as long as you update your CLAUDE.md/whatever with its findings, it generally moves smoothly from then on.
reply