Hacker Newsnew | past | comments | ask | show | jobs | submit | tharakam's commentslogin

"It is not really true that DNS is for people only" Yes, "Any problem in computer science can be solved with another level of indirection... except for the problem of too many layers".

DNS is one mechanism of adding a layer of abstraction.


No disagreement there, but this layer of abstraction (mapping names to unique numeric machine identifiers) seems unavoidable for the most part: even the OP does not propose doing away with it, just replacing one tech with another (eg. DNS with /etc/hosts).

So let's not make a general argument when there are specifics to be discussed — do you have an argument for why mapping names to IDs is an abstraction too much here?


I can relate to this article. My reaction to what is happening is also: "Leave me behind".

However, missing the joy of the old-school way of growing as a developer is not only the wrong reason, but also very dangerous according to Darwin.

Our customers don't care about how it is made after all, but they do care about long-term support, costs, and predictability, etc.

But I'm not sure whether we can say we made a real net positive progress in the industry. The whole thing is a big mess. In many cases, AI moves us in the same direction in turbo mode, making it not only messier and more expensive but also dangerous.

I tell them, "Leave me alone", as I see this mess as an opportunity if you think the right way, starting from the first principles.


Maybe our customers do care about how it's made.

I guess it is clearer if expressed like "Native application took only x% of WASM equivalent".


Yes. A short video I watched mentioned that even touching these thermal papers with normal gloves is unsafe.


The receipts that a large majority of humanity has been handling on a daily basis for decades? Unsafe? In what way?


I'm doubtful it's a majority.


I expected something Semantic Web-related. https://www.w3.org/OWL/


Exactly! lol


IMO, is this Good advice for hacker news itself. It contains diverse topics in one stream, such as history, Botany, and Coding. You can argue it is a feature or a bug.


In almost every way imaginable, I think this is counter-productive. This is just shallow thinking of the policymakers. Do they think human productivity works like machines in a factory? Good luck!


Those images have only a little commercial use IMO.


I'm confused. Everything sounds very expensive to me.

The last table which compares it with the other vendors is surprising. Even Stich Data (cheapest) costs $1 to move 240K records: (1B / 4,166.67 = 240K). Is this real?

So, their solution costs $1 to process 13.6M records. Sounds like this is not very share-worthy.

What I'm missing here?


What I want to know is why the fuck it takes 8 days to load 700MM records—in 2024.

I couldn’t even continue reading the article because it must be from 2006.


700M records in 8 days (1024 rps) is to mimic a real-world transactional (OLTP) workload. It doesn't define limits on what throughput can be achieved.


Ahhh. Thank you. That makes more sense.


Welcome to 2024 and the generation of developers raised in the cloud native world who think this is normal.

A billion rows is nothing and having $100 appear in conjunction with that is absurd unless you are doing some kind of really heavy compute or AI model training on that data.

By 2030 we’ll have those costs well up over a thousand dollars and it’ll take five or six separate SaaS systems wired together to do this. Progress!


To be fair, my machine that can process 1B rows an unlimited number of times still cost $1000 to build, so if you need a one off maybe paying the $100 is better?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: