Because end users don’t have any ability to avoid sites that use Cloudflare, and it’s free advertising every time a developer sees it. Sure, you might hate Cloudflare on everyone else’s sites, but it’s nice to have it on your side!
> I think every time I log in to GitLab I get a Cloudflare check.
This is almost certainly GitLab’s doing (though you can ultimately blame irresponsible AI scrapers). Site owners can control how often you see CF captchas.
He says brown is perceived when you see an orange-wavelength light that is significantly darker than its surroundings, providing the necessary context for your brain to interpret it as brown.
Genuine question: what’s your use case for having a single SF Symbols icon as a PDF file? Let alone having that as the default? In my own experience, I’d want SVG nearly every time.
You're right. Just flipped the default to SVG on main. Honest answer: SVG wasn't fully working during early dev, so PDF was the working default and it stuck. Should've revisited.
What you’re describing would be a completely unusable terminal. You’d lose things as basic as the backspace key. And what’s wrong with Terminal.app indicating when it’s suppressing output?
Terminal.app does not suppress output in my example.
The ssh command switches the terminal into no-echo mode with termios flags.
Terminal.app, being clever, watches for disabled echo (among other things) and assumes a password is being entered and displays the key icon and enables Secure Event Input.
Another barely usable website from the "National Design Studio." I wish they'd take a cue from gov.uk (or even the US Digital Service and 18F, which they gutted) and build clean, functional, and accessible sites... but the crew of web developers who are willing to work for this administration seem way too obsessed with this defense-tech startup landing page aesthetic to care about usability.
The developer of this scroll-smoothing JS library [1] has a lot to answer for.
> Just wait until there are entire classes of vulnerabilities related to LLM usage
This is a valid concern.
There are going to be a new class of vulnerabilities which an LLM is involved which are going to be discovered and it will make it possible to cause catastrophic damage to a company; very easily.
This won't be surprising since we have companies building casual remote code execution tools for "agents" waiting to be hijacked.
I understand that. What about that relates specifically to the Android CLI? That was rafram's question, and mine, and as far as I can tell still hasn't been answered.
I mean, I guess if you're going to say "don't use LLMs", then you also don't want to let agents use the Android CLI, but it seems like raising an awfully general concern in a discussion about a very specific article.
The US still enforces copyright law on song distribution which is the big difference. It basically requires a middleman (like spotify) that soaks up all the revenue from that distribution while giving almost nothing back to the artists.
reply