HNHacker News
TopNewBestAskShowJobs

evidencetamper

69 karma · joined February 3, 2025

submissionscomments
evidencetamper··on Users don't care about your tech stack
I heavily dislike GraphQL for all of the reasons. But I'll say that for a lot of developers, if you are already setting up an API gateway, you might as well batch the calls, and simplify the frontend code.

I don't buy it :) but I can see the reasoning.

evidencetamper··on Users don't care about your tech stack
It's true, and of course, all models are wrong, especially as you go into deeper detail, so I can't really argue an edge case here. Indeed, C++ is rarely the best answer. But we all know of trading systems and gaming engines that rely heavily on C++ (for now, may Rust keep growing).
evidencetamper··on Users don't care about your tech stack
This is a mixed bag of advice. While it seems wise at the surface, and certainly works as an initial model, the reality is a bit more complex than aphorisms.

For example, what you know might not provide the cost benefit ratio your client would. Or the performance. If you only know Cloud Spanner but now there is a need for a small relational table? These maxims have obvious limitations.

I do agree that the client doesn't care about the tech stack. Or that seeking a golden standard is a McGuffin. But it does much deeper than that. Maybe a great solution will be a mix of OCaml, Lua, Python, Perl, low latency and batches.

A good engineer balances tradeoffs and solves problems in a satisfying way sufficing all requirements. That can be MySQL and Node. But it can also be C++ and Oracle Coherence. Shying away from a tool just because it has a reputation is just as silly as using it for a hype.

evidencetamper··on Greg K-H: "Writing new code in Rust is a win for all of us"
Those are the tradeoffs, and it seems to me that Linux doesn't have to run in everything under the Sun as Doom ports do, and there might be other kernels that are better suited to such cases.
evidencetamper··on A better (than Optional) maybe for Java
You don't need your optional to be serialized - it's just a container. You need what's inside your optional to be serialized.
← PreviousPage 2 of 2