William Wenge-Murphy

Computers can never feel pain, not even in principle. They can't have experiences. Computers are abstract. Computers are numbers. A computer is identical to equations in pen and paper. Your math homework can't feel pain uk.finance.yahoo.com/news/man-bui...

Plants are more likely to feel pain than computers. Plants have action potentials ("spikes") and glutamate receptors (like synapses do) Consciousness is A Thing, a Natural Kind Computers are abstract. Computers are math. Math doesn't feel. There's no reason to think math summons consciousness.

Computers can never feel pain, not even in principle. They can't have experiences. Computers are abstract. Computers are numbers. A computer is identical to equations in pen and paper. Your math homework can't feel pain uk.finance.yahoo.com/news/man-bui...

I took the "make him easier" option and got an achievement for sucking ass, this game rules 😂

Tech weirdos who think computers can have feelings are so cringe.

"Computer" is an abstraction (e g. Turing machine) that could be implemented by infinitely many physical systems. You could represent TM states with Taco Bell sauce packets flipped to either side. A quadrillion Taco Bell sauce packets don't give ride to consciousness

I pointed ChatGPT at the ExCSS codebase to have it give me a full list of what the parser throws out instead of keeping it in the AST, as a baseline for my fork, and it also just went ahead and found some bugs in their code while it was at it, lol

UITK also has so many gaps oh my god. Designing without rem or em units is INSANITY. No viewport units is also irritating considering how simple they would be to implement, and that unity uses an off-the-shelf parser (ExCSS) for the syntax side anyway, but a lack of rem or em is CRAZY

Parsing is drop-in but to get started you have to do a selector engine which is gnarly, and also resolve specificity. And you can do that naively and inefficiently, but to do it *right* you'd need to be doing bookkeeping on subtrees (for partial updates) and....yeah, that's all a whole....thing.

UITK also has so many gaps oh my god. Designing without rem or em units is INSANITY. No viewport units is also irritating considering how simple they would be to implement, and that unity uses an off-the-shelf parser (ExCSS) for the syntax side anyway, but a lack of rem or em is CRAZY

It's really, really tempting to make a preprocessor that "lowers" extended properties to UITK compatible ones. I might not be able to resist. But you have to solve like 5 different problems just to get started, and then you can finally implement a few 'simple' properties.