Thanks for the additional information information, but with the "ecosystem gripe" I meant that most Overleaf projects are inadvertently designed for pdflatex simply because it's the default. No matter how much better other compilers are, pdflatex is the de facto standard in certain circles, even if few within these circles are aware of this (e.g. university laboratories), so I've had to begrudgingly switch back to latexmk for most projects to accommodate this.
A tool like this is sorely needed for LaTeX, and Tectonic is especially intuitive to embed into other applications, but the divergence of XeTeX from pdflatex makes it incompatible with most Overleaf projects. This is just an unfortunate ecosystem gripe, but for most workflows I end up having to reach for latexmk instead for this reason.
I've started using parentheses with notes/tangents to circumvent any false accusations of AI usage. They're nice to write, but bad form, so LLMs don't use them much.
I've been there, but it definitely felt like more of an enthusiast experience. Someone who's just looking into getting their first mechanical keyboard would do better at a larger shop stocked with cheaper keyboards and a greater variety of common switch types.
That being said, the shop is located in a surprisingly quiet area, surrounded by other small enthusiast shops. I especially liked "High Beam" a few stores down, which specialises in handheld PCs.
This is an entire Unity project that won't load due to however many content blockers I've got running on my phone. The incompetent one loads instantly, though it's admittedly laggy.
I think it's mostly just that a subscription seems weird for a tool like this. Most users would probably only need it occasionally, and with a subscription you can't just add it to your toolbox to grab when that time comes.
How many compatibility issues is MacOS realistically expected to spur? Windows DX felt unusable to me without a Linux VM (and later WSL), but on MacOS most tooling just kinda seems to work the same.
> Aura says a targeted voice phishing attack against one of its employees led to unauthorized access to about 900,000 records [...]
Employers are often surprised when I ask for less access, but I firmly believe no random employee should have personal data access like this. Ideally you'd want to require the customer to be in the loop to access their data as employee.