does bubble memory count as solid state?
I guess? I mean, it has no moving parts. but it requires preheating and involves movement of magnetic fields across a surface...
https://t.co/VG3XdoQ6OZ
That falls apart when you consider that vacuum tubes aren't considered "solid state", something about how they use thermionic emission and magnetic fields is enough to push it out of the realm of just electron movement.
— laura possum #blm (@quartizine) January 3, 2021
It has to warm up, yes, but it doesn't melt. The crystal remains solid, and only the magnetic fields move.
The other axis is managed by spinning the disc, and waiting for it to rotate around.
https://t.co/JlCPyOXXzL
So LaserCard is an interesting format: It's fundamentally the same as CD-ROMs, LaserDisc, DVD, etc, but instead of spinning, it's a flat grid layout. pic.twitter.com/bRmMCNL1vD
— foone (@Foone) November 21, 2018
does it count as solid state if doesn't move while in use, but it's connected to things that do?
they're immobile, and the universe spins around them?
solid state discs aren't "solid state" because they're not moving. not moving has nothing to do with if they're solid state or not
integrated circuits. all the flash memory stuff happens inside a die of silicon.
It's a chunk of garnet, not anything semiconductory
I want to make a rotating solid state disk.
https://t.co/aVU1sri57P
I was actually researching something about slip rings, and found this lovely picture.
— foone (@Foone) September 16, 2020
Want some ethernet you can rotate 360 degrees? NOW YOU CAN! pic.twitter.com/dLqMxAR5Hv
More from foone

How the fuck is a CF card "USB Enabled"?

So CF cards are a weird beast that act as either a PCMCIA card or an ATA/IDE card depending on a mode pin.
They're definitely not USB.
And it's not like that weird SanDisk card I have which you can fold in half and plug it in as a USB device.
Flip it over, bend it in half, and now you can plug your SD card right into a USB port pic.twitter.com/jeBefP2xU1
— foone (@Foone) May 2, 2020
It turns out the reason for "USB Enabled" is because it's a Lexar drive from the jumpSHOT era.
This is a normal CF card in most cases, you can use it in normal CF card readers and such
it is the most frequently manufactured device in history, and the total number manufactured from 1960-2018 is 13 sextillion.
That's 13,000,000,000,000,000,000,000.

Though this picture is a bit misleading.
Even with devices this small, we couldn't make 13 sextillion of them in 60 years.
So imagine a chip like this. It's the 555 timer, which is one of the most popular integrated circuits ever made.
In 2017, it was estimated a billion are made every year.

And at the heart of it is the die, which looks like this:
(from Ken Shirriff's blog)
https://t.co/mz5PQDjYqF

And that's fundamentally a bunch of CMOS transistors (along with some diodes and resistors), which are a type of MOSFET. How many of them are on a 555?
about 25. Not many, but it's a very simple chip.
More from Tech
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
I\u2019d recommend that the devs participate directly in the research.
— Jared Spool (@jmspool) November 18, 2018
If the devs go into the first sprint with a thorough understanding of the user\u2019s problems, they are far more likely to solve it well.
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.