sacheendra

For example, only 42% have a passport. https://www.forbes.com/sites/niallmccarthy/2018/01/11/the-sh...

Most countries which are not the Unites States don't have the power to make large scale systematic changes that this requires. It might not be possible even in the US, what with states shipping homeless people to other states and all.

The US government already does something similar for corn. Farmers are paid to not plant it to control market price.

For all practical purposes, it is true.

But the current consensus is that property is not fundamental to the existence of a human. The term property doesn't appear once on https://en.wikipedia.org/wiki/Universal_Declaration_of_Human....

Following your tomato example, you grew the tomato on some land and the plant absorbed nutrients from the land. Who gave your the right to do that? Do you own the nutrients?

How did humans come to own land? Was everybody born with their piece which they chose to trade? Of course not.

What we call property came about over thousands of years due to complex interactions between people. There is a concept of fairness to getting to keep what you made. But, there is nothing simple or fundamental about it.

It is not absurd at all that society thinks you shouldn't have this right if it is at the expense of others. Society can take all the wealth it wants from you if it thinks there is a problem to be solved. Poverty for example.

Taxes are tool at civil society's disposal to tackle problems. Considering them immoral that they should only be used as a last resort is absurd.

It quite funny that we consider property more important than people's lives. In the current political climate, going to warnis easier than rising taxes.

According the benchmark, the fastest 8 GPU node takes about 0.5 seconds. The cost of that node on AWS is about 24$/hour. The 21 node spark cluster takes 6 seconds. But, it only costs 4$/hour.

An additional benefit with Spark is that it can be used for a lot more variety of operations than a GPU.

This cost disadvantage restricts GPU processing to niche use cases.

You can start with serverless, move to normal cloud instances and finally to bare metal or the other way around!

For example, the core value provided by an ERP software is not performance but the business logic. Serverless is a good fit for startups creating such software. If you are running a conference call business or serving tons of video like Netflix, a different architecture better suits your need. Such as having edge servers with every ISP.

ERP applications which use HANA typically do have significant random accesses in their workload. It is due to this reason that it was initially marketed as an in-memory database. The random access performance of RAM was necessary for high performance. If HANA was just being used in in-memory mode, the speed increase is probably not that impressive. But, if there is non-volatile storage involved, then yes the speed increase would be impressive.

It gives the maximum amount of data in space before collapsing into a black hole.

Companies, which are Microsoft competitors in other fields, use Microsoft software such as Windows and MS SQL Server to process and store valuable data. There was always a risk of Microsoft backdooring their software to spy on competitors.

That doesn't happen because 1. Microsoft wants to be in business and 2. Private repositories probably come with legal requirements that GitHub/MS don't spy on users for competitive gain.

Finally, while software such as Wine has been written to liberate some application from Microsoft's platform monopoly, there is also a lot more Open Source software written for other purposes. I don't see them investing the effort to move away from GitHub unless Microsoft does something evil.

Cool factor is just working on cutting edge stuff or with some tech I'm super excited about.

Recognition comes from the community your are doing the project for (team, manager, etc.) recognizing its importance. This typically only happens if you pick projects which solve a business need and communicate that. Preferably lead to higher revenue.

Process is the end to end process of systematic identification of the problem via concrete quantitative metrics, formulating a solution using a scientific process, building the system following sound design principles, etc. It's kind of difficult to concretely define. What it is not is putting out fire after fire everyday.

This is the recipe of successful project I enjoy nowadays.

The recipe changes from person to person and time to time. The way to figure out your recipe is to introspect. Cut out the noise of FOMO, hyped tech, etc.

A good article I have read recently about deciding what you want is https://waitbutwhy.com/2018/04/picking-career.html. This will explain how to introspect in great detail.

Java 9 and 10 will still be free for commercial use until further notice.

For 100s to 1000s of servers. The cost starts mattering.

I'm not saying new applications shouldn't be built on lisp. Most applications don't have huge scaling requirements. But, if you expect the application to grow, have a plan in place for migration.

But, this article gives one of the reasons for avoiding its use in a high performance production environment. Provisioning a VM with over 25GB RAM for an application which requires about 4GB of it is a huge waste of resources.

While the common wisdom on HN is that for most applications, developer costs more than physical resources. Physical resources still cost money.

Initially list might be a good option for development velocity. But, over time as the application matures, adding features becomes more complicated and the velocity goes down anyway. Shifting to something which reduces costs by upto 6x might be worth it.