Anything can happen, but you're predicting the future without any evidence. You just made up a scenario in your head, predicted it would come true, then you can't believe people would say it's ridiculous.
When was the last time this happened with a gas car? How often are fires happening with lithium iron phosphate?
You think a car is going to crashing into a building AND burst into flames AND be impossible to put out AND burn the building down?
When was the last time this happened? Let's think about odds and statistics super hard.
>When was the last time this happened with a gas car?
ICE car fires are easier to put out.
>You think a car is going to crashing into a building AND burst into flames AND be impossible to put out AND burn the building down?
EVs catching on fire and then being impossible to put out is something that has already happened, and in fact as I understand it the latter invariably follows from the former. The only new thing that needs to happen is the fire happening while the car is not out on a road, but inside a building where it can set other things on fire. The fact that the vehicle cannot be put out and can frustrate firefighting and rescue efforts makes an already dangerous situation even more dangerous.
Which part of any of this is straining your imagination?
>When did one crash into a building, catch on fire, and kill people? Surely this must have happened at some point for you to put all this together.
You can't think of a single example of an ICE vehicle crashing into a building, starting a fire, and a bunch of people dying? I can think of two such crashes happening the same day, involving jet engines.
I don't know why this is relevant, though. The topic of discussion is lithium batteries, not ICEs. A vehicle crashing into a building and starting a fire that kills people is not some science fiction scenario that should need to be defended. Your incredulity is straying into bad faith territory.
>you changed what you're saying
I changed it because I think it's it's pretty obvious that the concerning thing is the EV catching fire where it can easily spread to other things. Whether that's because the vehicle crashed or for some other reason is inconsequential. The reason I gave that example initially was because that's just what I happened to have in mind at the time; it makes sense that a crash could damage the batteries enough to cause a thermal runaway, rather than the car randomly bursting into flames for no reason.
>It's only a matter of time before someone gets hit by lightning after winning the lottery too.
Winning the lottery doesn't increase your chances of getting hit by lightning, nor vice versa, but crashing your EV does increase the chances that it can catch fire, and a building is one of the things it can crash into. Having a fire that cannot be put out likewise increases the chances that someone may die from it, compared to if the fire is easily to be put out.
I don't know, do you really find it that unreasonable to be a little bit concerned that cars now have these giant energy stores that if they fail they're impossible to control until they burn out completely?
You can't think of a single example of an ICE vehicle crashing into a building, starting a fire, and a bunch of people dying? I can think of two such crashes happening the same day, involving jet engines.
So your argument is that electric vehicles are dangerous because of 9/11 ?
That's what you said. Cars became planes and suddenly 9/11 is your example and somehow it means that someone will crash a car into a building, the car will light on fire and everyone in the building will dies. These are your words.
C++ is great, coroutines are not. Neither of these are good ways to handle concurrency. You really need a more generalized graph and to minimize threads and context switching. You can't do more than the number of logical cores on a CPU anyway.
If demand for AI continues to grow 100-1000x fold - there's just no way for datacenters to be sustainably built on earth. Also we already quite close for them to be built cheaper in space.
Fab thing I don't understand tho. Only reason is to bring manufacturing in US since next year China is invading Taiwan so we don't have to defend them.
A portable GUI interface is a hard problem, unless you mean "a browser window without an URL bar" and your controls are HTML/CSS components.
Says who? This has already been done over and over. Tk, FLTK, JUCE, Qt, ImGUI and many more.
Worse still, you're building an abstraction layer on top of several genuinely different systems,
Features are pretty common across linux windows and macos. Clipboards, input, files, all sorts of stuff works enough that the lowest common denominator still covers about 90% of use cases.
1) cross platform GUIs are ugly by default, compared to fully native desktop apps, because they don't entirely replicate the affordances or the style of the platform;
These two things don't connect. Not being identical doesn't mean ugly or only one GUI would be considered not ugly.
reply