I’m a technical kinda guy, doing technical kinda stuff.
It’s difficult on the back end of the charger as well.
A shopping centre or rest stop can’t just spring for a few high capacity chargers for the car park. A single megawatt charger is 50 houses worth of consumption, so they now need a substation upgrade to provide what is basically a whole neighbourhood-equivalent of power.
Well, I did delete a company-mandated image from the bottom of my signature after I realised that it made even just a one-line “Thanks” email balloon out to 800kb.
People don’t just leave leaking apps out there for consumption.
Ha! Welcome to corporate, where vendors sell you software and say that the hardware has to have 128GB of ram and when you poke around a bit you discover a single JVM with constantly growing memory usage with a script that restarts it every time it runs out of resources.
AND a log file that describes - in typical Java excruciating detail - the precise lines in each module where the devs allocated resources but didn’t free them. About 40 times a second.
Lol between the top paragraph and the bottom one the number of partners increased by 23. I wonder how many partners they have now?
Anything useful is still “unsafe.”
So you take care with the bits that have to deal with C, just like you have to with C code itself, and then all the rest of your code is still safe by default. Still a net improvement, yes?
Yeah basically you can only signal “on-off” so many times a second in a vga cable before the ons and offs get blurry and unusable. So you can trade lower resolution for a higher frame rate as long as you keep the total number of on-offs below the limits.
If it seems stupid, that just means that it was cheaper to do it this way.
Program ROM/EEPROM + RAM, or just RAM connected to a USB interface with a reset line tied to the camera processor? See the USB device ID connect , fill the ram with the camera software, toggle processor reset , off you go.