Underwater Chain Saws
stanleyinfrastructure.com
stanleyinfrastructure.com
Amazing how capable tools can be, in industries that simply cannot get their work done without them and are willing to pay a healthy amount. Sometimes I wonder how good our dev tooling would be if we were willing to pay thousands a year, as opposed to the time-wasting bug-fest that is Xcode. Not singling out Apple, I’m sure all are comparably bad, it’s just what I happen to use :)
I feel like we need an Apple-themed Godwin's Law - namely that no HN thread is complete without someone somehow managing to bring up Apple and how evil and undervalued they are.
The irony is that high-end Macs have been widely laughed at by people who don't have a use for them...while various creative and scientific sectors gladly pay that expense because unlike the commenters they're actually using them to make money; for example, the G5 and first-gen Mac Pro had enormous memory bandwidth that made them ideal for a lot of scientific data processing, medical imagery, running instruments, etc.
Also, gently, note:
> Not singling out Apple, I’m sure all are comparably bad, it’s just what I happen to use :)
The Xcode thing is often an in-joke with iOS developers.
I’ve been here 11 years and see this all the time.
This, however, is not an instance of it.
Yet here we are on a thread linking to a site showing an industrial underwater chainsaw, and someone has managed to connect it to tech (possibly, and normally hinting at the importance of FOSS) and managed to have a dig at Apple, Microsoft or Google.
Easily 100-150k per seat for mixed signal chip design. Cost as much or more than the salary of the person using it.
And yeah. It certainly is a better tool than Xcode.
Apple don’t even let you downgrade iOS on your own devices.
Compare and contrast.
Worst software I ever used. Crashy, slow, critical features missing (example: debugger can show thread list... but not the stacks of other threads).
So no, I would not expect expensive commercial software to be better. It might generate 2% faster code or be certified, but the day to day experience would be terrible.
They both were discovered by former colleagues of mine. And named by me.
I'm sure there are shady vendors of high end software products, but at those price ranges there's no reason to choose them over established names.
If you've literally never seen a guarantee like that and your company is actually paying that much money for a product, then it would be wise to shop around.
Jetbrains used to make an IDE for Objective C and Swift, but they sunset it last year due to weak sales. They still make fantastic tools for other programming languages though.
$4100 is peanuts compared to how expensive are (professional) underwater jobs.
Metals, in particular. This is why in marine environments, special grades of stainless are used. Most commonly SAE 316 alloy (often marked with "A4", vs "A2" for regular stainless).
Another approach is the use of sacrificial anodes.
Where practical, it helps to rinse equipment with fresh water after use.
https://www.hse.gov.uk/foi/internalops/sims/cactus/5_02_18.h...
Look no further than embedded development. Everything costs a fortune, but makes Xcode look polished and a pleasure to use. And I really hate Xcode.
The cost has to be that high, considering the annual market for hydraulic underwater chainsaws can not be more than a few hundred at best. Considering the environment these are expected to work in means the R&D costs are considerably higher than your bog standard chainsaw, with much few units to spread that cost over.
Xcode is most certainly not free, at the minimum you need an apple computer. So you must pay apple to use it.
If it sucks, it's not because a lack of money, it's because Apple doesn't care.
That chainsaw is a yearly subscription? I'd rather pay once for a chainsaw.
Would we pay that directly or our employers? Also, how many would pay if the benefits are greater productivity for their employer instead of greater income from increased velocity?
> Maintain proper footing and balance at all times.
Is this not supposed to be used in deep water? Or am I just swimming wrong?
'Your honor, our manual clearly stated to maintain proper footing and balance at all times, which the diver clear did not do, resulting in his unfortunate death when our tool exploded and severed his air line. We move for summary dismissal.'
It doesn't sound like it's meant to be used in very deep water, since it's intended for cutting through wood:
> The Stanley line of underwater chain saws are designed for cutting all types of wood structures including bridge pilings, pier and dock timbers. All chain saw models include an interlocking safety trigger with hand guard and stainless steel spool and fasteners.
There's a photo of it being used, but it's very unclear what's happening: https://www.stanleyinfrastructure.com/sites/default/files/pr...
I gave up chainsawing the day I accidentally sawed through my boots. Just that morning I had put on a pair of steel toecap boots for the first time. Saved my toes.
Amazing coincidence. Cannot help but think that it was not a coincidence, but you feeling your toes safe because of toecaps.
At 2000 psi and 14gpm the saw consumes 12.2 kw or 16.3 freedom (horse) powers
I suspect a gasoline-powered chainsaw wouldn't work underwater... which made me wonder if maybe that does exist because you could feed it O2 from a supply tank just like the fuel, maybe even from the diver's own air tank?
Now I want to know how bouyant battery-packs are and if an impractically-heavy battery-powered chainsaw work well underwater?
I strongly suspect that this is incorrect. A given amount of oxygen and fuel releases the same amount of energy at any (reasonable?) pressure. 4x oxy (and fuel) --> 4x energy... this is the principle of turbochargers and superchargers (although the limiting factor is compression).
Interestingly, and paradoxically, I suspect that at an appreciable depth you mitigate the "air pump" effect and you don't need the compression stroke (or as much of one) to achieve a particular fuel mixture density prior to ignition so you'd lose "compression braking" and gain some efficiency.
(I also suspect that what happens if your vessel implodes and you're suddenly subject to 6,000psi is that the now superheated oxygen reacts with any oxidizable material at hand in an explosive exothermic reaction.)
The air in the engine will be 4x as dense, but the flow rate will be the same.
The air in the tank cannot change density, and will therefore have a 4x higher flow rate.
The result is that storage is worth less strokes/breaths at depth.
Even the pressure going into the combustion chamber could be a complicated thing, right? Say you’re at 20 feet, that’s a fair amount of pressure. But what if you’re at 80 feet? Would it still be able to function the same way? I assume no, but I also know nothing about running ICEs under water.
You'd probably lose some efficiency because the difference between peak pressure and neutral pressure in thr cylinder feels like it would be smaller. Perhaps not, because you could fit much more fuel and air in the cylinder for a bigger bang?
https://www.earthmoversmagazine.co.uk/digger-man/view,komats...
the early big-dog robots demonstrated that famously.
I've seen what happens when a hydraulic line gets cut in an industrial plant.
That's a minimum of four people per job with complex time critical work in harbours holding up transit shipping can see that layered up to cover 24x7 operation.
The hose management is the air mix lines to the diver along with cmms and then any tool lines required - hydraulic, pnuematic, additional electric, etc.
Why do all these tool companies make actual good tools, and then license their names off to sell sub par rubbish trading off a name that used to be known for quality.