A reusable rocket without an asshole.
It's a state-owned company. Have you forgotten what's still going on in China? In the Xinjiang region, over a million Uyghurs and other Muslim minorities have been in "vocational education and training centers" since 2017. If you think that carrying out a genocide doesn't make you an asshole then you are an asshole.
Why are people so hung up on using typescript instead of using a compiled language? If you want speed then using a compiled language is the only way to go.
How is it that you seem to both see and ignore the part where they're building their own power supply?
That's a listed "goal", not something they have done. Do you have information claiming they have built their own power generation systems?
I don't know what you mean by the discharging comment.
Finally, some truth from you. You don't understand the issue. Batteries heat up during discharge.
It is not cross-API compatible because it is an API. It's implemented on multiple platforms and it's only supported on platforms it's implemented for.
Also, you seem to be forgetting there are a lot of API specific functions functions: e.g. vkCreateWaylandSurfaceKHR, vkCreateWin32SurfaceKHR, vkCreateXcbSurfaceKHR, vkCreateXlibSurfaceKHR.
I have never known ICEs to break in snow storms specifically
ICE can randomly break while you're driving for no reason. That's how mechanical system work: they do until they don't.
On the other hand, an EV can lose 40% just from being in -17c.
Why would you think that a discharging battery would be anything but warm? Do you not know that batteries put off heat when discharging?
Why would you want to capture an infinite capacity for spite?
For spite, obviously.
The problem is improperly managed (damage/overcharge/etc) cells self-inflate to become what what the internet refers to as a spicy pillow. If they have eliminated the possibility of creating a spicy pillow then I have overstated the danger. However, so long as battery damage results in thermal runaway that causes a total carbecue then it they need to keep pushing toward making it entirely solid-state. ICE has a higher chance of carbecues but facts be damned, people are sufficiently stupid to hold onto that concern.
When a battery can be damaged without presenting a damage to the car then the battery is sufficiently safe.
If you don't mind the pain and possibly absolute danger of possibly finding out your battery is failing while driving
What you are describing is how ICE fails not how that is not EVs fail. Honestly, you just made an argument against using ICE.
One of the biggest barriers to Open Source adoption has been clueless bosses that are impressed by shinny presentations.
If we're being honest, this is what has driven software adoption within businesses.
His name is Edward Snowden.
FTFA (minor clarification be me):
Semi-solid-state batteries significantly reduce the amount of liquid-that-immediately-bursts-into-flames-when-exposed-to-air-and-doesn't-stop-burning-when-you-douse-it-with-water inside the cell, improving thermal stability and lowering the risk of overheating, swelling, or fire.
I think it's fantastic that they are reducing the amount of hot sauce they are putting in batteries but I think they need to push until they completely eliminate it.
A slow burn is better but no-burn is best.
In that context, yes, both types of cars can drive for the normal lifetime of a car. By this attribute, an EV the better economic choice. Should your car make it beyond the lifetime of the battery pack, it will be more economical to replace the battery pack rather than utilize an ICE car that you have maintained.
Cryptocurrency is a waste of energy and drain on the economy. Nothing of value is produced because it's all a grift.
The point is about how long a person could make a car last if they wanted to
That's also stupid because you can turn anything into the Ship of Theseus if you try hard enough.
If you aren't talking about the economics of it then you're just talking about your feelings. Economically, ICE is a failure.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (1) Gee, I wish we hadn't backed down on 'noalias'.
