HNHacker News
TopNewBestAskShowJobs

saint_yossarian

281 karma · joined April 2, 2022

submissionscomments
saint_yossarian··on How Israeli actions caused famine in Gaza, visualized
More details here: https://en.wikipedia.org/wiki/Israeli_support_for_Hamas
saint_yossarian··on Ask HN: Went to prison for 18 months, lost access to my GitHub. What can I do?
You can use a TOTP authenticator with backup support (I use Aegis on Android, and less critical ones in Bitwarden), and backup your recovery codes.
saint_yossarian··on Neovim Pack
Well kickstart.nvim is a template for your own configuration, not a distribution. You're not supposed to update it.
saint_yossarian··on Neovim Pack
AFAIK using setup() is actually a cargo-cult practice and discouraged by the Neovim maintainers.
saint_yossarian··on Amazonq.nvim: Official AWS AI Assistant Plugin for Neovim
From the README:

> After installation, authenticate through IAM Identity Center or AWS Builder ID.

saint_yossarian··on I Don't Have Spotify
They started skipping some months. Check https://isitbandcampfriday.com/ for the next one.
saint_yossarian··on I Am An AI Hater
What evidence convinced you?
saint_yossarian··on Rv, a new kind of Ruby management tool
Wait, how do you get precompiled Rubies with mise? I still have to compile with default settings, and the docs only mention that it uses ruby-build behind the scenes: https://mise.jdx.dev/lang/ruby.html
saint_yossarian··on Writing with LLM is not a shame
While your breakdown of LLM “benefits” is thorough, I think it glosses over—or outright ignores—some significant limitations and trade-offs that make the picture far less rosy. It’s easy to frame this technology as an unqualified upgrade to human writing, but that framing is misleading and potentially harmful. Let me go point by point through your categories and explain where the problems lie.

1. Enhanced Productivity

Yes, LLMs can produce text quickly, but speed is not synonymous with quality. Churning out a draft in seconds is only useful if that draft actually advances the writer’s ideas, rather than lulling them into outsourcing thought itself. What often happens is that people mistake “having words on a page” for “having meaningful ideas.” Productivity in writing is not about word count—it’s about clarity of thought, and clarity is something that an LLM cannot supply. It can rearrange existing patterns, but it cannot truly reason or generate original insight. A fast draft is worthless if it’s hollow.

2. Improved Writing Quality

This point assumes that grammar and surface-level polish are the essence of good writing. They are not. Good writing emerges from the writer’s voice, their personality, their quirks, even their mistakes. Grammar-correcting AI tends to standardize expression into a bland, middle-of-the-road prose style. The result is “correct,” but sterile. Moreover, “tone adjustment” and “clarity” are superficial facsimiles of understanding. Simplifying an idea is only valuable if you understand what makes it complex in the first place. AI doesn’t “understand” ideas—it flattens them into patterns of words that look simpler but may remove nuance in the process.

3. Creativity and Ideation

Here is where the hype is the most exaggerated. Brainstorming with an LLM often produces generic, cliché, or predictable results. If you ask for metaphors, you’ll get the most common ones floating around in its training data. If you ask for plots, you’ll get reheated versions of existing tropes. Calling this “creativity” misunderstands what creativity actually is: the human capacity to connect disparate, personal experiences into something novel. An LLM is bounded by statistical averages. It cannot be surprised by itself. Humans, on the other hand, can.

4. Language Versatility

Translation and localization are areas where LLMs seem promising, but again, nuance matters. Language is not merely about syntax or vocabulary; it is deeply cultural, contextual, and historically embedded. Machine translation may be “good enough” for casual use, but it consistently fails to capture subtext, irony, humor, idiom, or cultural resonance. Outsourcing too much of this to AI risks flattening linguistic richness into something utilitarian but impoverished.

5. Research Assistance

This one is especially dangerous. Yes, LLMs can summarize and generate context, but they are notorious for producing confident-sounding misinformation (“hallucinations”). Unless the user already has expertise in the topic, they will not know whether what they’re reading is accurate. This means that instead of empowering research, LLMs encourage intellectual laziness and misinformation at scale. The “citation help” is even worse: fabricated references, garbled bibliographic entries, and misleading formatting are common. Presenting this as a “benefit” is disingenuous without an equally strong warning.

6. Editing and Rewriting

Paraphrasing and consistency checks may sound helpful, but they too come at a cost. When you outsource the act of rewriting, you risk losing the friction that forces you to refine your own ideas. Struggling to find words is not a flaw—it’s part of thinking. Offloading that process to an algorithm encourages passivity. You end up with smoother sentences, but not sharper thoughts. “Consistency” is also a double-edged sword: AI can enforce bland uniformity where variation and individuality might have been more compelling.

7. Customization and Integration

This is just another way of saying “industrialization of writing.” The more writing is engineered through prompts and APIs, the more it shifts from being a human practice to being an automated pipeline. At that point, writing stops being about human connection or expression and becomes just another commodity optimized for scale. That’s fine for spam emails or ad copy, but disastrous if applied to domains where authenticity and trust actually matter (e.g., journalism, education, or literature).

