Scholars_Mate

Then which Apple phone are you talking about? The iPhone 15 is pretty much the same size as the Pixel 8. The iPhone SE is the only small phone Apple seems to make, and from what I can tell from a quick search, they aren't selling a lot of them.

The iPhone 15 is 147.6 height x 71.6 width x 7.8 depth (mm).
The Pixel 8 is 150.5 height x 70.8 width x 8.9 depth (mm)

I would call that pretty much the same size.

No they don't? The iPhone 12 mini and iPhone 13 mini were the worst performing phones out of their lineup. Small phones are dead because hardly anyone buys them.

Texas does have anti-SLAPP laws passed and they are among the strongest in the nation. Unfortunately, the courts have ruled that they cannot be used in federal courts.

Then Linus responded pretty poorly (and ended up stepping down as CEO and is now a chief creative something or other iirc)

Linus didn't step down in response to this. I don't remember the exact timelines, but he either stepped down before this, or was in already in the process of transitioning to the new CEO when this happened.

No. Modern SSDs are quite sophisticated in how they handle wear leveling and are, for the most part, black boxes.

SSDs maintain a mapping of logical blocks (what your OS sees) to physical blocks (where the data is physically stored on the flash chips). For instance, when your computer writes to the logical block address 100, the SSD might map that to a physical block address of 200 (this is a very simplified). If you overwrite logical block address 100 again, the SSD might write to physical block address 300 and remap it, while not touching the data at physical block address 200. This let's you avoid wearing out a particular part of the flash memory and instead spread the load out. It also means that someone could potentially rip the flash chips off the SSD, read them directly, and see data you thought was overwritten.

You can't just overwrite the entire SSD either because most SSDs overprovision, e.g. physically have more storage than they report. This is for wear leveling and increased life span of the SSD. If you overwrite the entire SSD, there may be physical flash that was not being overwritten. You can try overwriting the drive multiple times, but because SSDs are black boxes, you can't be 100% sure how it handles wear leveling and that all the data was actually overwritten.

I feel like lightning rods are going to be needed on this planet to protect your factory, but you will also be able to use them to generate electricity. The alien ruins are also interesting. I wonder if they will be required for research on this planet, as in you need to explore a little and find/fix an alien research building, or deconstruct them for artifacts. I also wonder what kinds of enemies you might find here? Ancient, self-replicating robots defending their long-gone masters from ~~foreign invaders~~ you?

To native English speakers, yes. To non-native speakers, this is yet another bizarre rule they just have to memorize.

Micay stepped down as lead developer and foundation director. I'm not sure what role he has with the project currently, but it seems like he plans on leaving the project entirely, long term. I haven't heard of any controversy since then. They've been hard at work and actually added support for Android Auto last month.

So many great changes I'm looking forward to using in the new update! Being able to flip oil refineries and chemical plants is a huge QoL upgrade for making compact, tileable designs. If I need to scale a refinery/chemical pipeline hotizontally, I can just copy it, flip it, and butt the inputs or outputs together.

Setting assembler recipes with the circuit network seems more powerful (and complicated, seen by the number of combinators) than most players will ever use, but that's why I love this game. I think it's really funny how the devs went from, "Parametized blueprints might be too complicated for players," to, "just build a finite state machine out of logic gates to control your assembly machines." I'm really looking forward to seeing what other people are capable of doing with this. I'll have to dust off my notes from my digital logic classes before I have a go at it.

P.S. The devs totally missed the chance to make a Missy Elliott reference: "I put my thing down, flip it and reverse it."

This is great to hear! The lack of Android Auto support was pretty much the only thing stopping me from considering a Pixel+GrapheneOS. My Galaxy S10 still has some life left in it, but I'll probably consider replacing it with the Pixel 9 or 8a whenever those come out next year.

• SLC -> Single-Level Cell, i.e. 1 bit per cell
• MLC -> Multi-Level Cell, i.e. 2 bits per cell
• TLC -> Triple-Level Cell, i.e. 3 bits per cell
• QLC -> Quad-Level Cell, i.e. 4 bits per cell

The more bits per cell you store, the more dense and therefore cheaper your flash chips can be for a give capacity. The downside is that it is slower and less reliable since you have to be able to write and read exponentially more voltage states per cell, e.g. 2 states for SLC, 4 states for MLC, 8 states for TLC, etc.