It doesn't support basic code/monospace blocks using backticks:
> Unsupported Syntax Detected
> This file contains syntax that isn't fully supported in formatted view. Some content may not render as intended, and switching views could modify parts of your original Markdown. Do you want to continue?
When has MS ever implemented someone else's standard or even convention (MD is not really a standard)? They only ever implemented their own incompatible parody. They're even incompatible with themselves, because backticks do work in MS Teams. This software is probably vibecoded slop.
I don’t want lithium-ion alternatives for better range. Quite the opposite, I’m actually okay having slightly less range if it means my car won’t spontaneously combust. This one apparently improves the safety of lithium-ion batteries too, so it’s great, but I hate when headlines focus on one thing that matters the least.
> Quite the opposite, I’m actually okay having slightly less range if it means my car won’t spontaneously combust.
Modern LFP LiIon (LiFePO4) batteries are pretty damn safe now, and is also the dominant chemistry in new EV batteries and energy storage systems. The fire risk is nothing like what it was, arguably your wish has already been granted.
The Chinese market is mandating this year that EV batteries prevent fire or explosion for a minimum of 2hrs after a cell enters thermal runaway, and LFP is the main driver to achieve it.
Is this true when adjusting for vehicle age? The average age of an EV is quite a bit lower than the average age of an ICE vehicle, and I assume there is at least some correlation between a vehicle's age and how likely it is to explode (based on degradation, type of use, type of owner, etc.).
Neither EVs nor ICE cars spontaneously combust unless there's a design flaw. Even when this happens it tends to be very rare, but the Chevy Bolt fires for example were fixed with a recall. Similarly a Ford recall last year fixed a problem where fuel injectors could leak and cause an engine fire.
EVs and ICE cars can both catch on fire in a bad enough accident, but this is true regardless of the age of the vehicle, and tends to be more sudden and violent with gasoline explosions vs battery fires.
Exactly! The C64 could control where the beam started painting. To move the screen a pixel you just wrote the the x and y offsets to two 8-bit I/O registers. Only after scrolling 7 or 8 pixels you had to copy memory around. I was relatively easy to get this right smoothly and since everything was in sync with the beam it was easy to make tear free.
Shaking effects that did not require memory copy were even easier.
I was green with envy, when I saw how fast and smooth a C64 scrolled some text (iirc it was some machine code monitor). My Amstrad CPC464 had no text mode and the Z80A CPU was clearly overwhelmed with shifting the whopping 16KiB RAM of the graphics buffer or even just rendering a line of text.
Eh, the NES is better because you get two entire screen buffers. The C-64 gives you only one offscreen row or column to repaint every coarse scroll, and the colormap is fixed so you gotta move all of its bytes while racing the beam.
The term "disc" for storage predates optical media. "Disc" was the common spelling for a disk (like a floppy disk) on British 8-bit computers like Amstrad CPC or Sinclair Spectrum.[1][2]
It seems like the distinction simply comes from British and American preferences.[3]
I have no idea how Apple jumped to such an arbitrary conclusion.
Disk was already the standard spelling in the UK by 1984 (in a computing context), just as program was used in preference to programme. But Amstrad mistyped it as disc on the plastic mouldings for their first CPC, and were too cheap to change them. Consequently CPC 3in disks were always called discs even into the 90s.
Taycan relies too heavily on touch. Not even vent directions are manually adjustable on a Taycan. BMW i4 interior is much better in that aspect: many physical controls. I hope Porsche fixes its mistakes soon.
reply