these translate rotary motion into linear motion. if you hold the screw fixed (with bearings), and let the nut float, then turning the screw moves the nut back and forth along the screw
you could make a standalone executable. I was assuming that people didn't want to start emacs to run it. if its just because...emacs is just morally offensive and one doesn't even want it running under the covers, I dont how to help you.
If you used Emacs as a stand-alone game engine, at least it could make it claim it was "Reticulating Splines..." for a few minutes while it started up.
the last section discusses this. the author was having problems relating the feed and the current settings to the weld characteristics. personally I prefer to manage all that with a pedal and manual feed with a tig
the swing is small enough that one doesn't even have to target individuals. delaying some mail from particular zip codes might be enough. suppressing urban voting a little might be enough. a few of these and you're done.
there is a presumption that the models we are using today are 'good enough'. by models I mean thinks like linkers and package managers, micro services and cluster management tools.
I personally think that we're not done evolving really, and to call it quits today would leave alot of efficiency and productivity on the table
not a gunsmith, but cast iron manages to be both soft and brittle at the same time. and the barrel and bearing parts would have to be machined anyways. you have to try to harden it too. its probably easier to just machine the whole thing out of decent quality steel. just guessing.
really? they didn't have machining in the 1700s. how about a good'ol musket? or a bit more modern: a gatling gun. I always thought those were made under coarse conditions. I mean, people just need something that makes a spark against gun powder,goes boom and shoots really fast projectiles. If a shotgun is possible, then an automatic shotgun doesn't feel like it's a stretch. I would think the firing mechanisms might not be tolerant of amateur techniques, but the reloading and trigger parts at least might be. I'm also not a gunsmith, no idea what I'm talking about for the record.
They certainly didn't have mills as we know them in the 1700s, but lathes, drills, and subtractive manufacturing had been in practice for millenia. You could say they were "machined by hand". Most early firearms (barring large-bore guns like cannons) were made from forged steel or iron, which is significantly stronger than cast iron due to its lower carbon content and regular grain structure. These forged parts were then worked on by gunspiths with cutters and abrasives to produce parts in tolerance for their mechanism. Cast iron (or more typically in early warfare, bronze) was suitable for cannons and large-bore guns due to the mass of the finished gun; more metal meant that the gun could withstand more shock, but even then they could fail catastrophically due to material fatigue or failure.
Well, the kind of guns politicians are afraid people will make at home are not intended for durability. But things like street crime, school shootings,etc.. where it's just a one and done affair.
Complex manufacturing of improvised firearms has been practically made obsolete by the commodification of both steel tubing and cartridges. "Pipe guns" are incredibly easy to make, and require little more than a pipe, a cap, and a drill (which can sometimes be omitted as well). Many common cartridge diameters very closely or exactly match commercially available pipe diameters, and the hardware to make a single-shot firearm is ubiquitous in any store that sells plumbing supplies. Pipe guns are simple and cheap enough to make that some people abuse gun buy-back programs by deliberately manufacturing pipe guns for pennies and pocketing the money these programs offer [0]. These are real, functional guns, and I promise they're simpler, faster, and cheaper to manufacture than any 3d printed gun.
I assume this is mostly for a shotgun shell affair? otherwise the difference in bore, and particularly the seam that is present in almost all steel pipe (unless its drawn-over-mandrel which is a more speciality product), would make it pretty dodgy to fire a proper round
they also didn't have 3d printers in the 1700s, so I figure the 3d printer doesn't add much if it requires all of these post-processing steps like molding, casting, and finishing
the largest unaccounted for victims of environmental degradation are our children and their children. given that we can't even keep from poisoning our own well water for our own uses today, it really does like on the whole we're failing to regulate sufficiently.
which isn't to argue that they shouldn't make sense. or that they should be used to tilt the playing field due to corruption, but on the balance claiming that we are currently overregulated is pretty indefensible.
this is likely wrong. the issue with partitions is that we can no longer communicate at all, thus we can't end up in the same state. If we have poor performance, thats certainly something that worth putting machinery in to adapt to, but its not at all in the same class as 'I can't talk to you and I dont know what you're doing at all' fro a correctness standpoint
edit: yeah ok, since failure detection is being driven by timers by necessity, then sure. the tradeoff we're making between the interval under which we're unable to make progress vs the upheaval caused by announcing a failure.
Yeah, I glossed over a few steps. There's likely a latency threshold beyond which you should abort, and then it is a partition (after all, that's what TCP is doing under the hood if it sends a packet and doesn't get a response).
One should be so lucky to have an operation fail immediately, rather than lumber on until it times out (holding resources hostage all the while)!
Note that once you have virtual machines, those other things can be provided using that same virtual machine interface. Layering and standards are really useful. Spin up your own storage cluster? if you want...pay a managed service from a third party on the same cloud? whatever makes sense to you. I find it appalling that because money was so cheap, people got used to just throwing it at the hyperscalers 'rich offerings', and now we have multiple generations of people that think RDS is some magic box that would take billions in investment to replicate.
This matches my experience. I run a pay-per-use VM service (shellbox.dev) entirely on Hetzner auction servers with Firecracker microVMs. Sub-second boot, full Linux environment, SSH-only interface. The entire "cloud" layer is Firecracker + Btrfs reflinks for instant copy-on-write cloning. No managed Kubernetes, no proprietary orchestrators.
The total cost of that stack is remarkably low — cheap enough to offer VMs at $0.02/hr running and $0.50/mo stopped, which undercuts most hyperscalers for bursty workloads. The "billions in investment" framing is exactly the problem. Most of what hyperscalers sell is convenience wrappers around commodity compute, and the lock-in is the product.
We didn’t do it because money was cheap we did it because there are tons of benefits to not having to inventory your own compute. Everything from elastic scaling to financial engineering was improved via the hyper scalar options and it’s ridiculous to act like those options aren’t valuable post hoc because Europe doesn’t have a native one.
I think the Heztners and their ilk are coming along nicely and probably can support a lot of Europes cloud computing needs, but they aren’t in the same league as the hyper scalars when it comes to capabilities currently. It would be great if they got there for everyone though.
exactly. in HPC we all understood that it was a tradeoff between money and time, and that the curve was exponential. if you wanted to race ahead of todays capabilities, you could, but you couldn't go very far without burning alot of cash.
because of the investment story about being first and building a moat, we have companies torching 100s of billions of dollars to see who can climb that exponential the furthest.
we have so much work to do, in infrastructure, and distributed computation models, and programmability, quantization, and information theory...just relax a little. you dont have to compete with OpenAI. OpenAI is just a giant waste of money. take your incremental gains and invest in research and I assure you we can get there without directing our entire economic output into buying the latest highest margin parts from Nvidia only to use them at 30%, if you're being generous.
It's true that the progress on clock speeds has slowed. Now we have to address the parallelism problem in order to keep moving forward. And we haven't done a very good job. Progress on that front will get us back on the acceleration curve. Saedfly, the current framing of 'who buys the most hardware', while I providing a nice marketing story, isn't netting us that much progress except what Nvidia spends internally.
reply