8. Cost Efficiency

Framing this as a cost benefit—“reduces need for human writers”—is perhaps the most telling point in your list. This reduces writing to a purely economic function, ignoring its human and cultural value. The assumption here is that human writers are redundant unless they can outcompete machines on efficiency. That is not just shortsighted; it’s destructive. Human writers don’t merely “generate content”—they interpret, critique, and shape culture. Outsourcing all that to probabilistic models risks a future where the written word is abundant but devoid of depth.

The larger issue is that your entire framing assumes writing is merely a transactional process: input (ideas or tasks) → output (words on a page). But writing is not just about producing text. It is about thinking, communicating, and connecting. By presenting LLMs as a categorical improvement, you erase the most important part of the process: the human struggle to articulate meaning.

So yes, LLMs have uses, but they should be treated as narrow tools with serious limitations—not as the new standard for all writing. To present them otherwise is to flatten human expression into machine-mediated convenience, and to celebrate that flattening as “progress.”

saint_yossarian··on Using Podman, Compose and BuildKit
Must have been ages ago, even stable now has 5.4: https://packages.debian.org/search?searchon=names&suite=all&...
saint_yossarian··on Anthropic's CEO says in 3-6 months, AI will write 90% of the code (March 2025)
You're probably thinking of https://github.com/ghuntley/cursed. It... certainly seems to live up to its name.
saint_yossarian··on AI is different
How many of those rides required human intervention by Waymo's remote operators? From what I can tell they're not sharing that information.
saint_yossarian··on Model intelligence is no longer the constraint for automation
One thing that comes to mind: You still have to verify that the tests are exhaustive, and that the code isn't just gaming specific test scenarios.

I guess fuzzing and property-based testing could mitigate this to some extent.

saint_yossarian··on What does Palantir actually do?
They literally advertise a "AI-powered kill chain". See https://www.palantir.com/platforms/gotham/
saint_yossarian··on Debian 13 “Trixie”
It's a systemd thing, see `man systemd-tmpfiles`.
saint_yossarian··on AccuWeather to discontinue free access to Core Weather API
Here's a convenient list: https://github.com/breezy-weather/breezy-weather/blob/main/d...
saint_yossarian··on Cloudflare Introduces Default Blocking of A.I. Data Scrapers
I remember using mod_security with Apache long ago for some of this, looks like it's still around and now also supports Nginx and IIS: https://modsecurity.org/
saint_yossarian··on Canyon.mid
Yes, there was even a <bgsound> HTML tag to play MIDI files, which was heavily used in places like Geocities.
saint_yossarian··on Agentic Coding Recommendations
The Neovim plugin CodeCompanion is currently moving into a more agentic direction, it already supports an auto-submit loop with builtin tools and MCP integration.

Yes it's not a standalone CLI tool, but IMHO I'd rather have a full editor available at all times, especially one that's so hackable and lightweight.

saint_yossarian··on Self-hosting your own media considered harmful according to YouTube
> Herd immunity can only be achieved if a sufficiently large part of the population is vaccinated.

...or getting infected, of course.

saint_yossarian··on Hacker News now runs on top of Common Lisp
It does support the userContent.css file in the profile, there's just no UI for it.
saint_yossarian··on GTK Krell Monitors
https://extensions.gnome.org/extension/3010/system-monitor-n... is good.
saint_yossarian··on Sapphire: Rust based package manager for macOS
https://mise.jdx.dev/ supports uv through its pipx backend, and is a very good package/tool manager in general.
saint_yossarian··on Study finds solo music listening boosts social well-being
hdtracks.com has a pretty big catalog, but is sometimes a bit expensive.
saint_yossarian··on AI image recognition detects bubble-like structures in the universe
It's blocked by "EasyList – Newsletter Notices", the annoyances lists are often a bit too aggressive.
saint_yossarian··on New in Gmail: Making E2E encrypted emails easy to use for all organizations
ProtonMail downloads the whole mailbox to browser storage to support fulltext search.
saint_yossarian··on A love letter to the CSV format
Also VisiData is an excellent TUI spreadsheet.
saint_yossarian··on Revenge of the Junior Developer
That's just another type of test, the question was who's going to check that the tests are actually testing the correct things. Maybe look up the Therac-25 that was mentioned.
saint_yossarian··on “Vibe Coding” vs. Reality
Sure, but writing those is just coding in a fuzzier and more verbose language.
saint_yossarian··on OpenAI Audio Models
Thanks, that's interesting. I thought service workers were only needed for things like offline support and background activity after a tab is closed (which is why I disabled them).

Streaming audio is a new one to me, I wonder if the same could be achieved with web workers instead. Or at least similar use cases like video calls work fine for me without service workers. See e.g. https://github.com/scottstensland/web-audio-workers-sockets

← PreviousPage 3 of 6Next →