Could one use something like this from the surface to detect steel submerged under 20-40 feet of water?
Readit Newsmcculley commented on Build a DIY magnetometer with a couple of seasoning bottles spectrum.ieee.org/listen-... · Posted by u/nullbyte808
mcculley commented on CATL expects oceanic electric ships in three years cleantechnica.com/2025/12... · Posted by u/thelastgallon
There are multiple electric ferries already in operation:
https://en.wikipedia.org/wiki/MV_Ampere
They are quite impressive but they are still very far away from your average ocean going cargo vessel.
Yeah, the oceanic part is the issue. Going between two close points, at least one of which has electricity, is easy.
mcculley commented on CATL expects oceanic electric ships in three years cleantechnica.com/2025/12... · Posted by u/thelastgallon
I am very skeptical. Battery tech is still far away from the energy density of diesel fuel. How far could an electric ship go and what could it carry?
> Krishna also referenced the depreciation of the AI chips inside data centers as another factor: "You've got to use it all in five years because at that point, you've got to throw it away and refill it," he said
This doesn't seem correct to me, or at least is built on several shaky assumptions. One would have to 'refill' your hardware if:
- AI accelerator cards all start dying around the 5 year mark, which is possible given the heat density/cooling needs, but doesn't seem all that likely.
- Technology advances such that only the absolute newest cards can be used to run _any_ model profitably, which only seems likely if we see some pretty radical advances in efficiency. Otherwise, it seems like assuming your hardware is stable after 5 years of burn in, you could continue to run older models on that hardware at only the cost of the floorspace/power. Maybe you need new cards for new models for some reason (maybe a new fp format that only new cards support? some magic amount of ram? etc), but it seems like there may be room for revenue via older/less capable models at a discounted rate.
But if your competitor is running newer chips that consume less power per operation, aren't you forced to upgrade as well and dispose of the old hardware?
mcculley commented on China Has Three Reusable Rockets Ready for Their Debut Flights china-in-space.com/p/chin... · Posted by u/speckx
That's awesome.
Secretly (?) I'm hoping for another "space race"— this time between the U.S. and China. I'm hoping this for the U.S.'s sake. I'm hoping that good can come of it.
There is a market for this on Kalshi and China is narrowly in the lead again, according to traders.
https://kalshi.com/markets/kxmoonman/manned-mission-to-the-m...
mcculley commented on China Has Three Reusable Rockets Ready for Their Debut Flights china-in-space.com/p/chin... · Posted by u/speckx
Congress will notice when old politburo members start living on the moon base healthy for another 20 years
Will they live longer on the moon?
(Maybe you are just joking, but I wonder about the idea.)
When I was a kid, it was a general assumption in science fiction that living in zero-G or low-G would provide health/longevity benefits. Our experience with the ISS shows that microgravity is bad for health (muscle atrophy, bone loss, vision problems). It is not clear that low gravity would be much different.
Electron isn't popular because SwiftUI sucks (although both statements can be true at the same time) it's because big shops have decided that it's not worth the cost to develop native UIs on each platform anymore, so the only way they've decided we will get "native" apps is via Electron.
If electron didn't exist, it would be QT, or we'd only see native apps on Windows like the old days, and nothing at all on macOS and Linux (or just web apps).
It's not a tech issue but a cultural/management problem.
Personally I try to avoid Electron apps as much as possible, but it's pretty much unavoidable now. Docker Desktop, Bitwarden, 1password, slack, VSCode, dropbox, GitHub Desktop, Obsidian, Notion, Signal, Discord, etc. All the major apps are electron. Even in the Windows world Microsoft stopped making native and makes heavy use of their own version of Electron (EdgeWebView2) for their own apps. The freaking start menu is react native ffs.
The industry has lost its collective mind in favor of being able to hire cheap javascript talent
I have written applications for macOS in Objective-C and remain a Swift skeptic. Maybe the language has more serious design behind it now. I don’t know. As much as I hate JavaScript, maybe it is time for Apple to provide a JavaScript API or their own official Electron layer. I really hate how Electron apps don’t use the same text input field as the rest of macOS.
>>there is a fear of not being selected to ask questions
That's not exactly what's happening.
>>The rules limit where reporters can go without an official escort and convey “an unprecedented message of intimidation” for anyone in the Defense Department who might want to speak to a reporter without the approval of Hegseth’s team
On NPR (National Public Radio) a few days ago, a reporter said they could wander the halls of the Pentagon and ask anyone they ran into any question about anything. This will not be allowed anymore and, considering it's the Pentagon, doesn't seem unreasonable to me.
What is the right structure for the Ministry of Truth?
It seems as though a lot of arguments about this boil down to a few inane implications:
1. Apple should test every (common?) app and any change to the OS that they make that makes an app worse shouldn't be done regardless of why they wanted to make that change. 2. Even though Apple tells people not to use private APIs, if a program uses a private API anyway Apple should build a workaround into their OS instead of letting apps suffer their own repercussions. 3. Apple should test everything ahead of time and then go around telling all the app developers that there's a problem, as if those app developers are going to do anything about it.
No matter what Apple did here, their actual choices boiled down to:
1. Add workarounds for misbehaving broken apps, giving those apps no incentive to fix their issues, and forcing Apple to support those workarounds indefinitely; this also undermines their "don't use private APIs, they could break later" position. This is the kind of thing that made Windows into an unmaintainable sack of cruft.
2. Do what they did, which is change the API and let broken apps be broken to the user's detriment. Everyone blames Apple even though it's objectively not their fault.
2. Add some kind of non-workaround that caused problems for the app and not the user; e.g. have this private API rate limited or something so that the app ends up blocking in the call. Could cause problems for actual consumers of this API, and people would still blame Apple but in this case it would be more of their fault than option 2.
In the end, Apple can't spend their time fretting over what bad developers do wrong; they spend their time on their OS and software and if a developer writes bad software and causes problems then so be it.
Apple really should investigate why so many popular apps are implemented using Electron. Is it that hard to use the native APIs now? If so, Apple needs to improve the native application development experience. The UX on these apps is terrible and should be embarrassing for all involved.