IcePic

I liked the movie, and I haven't even played Final Fantasy.

The quality was good enough for me to enjoy the story without getting stuck in the "graphics".

but it had the letters s, e and x in a row, so that wont pass the work web filtering software.

You could own one of those Teslas with free supercharge for life. Except they don't do V2G. Probably not a total coincidence.

The problem with missing drivers is not "typing code fast enough", it is knowing that you need to poke 5 into [base-address + $0562] within 5 milliseconds of receiving an IRQ or something stupid like that which good docs would tell you why and how, but most/many vendors will not hand out docs on how to program their chips at that level. They will have docs on how to paint rectangles on an existing surface using the gfx card, but not on how to actually start it at poweron or something along those lines. If you can't make it start painting a screen and waking up the monitor at boot, it is of very little use that you can paint rectangles in the dark.

So even if you can divine that a binary windows driver sometimes writes a 5 into that register at certain times, you will have a far harder time figuring out how and when it is needed to actually do that, and the source you get will be super hard for anyone else to understand if its all magic numbers getting written into "random" locations, compared to say, "wificard.driver.radio_enable = ACTIVATE_RADIO;" even if it compiles into writing 5 to offset $0562. Such reverse-engineered sources are super hard to keep working in the long run, when someone rewrites how and when IRQs are delivered to devices or whatever major is happening in the kernels so this leads to drivers no longer working even if they did have a short period of use.

This is totally crazy. And cool. But also crazy.

In Sweden it has. When I got my EV 4 years ago, the list of public EV charging locations was about the same as the amount of petrol stations, now its 3-4x as many. And as others have mentioned, having a wall charger of your own is of course the easiest and cheapest, but fearing long distance travels with EVs in Europe is not a thing, I think.

Even then, what europeans would want is that noone could force them to copy or release it outside of Europe. Otherwise its kind of moot where its stored, if it can be coerced out anyhow.

Yes, did not mean to imply that everyone should know everything immediately, just that "the server was too small" feels a bit misguided. It might solve the problem to make the hw a real monster, but if you hit limits at 500 then I think one should look at the other parts of the equation. Glad you fixed it in the end.

In the 90s, people thought about the c10k problem, which is how to handle 10000 connections.

In those days, this 2GB server would have been a dream to have and probably had moved the needle to 20k, 50k or whatever the limit is. You only get problems with 500 connections on a modern machine if you are really really bad at handling each request.

It worked for Stephen Hawking, and he was totally worth listening to.

C64 also has a token parsing routine in zeropage.

It would also eat up even more RAM, so your 64k computer that "normally" gave you only 39k for BASIC, with Simons' BASIC loaded you would be down to 30.7k.

If we get new code by the "shovel", then it is likely trained on old bad code, so it might just (re)introduce old types of bugs by the shovel until all new fixed code overshadows the old code by a margin, which in turn will take a long while.

If they don't get scanned, then they also don't get fixed, so if they have the same amount of holes, they will stay vulnerable for longer.

Go back to amiga and C64.