Lockheed's job is to follow the customer's specifications.
NASA's job is to check to make sure what they paid for is what they received.
I do this every single day as a quality inspector here. I don't know why a bunch of highly-degreed engineers can't do a simple job that a person with oonly a GED does without fail.
Actually no, it's Lockheed's that should have had a test-suite and conformance-suite for it, but probably only has a C-Suite. If the program is non-trivial proving its correctness can be very expensive to prove, both money and time wise, and something that is done contrary to the spec is obviously on the one executing the spec and being paid for it, which probably wasn't cheap and probably these expenses add to the "NASA only burns money..." narrative.
"Its not expensive because its niche, its expensive because its hard."
I'd counter and suggest it is expensive because almost nobody gives a damn about the first 3 layers in the OSI model, and have pushed most security responsibility up to layers 4-7. That's roughly half of your attack surface still exposed.
"Thats already puting thousands of volts and hundreds or thousands of amps through the silicon."
In a typical string of solar panels design, you'll get tons of volts but not a lot in amps - current cell maximums top out at ~11A and the connective MC4 wiring can't handle too much more current than that, so what you end up with is like a 1,000V 10A string on one MPPT connection into the inverter.
A solar panel is 4 feet or so on the long side. Theres 250+ of them in a string 1/4 mile long.... at 48 V/panel, you get to 12KV. even if it's topped out at 10A thats still 120KW... you need a hefty cable to carry that panel to panel. Which is the core of the point I was making.
Amps determine how hefty a cable needs to be, not volts. Volts mostly determine how thick the insulation needs to be.
14 gauge wire is basically all you need to carry 10A safely for an extended period of time regardless the voltage. It doesn't matter that you are carrying 120KW.
The proof of this is in EV charge cables. Those bad boys can carry up to 350kW. Yet the cables are often thinner than you might expect. How do they do this? It's by using high voltages (around 900V) which cuts back the amps to around 300->400.
Tesla's chargers peak (or used to) around 600V which has required them to have much beefier cables to handle the high current.
I get that. I'm pretty skeptical that 120 KW going through the last panel doesn't cause damage, and in the "multiple miles chained together" (to quote op) many MW going through the panel at the end of the chain doesn't run into some sort of issue in the real world. Even small percentage losses turn into a lot of heat or other issues at that scale.
If it doesn't why not just make the whole 100 mile stretch of canals discussed a single very long daisy chain of panels, and still address the concern of the OP in terms of extra material for conductors?
And so ultimately, despite my details being wrong about currents, the notion of stringing miles of panels together is probably not a good basis for rejecting the panels over the canals.
In reality, you shouldn't string a lot of panels together for other reasons. An obstructed panel doesn't just not produce energy. It acts as a resistor, _wasting_ energy that flows through it.
You would have short strings of panels and small string inverters built every ~100 meters along the channel. Inverters will also connect to the high-voltage bus cable, likely buried in a trench along the channel. And most channels in California are not gravity-fed, so they already need pump stations along the way and have power distribution systems for them.
"Theres 250+ of them in a string 1/4 mile long.... at 48 V/panel, you get to 12KV. "
And they're never installed in config chains that high voltage - cell spacing between cells is typically very low and only capable of withstanding ~5kV before internal arcing occurs.
Also, your typical 72-cell solar panel is only 32V.
Sounds like an unauthorized access of my computer - a fine of a dollar per byte, per person, should make Apple turn the hell around. 15 billion dollars times how many Apple users that have been wronged in this manner? Apple would be dead instantly.
I think you'll find that you agreed to it somewhere in their voluminous terms of service.
I looked it up and indeed, it's in section 1, paragraph C:
Your Device will periodically check with Apple for Apple Software Changes. If a change is available, the change may automatically download and install onto your Device
and, if applicable, your peripheral devices. By using the Apple Software, you agree that Apple may download and install automatic Apple Software Changes onto your Device and your peripheral devices.
He said it's "unauthorized access of his computer", even though he implicitly authorized it by clicking through the agreement (apparently without reading it).
If people actually read these clickthrough agreements and started sending devices back when they don't agree, it would encourage the industry to change.
No one "needs" an iPhone, they can support one of the open source phones with far less onerous terms.
IMO the notion that such one-sided agreements are not made under duress needs to die in a fire. I wish there were a viable grassroots political movement to remove the corporate boot from our neck; until that point, fuck these terms of servitude and every abuse they enable.
It's true - every current cockup in our custom production system comes from Apple-using developers.
All of our Linux stuff is rock solid and is what we actually use to communicate with our satellites. We will explicitly avoid Microsoft and Apple here.
I'm hearing in other chats that this is actually a rehash of a nonsensical recycling attempt done a couple of years ago.
So I want to ask a question. What in this study would throw the HN people off as incorrect or raising a flag? Is terminology being used incorrectly? Is data vs shown photographs not quite matching up with what is being stated? I'm no battery expert, so I'm quite curious as to why I'm hearing that this is fake from people that work directly in the battery industry (and they're not big companies, most of them are individuals providing various services, some in recycling, some in custom manufacturing, some in installation.)
"It's not reasonable to expect thousands of existing games to port to ARM"
Realistically it is possible and not actually that difficult. The hardest part would be ensuring that specific code changes from older x86 code to modern ARM code actually translate over properly and perform as expected. The majority of work done there would have to be in the libraries that were used to build the game. For way older games, like the ones you'd run under DOS, it would be much easier, as most stuff was in ASM and C (you did have the occasional BASIC game or PASCAL game flying around which would likely need a little bit of extra work) so you'd just be doing direct translation of instructions.
Let's just use Flock cameras to track all top-level YC people, publish everything we possibly can. Absolutely and utterly eliminate their privacy until they learn to respect ours.
"Sounds like he is salty that somebody found an exploit using LLM that he found manually"
No, he's salty that this last remaining hypervisor exploit is going to get patched, causing his PS5 Linux project to get wholly-fucked as now there will be no (currently-known) way to sideload the OS. Reading comprehension is very important here.
Both parties fucked up.
Lockheed's job is to follow the customer's specifications.
NASA's job is to check to make sure what they paid for is what they received.
I do this every single day as a quality inspector here. I don't know why a bunch of highly-degreed engineers can't do a simple job that a person with oonly a GED does without fail.
reply