Unfortunately, I can relate 😓
RT @ADHD_Alien@twitter.com
Just as a "fun" addition, I actually really taped pencils to my hand to be able to keep drawing
🐦🔗: https://twitter.com/ADHD_Alien/status/1141024951232847877
horror
RT @supercomposite@twitter.com
🧵: I discovered this woman, who I call Loab, in April. The AI reproduced her more easily than most celebrities. Her presence is persistent, and she haunts every image she touches. CW: Take a seat. This is a true horror story, and veers sharply macabre.
🐦🔗: https://twitter.com/supercomposite/status/1567162288087470081
If you write a parser as a Ruby object that consumes its method_missing arguments, I guess you could just do full blown NLP or define any context-free grammar as a DSL?
RT @dmitrytsepelev@twitter.com
Check out my experimental gem for creating natural–ish DSLs with Ruby 🙂 Link: https://github.com/DmitryTsepelev/natural_dsl
🐦🔗: https://twitter.com/dmitrytsepelev/status/1554407425482047488
Hello, it's me.
RT @Gilesyb@twitter.com
This is an astonishingly important story from @jburnmurdoch@twitter.com. Our suddenly-diminished labour force is an immediate, dangerous drag on UK prosperity. It's a hypothesis, but if NHS decay is the reason, this is THE issue of the decade https://on.ft.com/3IYrtgP
I suppose that the answer is that there are many different types of sub and superscripts, and that sometimes you want, e.g., the subscript version of a character to look slightly different, but don't we already have support for ligatures in fonts for exactly that reason?
We have an interesting bug in #PLFA, where the font looks horrible across all browsers on Windows, but it looks absolutely fine on macOS. Does anyone know what could be going wrong here?