Recent submissions

Comment · 3 years ago
Peasants have unemployment insurance. If government is supposed to pay something on top of it, why do we even have unemployment benefits to begin with?
Comment · 3 years ago
The goal of saving is to have a lifestyle that you can MAINTAIN during retirement.

- if you save 60% of your income, your lifestyle will be severely damaged and you won't become a spender all of a sudden the day after retirement.

- If you save 5% of your income, then you won't be able to lower your lifestyle once you retire.

Saving 15/20% of income isn't a magic number. But it's something that doesn't damage your lifestyle + it accumulates to a meaningful amount that saves your ass in old times.

Going aggressive in either direction (spending or saving) is not the right mindset, because you won't be able to CHANGE once you adopt a specific lifestyle.

Comment · 4 years ago
>Startup are a none issue

Yes it is. Developing any short term job -- that runs multiple seconds and goes away -- like lambda or k8s jobs with Java is meaningless for exactly this reason. The startup time is longer than the run time.

Comment · 4 years ago
Simply because blast radius for Java is limited to a set of very high quality libraries -- in terms of code not functionality. These libraries come from Apache Foundation, Eclipse Foundation, Google, Facebook, Spring, etc. Literally every single Java application depends on something from Apache [ok I understand stuff like Log4Shell can still happen].

The same is not true for JS. The most mature libraries depend on absurdly vague libraries that no one has ever reviewed.

Comment · 5 years ago
I don't know why this is being down voted. The entire modern bullshit Internet exists because of NAT. We can't host stuff ourselves and have to use some central system. Since nothing is free, the provider has to inject more and more ads everywhere.
Comment · 5 years ago
EVOO, Ghee (from grass fed butter), Coconut oil, Avocado oil, Sesame oil, Tallow, Lard and Butter (from grass fed animal) is all that you should be eating. Everything else belongs to trash bin.
Comment · 6 years ago
I personally think this is the only reason causing work force depreciation among software engineers. If shit is changing every six months, then keeping up with changes should be part of the job, not part of the weekend.
Comment · 6 years ago
If tourism + aviation is profitable combined, then why should we care? It's like Sony is not profitable by selling play station hardware. But game business unit is profitable because subscription income covers the hardware loss.
Comment · 6 years ago
Build taller. Skyscraper has been invented long time ago.
Comment · 6 years ago
Even if it's half cheaper, a family house of 80-100m^2 costs beyond 600K which is way beyond affordability range of a couple both working as software engineers let alone people with non-tech jobs.
Comment · 6 years ago
Sure. Happiest countries are in Europe with highest suicide as well. What sort of happiness is that?
Comment · 6 years ago
I live and work in Munich and I have to pay half a million euros for a 25m^2 box. EU is cheaper than US is a fallacy.
Comment · 6 years ago
Network is faster than disk. Once cached, then you are only bound by network IO for subsequent uses.
Comment · 6 years ago
That's true but still limitation is not fully resolved. In order to increase consumption rate, we need to add replicas. In pulsar Brokers are merely cache nodes over Bookkeeper. Adding more Brokers is trivial in Pulsar.
Comment · 6 years ago
There are real differences among them. Here is some painful aspects of Kafka:

1. A single partition is stored in one node (replicas on another nodes). With this, introducing new nodes takes very long time to replicate large partitions, because it can replicate one partition from only one node (leader of the partition). On Pulsar each segment of partition is stored in a different bookkeeper node.

2. Because of 1, if two consumers read different parts of a partition that are far from each other, they will compete over disk bandwidth. In Kafka consumer can not read from replica node. If a topic is really popular and many consumers try to read from it (from different parts of the file which makes OS page cache useless), total consumption rate is limited to disk bandwidth of a single node. But in Pulsar each consumer can read from different brokers. Catch up consumers won't trash streaming consumers in Pulsar.

These are not problems that can be fixed easily. Additionally, in the realm of streaming the difference between Flink and Spark is day and night. The low watermark feature that Flink offers makes them behave fundamentally different.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton