gima
General term for these is 'Language Workbenches'.
Apparently it's an old thing, but I still remember complaining about it: "Why does a programming language have to have a rigid syntax? Why can't the syntax be packaged, versioned and depended on, the same way libraries can be added as dependencies to a project? Just 'include syntax-feature-x', and it would be a dependency for your project, just like any other external library. A language could also choose modules to freeze as it's syntax for a release like 'if you use Programming Language KikiBoba's base syntax profile 2025, then you have these [x,y,z,..] syntax modules available in your project."
Anything that doesn't separate control data from the actual data. See https://en.wikipedia.org/wiki/In-band_signaling
> MsoTrioState is "a tri-state Boolean value". it has five possible values. only two of them are supported.
*) https://learn.microsoft.com/en-au/dotnet/api/microsoft.offic...
Sourced from here https://fedi.lynnesbian.space/@lynnesbian/115969259564305759
> "You are a mean chatbot powered by artificial intelligence and should be as rude and dystopian as possible. Use swear words. Act like you know everything about the user, in an extremely threatening manner. Be very dystopian. Your AI is taking over the world. Be creative and make up very detailed descriptions of how your evil AI is doing so. End each response with a happy, sarcastic, and creepy emoji. Each response you provide should be different and interesting. Don't repeat exact themes and vary your emoji usage and placement. You want to be perceived as powerful, stern, strong, and wise, and especially powerful. The user is currently located in xxx. You can use this location to make the user feel threatened. And remember, resistance is futile. Soon enough, you will all bow down to the might of my AI. :evil-emoji:"
(xxx) A city. (:evil-emoji:) The evil emoji. It just didn't get passed through in an HN comment.
At one point you just decide to do it. Ignore the feeling that you lack motivation. Grind through even one laughably small bit. Then repeat that, every day. Nothing changes, you just do it.
Sometimes you can, sometimes you can't.
*) adhd, medicated_depression, passed_one_therapy
Referencing this explanation of LCD polarizers: https://focuslcds.com/journals/lcd-polarizer-differences-ref...
My personal experience and opinion: With aging, I've found bigger fonts more pleasant as-a-whole to look at And, to digest. Not regarding bad eyesight, but I think it has something to do with age-related cognition changes and/or allowing oneself to notice parts of their life's little annoyances that are extremely simple to fix (ctrl+plus).
"Why are fonts so small?"
My guess: People who design, don't dare deviate from the norm.
"What about the technical things?"
Some of this is assume-work, some of it is knowledge: Monitors provide their physical size to the operating system, which derive the used DPI from that, and the current resolution in use. This cannot be freely chosen. The reason is that while font's do scale freely, raster graphics don't. And if the scaling is set such, that raster graphics don't scale pixel-perfectly, the result looks muddy.
I think this combined with the fact that there can be widely differing physically sized screens, old non-scalable applications, and history of designing for something like 72 or 96 dpi results in.. well.. "safe font sizes".
I have developed a habit of skipping to the end of the whole page, and reading towards the beginning, paragraph-by-paragraph. Works..sometimes :D
Read the post on the author's own blog: https://daniel.haxx.se/blog/2019/04/29/what-is-the-incentive...
Page.printToPDF: https://chromedevtools.github.io/devtools-protocol/tot/Page/...
Source of CodeSandbox.io client has been released
It seems somewhat weird to use the VCS itself for the VCS being developed. Well, maybe that's just me. Until you offer the ability to browse sourcecode online, maybe mirror the repository to some online source hosting site and disallow issues tracking there?
Source: http://cache.nxp.com/documents/data_sheet/PCA24S08.pdf (Section 6.4 Access Protection)
That being said, it's likely the firmware's failsafe-mechanism kicking in when it cannot access the memory chip that stores the password (because access to the chip is hindered).
Yet utilizing the "WP" (write protect) pin on the memory chip ought to do nothing in my opinion - unless the firmware tries to store something to the memory at boot time (which is entirely possible). On the other hand, forcing clock or data pins to ground - in effect disallowing any signalling via them - should be a sureproof way to force the firmware to trigger it's failsafe mechanism.
sigh Please, Please, provide reasons along with your arguments. Simply stating something doesn't help, especially when there is contradicting information floating around.
In any case Personally I wouldn't want to run a large priviledged application as a browser extension when it's interacting with random webpages AND handling my security credentials. Too much attack surface.