HNHacker News
TopNewBestAskShowJobs

asa400

1,194 karma · joined April 10, 2013

submissionscomments
asa400··on Why I Chose Elixir Phoenix over Rails, Laravel, and Next.js
The size of the diff and the latency of the underlying transport layer are independent. If your user in NY clicks a button that has to go to your server in SF, you pay for that ping both NY->SF and SF—>NY for the reply.

Same goes for whether they’re on some flakey mobile connection in a car or on a train.

It’s also super easy to accidentally send a ton of data down the wire on component mount. I worked on a massive LiveView app at a company you’ve heard of and these kinds of issues were a problem the whole time.

You also give up the standard stateless HTTP request/response model when you go with LiveView. This is not necessarily bad, but people should be aware that they’re turning their stateless web tier into a stateful web tier. It’s an entirely different model (and in my opinion, more challenging).

LiveView is cool technology but I don’t want people to overlook the fact that it has some sharp edges you have to be aware of when building large products.

asa400··on I audited 47 failed startups' codebases
What languages would you start with, and what languages would you change to?
asa400··on Svelte’s characteristics that likely contribute most to improved performance
Thanks for the detailed response.
asa400··on Svelte’s characteristics that likely contribute most to improved performance
Serious question: is rendering throughput as much of an issue today as it used to be?

I feel like CPUs have gotten a ton faster while bundle sizes have gotten larger and mobile networks still have a ton of latency, so network matters more in the scheme of things.

Would love to hear other perspectives, though!

asa400··on The RSS feed reader landscape
If you're looking for an on-device terminal feed reader, here's mine: https://github.com/ckampfe/russ

Some folks seem to like it.

asa400··on The murky economics of the data-centre investment boom
Almost doesn’t matter what Google’s short term unit economics on AI are as long as their shareholders and board are OK with it. Google makes money hand over fist and can afford it. Microsoft is fine, Oracle is fine, TSMC is fine. These other shops are leveraged to the hilt, so they’ll be in a world of hurt if people stop buying, financing, or investing.
asa400··on A comparison of Ada and Rust, using solutions to the Advent of Code
Not the OP but I'll take a stab: I see "waiting faster" as meaning roughly "check the status of" faster.

For example, you have lots of concurrent tasks, and they're waiting on slow external IO. Each task needs its IO to finish so you can make forward progress. At any given time, it's unlikely more than a couple of tasks can make forward progress, due to waiting on that IO. So most of the time, you end up checking on tasks that aren't ready to do anything, because the IO isn't done. So you're waiting on them to be ready.

Now, if you can do that "waiting" (really, checking if they're ready for work or not) on them faster, you can spend more of your machine time on whatever actual work _is_ ready to be done, rather than on checking which tasks are ready for work.

Threads make sense in the opposite scenario: when you have lots of work that _is_ ready, and you just need to chew through it as fast as possible. E.g. numbers to crunch, data to search through, etc.

I'd love if someone has a more illustrative metaphor to explain this, this is just how I think about it.

asa400··on Benefits of choosing email over messaging
I’ve often wondered why forums never took off at any of the companies I’ve worked at. Has anyone else worked at companies that had forums?

All I worked at had email and chat, and some had wikis, but never forums, despite having crucial advantages over email (anyone who joins later can search them) and wikis (they’re conversations rather than mutable, outdated documents) and chat (they can’t interrupt you).

asa400··on A comparison of Ada and Rust, using solutions to the Advent of Code
Another way of thinking about this is whether you want to optimize your workload for throughput or latency. It's almost never a binary choice, though.
asa400··on OpenAI's H1 2025: $4.3B in income, $13.5B in loss
I'm not saying you're wrong, but people said the same thing about Yahoo, Excite, Lycos, etc. in 1999. Interesting times, then and now.
asa400··on OpenAI's H1 2025: $4.3B in income, $13.5B in loss
What is OpenAI's competitive moat? There's no product stickiness here.

What prevents people from just using Google, who can build AI stuff into their existing massive search/ads/video/email/browser infrastructure?

Normal, non-technical users can't tell the difference between these models at all, so their usage numbers are highly dependent on marketing. Google has massive distribution with world-wide brands that people already know, trust, and pay for, especially in enterprise.

Google doesn't have to go to the private markets to raise capital, they can spend as much of their own money as they like to market the living hell out of this stuff, just like they did with Chrome. The clock is running on OpenAI. At some point OpenAI's investors are going to want their money back.

I'm not saying Google is going to win, but if I had to bet on which company's money runs out faster, I'm not betting against Google.

asa400··on Leaked Apple M5 9 core Geekbench scores
I have an M1 Max and I'm curious, do you notice any difference in battery life/power usage?
asa400··on Leaked Apple M5 9 core Geekbench scores
Same here. I have an M1 Max with 64GB and the only time I notice a slowdown is doing Rust release builds with `lto = true` and `codegen-units = 1`, which makes complete sense. Otherwise there is _plenty_ of multicore performance for debug builds, webdev, web browsing, etc., often all at once.
asa400··on The allure of new languages vs. the necessity of problem-solving
Yeah, I find the notion that coreutils is so proven and solid that it can't possibly be improved in any way to be utterly ridiculous. And I'm not even saying Rust necessarily has to be the thing to do it.

I just don't believe "pile of old C" is any kind of strong indicator of quality or performance, positive or negative.

asa400··on The allure of new languages vs. the necessity of problem-solving
Excellent comment.

  > People like to complain that writing correct Rust is hard. Thats's true, particularly for novices. But you'll get better. Thing is, writing correct C++ code isn't exactly easy either.
Agreed, and I wish all of the "Rust is hard" people would offer this critique _in context_.

The question is not "is Rust harder than C or C++?". The question is, "is writing correct Rust harder than writing correct C or C++?".

You could even think of it in financial terms: "is the cost of writing correct Rust higher or lower than the cost of writing correct C or C++?".

Another interesting qualification to add on is: "...for someone who doesn't already know Rust or C or C++". If you had to onboard a new team member, and they didn't know Rust or C or C++, which language would you want your project to be in? Which would they be able to safely contribute to the fastest? I know what I'm picking.

asa400··on Is Zig's new writer unsafe?
The parent quite literally made a normative statement and I disagreed with it:

  > Collaborating would be contacting the Zig team through one of the many channels available and asking questions, offering suggestions etc.
If nothing else, this is attempting to define what counts as valid collaboration, and it's a definition I reject, so I disagreed with it. Good-faith experience reports are valid, useful, pro-social collaboration. Doing so is a perfectly productive way to criticize.

  > So what was the point in saying this? Do you think people believe anything contrary to what you said?
Apparently they do. The parent even made a veiled accusation that the author writing a good-faith blog post on their own blog about their own experiences "can even be seen as self promotion". Since when is sharing your good-faith critique about the design of a tool you've used something underhanded or nefarious?

Setting the bounds of valid community collaboration to "people can post on their own blog as long as I like it otherwise they're being mean" is not a set of values I subscribe to, so I felt it was worth it to articulate that.

asa400··on Is Zig's new writer unsafe?
Nah, this is absurd. This guy or anybody else can write whatever they want, whenever they want, on their own blog. They are under zero obligation to create bug reports, file issues, check in on a chat channel, or contribute in any other way to an open source software project that does not employ them. Writing blog posts is a perfectly reasonable and normal community behavior.

The members of the Zig project are free to reach out to the author!

When you create a project in public people will write about it, tweet about it, complain about it, etc (if you’re lucky!).

asa400··on In Defense of C++
Not that npm-style package management is the best we can do or anything, but I would be more sympathetic to this argument if C or C++ had a clearly better security story than JS, Python, etc. (pick your poison), but they're also disasters in this area.

What happens in practice is people end up writing their own insecure code instead of using someone else's insecure code. Of course, we can debate the tradeoffs of one or the other!

asa400··on In Defense of C++
Just think of how many _more_ vulns C and C++ could be responsible for if they had package modern managers! :)
asa400··on When the job search becomes impossible
Speaking of networks, hey Joe! Clark from Belly. Hope you're doing well!
asa400··on Rust: A quest for performant, reliable software [video]
The talk touches on this notion specifically. The author notes that it's intentionally clickbait.
asa400··on Why our website looks like an operating system
I played around with this for a while and couldn't actually derive any useful information from it.

