Keil, of course.

I see what you are getting at (and I actually do know the basics of SQL), but for embedded developers, i think it's much more important to know about the storage medium. Is it EEPROM or flash? What are pages and blocks? Do you need wear leveling? Can you erase bytes or only entire pages at a time? What is the write time og a page, a block and a byte? There are so many limitations in the way we have to store data, that I think it can be harmful to think of data as relational in the sense SQL teaches you, as it can wreck your performance and the lifetime of the storage medium.

Sadly, this does not seem to be the norm in my experience. I have not attemped to adding this myself, but I wanted to ask: are there any hurdles or other good reasons to not just adding this to every create? Why isn't it the default?

I'm saying that appears conscious and is conscious could very well be the same thing, we don't know, so in this imaginary world, I would not trust anyone who told me "don't worry, you can torture them, they are not actually conscious".

No. I'm very certain that my Roomba is not conscious. But If we can't tell whether or not these people are conscious or not, then I don't think it's right to have this power over them. A better parallel than a Roomba would be an animal.

I think it matters a great deal! I would like to believe that not only would I not use such a system, I would actively fight to have it made illegal.

How do you test that? How do you know that people around you actually have conscious and not just seem to have? If you can't experience anything, how do you fake conscious? And is this fake conscious really any less real than ours? I think anything that resembles conscious well enough to fool people could be argued to be real, even if it's different to ours.

What's the difference seeming conscious and being conscious?

Nope. Never heard of it.

The pairs version linked (which Is my daily driver), I don't think it's bad at all