As someone who doesn't know posthog, this was basically impossible to navigate. The UI and theme is cool, the widgets are fun and well styled, but I couldn't actually figure out what I was supposed to be doing, what I was supposed to be reading, what meaning I was supposed to take away about a company (I'm guessing) that makes products (again - guessing).

asa400··on Clojure's Solutions to the Expression Problem
Yep pretty much. It’s “open world” polymorphism.
asa400··on Run Erlang/Elixir on Microcontrollers and Embedded Linux
Yes - Erlang/Elixir wouldn't be the bound here. 90s hardware is plenty for them. They were designed for far less.
asa400··on Next.js is infuriating
Folks will deal with all of this crazy stuff just to avoid using Ruby on Rails, Phoenix, Django, etc. Why? Is Next.js that much better for the user? I doubt it.
asa400··on AI adoption linked to 13% decline in jobs for young U.S. workers: study
Stuff that isn’t pure SaaS. Physical products that benefit from hands on interaction with customers, worksites, and other internal producers. Small and/or local businesses that want someone whose face they can see in person.
asa400··on Beginning 1 September, we will need to geoblock Mississippi IPs
Ever spent any time in Houston, Los Angeles, Miami, San Jose, Casper, Traverse City, Nashville, New York, Buffalo, New Orleans, Cortez, Lubbock, Chicago, Salt Lake City, Minneapolis, Jackson, Boston, Seattle?

In your mind, are these all filled with people who look the same, sound the same, practice the same religion, immigrated from the same place?

asa400··on Beginning 1 September, we will need to geoblock Mississippi IPs
> The US doesn’t have 50 different cultures with totally different values...

Indeed. It has far more than that. The US is astonishingly diverse.

asa400··on Unexpected productivity boost of Rust
Correct. If you then want to subsequently re-reference or dereference that reference (this happens sometimes), you'll need to accordingly `&` or `*` it, but if you're just using it as is, the bare syntactical `name` (whatever it happens to be) already refers to a reference.
asa400··on Unexpected productivity boost of Rust
I'm not sure how what you're describing is different from passing an immutable/shared reference.

If you call `foo(&value)` then `value` remains available in your calling scope after `foo` returns. If you don't mutate `value` in foo, and foo doesn't do anything other than derive a new value from `value`, then it sounds like a shared reference works for what you're describing?

Rust makes you be explicit as to whether you want to lend out the value or give the value away, which is a design decision, and Rust chooses that the bare syntax `value` is for moving and the `&value` syntax is for borrowing. Perhaps you're arguing that a shared immutable borrow should be the default syntax.

Apologies if I'm misunderstanding!

← PreviousPage 6 of 10Next →