452 karma · joined September 23, 2019
While not discounting how good coreutils are, everything you've listed is basically a commodity at this point.
Companies who live higher in the stack swoop in and claim all of the value.
If you don't want to pay for it, why would somebody else?
It's strongly tied to economic growth, and thus everybody's pensions are tied up in the success of advertising. It seems illogical it makes such an obscene amount of money, but collectively the advertising industry is bigger than even oil & gas.
Now I don't exactly enjoy ads, I accept a few, but every time they're implemented the pressures of the market just increase it over and over until it ruins the base product, like a cancer.
What's the alternative?
Consumers don't have enough money to pay for dozens and dozens of subscriptions. The ads industry is effectively a tax on every other industry, and thus makes more money than consumers would ever spend on content. I'm open to ban advertising entirely but that also seems like an opposite extreme and counterproductive.
Coming at this from a UK perspective, housing is a nightmare here too. But our green belt is at an all time low and London is an unbelievable sprawl. No, I'd rather rent forever than ruin the countryside.
- Google Cloud Run (or anything that can run docker)
- SendGrid (but use SMTP only for easy migration)
- Google Workspace (Office/Notion are also cool but I just don't use them often)
- Mainly Go with Python for scripts
- PostgreSQL
- gRPC/Protocol Buffers for API servers
Where possible I try and take on as few dependencies on big cloud services, and always use standard gateways. It makes moving around much easier. Other stuff mentioned here is quite good, but I'll especially recommend https://IndieHackers.com
Very little can be controlled for in studies like this. There are just too many factors to slice on, and before long you're just reading into noise.
You can be "theoretical physicist smart" without being a theoretical physicist.
This is completely backwards. Demand is highly price inelastic and inversely correlated with the supply of renewables. People usually eat at night. They heat their homes overnight. None of these things will change based on energy prices.
What you're proposing is a tax on the poor, and no practical benefit to boot.
> The charger for your electric car is another very practical sink for cheap electricity.
I don't have an electric car. I do not know anybody with an electric car. And wouldn't the surplus show up specifically when those cars aren't at the home?
> A battery consisting of a pile of rocks can't be expensive.
No, but the labor cost of hooking up your pile of rocks battery will be impractical for almost everyone.
> The next level is using residential HVAC systems the same way.
Again, I don't know anybody with an HVAC system. Everything here in the UK is based on natural gas and would cost an unbelievable amount of money to replace with electric.
I'm not denying that, but all the same, we're not talking about thousands of separate codebases. It's a single monorepo codebase with consistent styling, the advantage being that people can switch teams or contribute to other Google software under the same style guide.
The overhead isn't a bug, it's a core feature as consistent style makes it that much easier to switch teams.
I don't see why not.
It has an interface for input and output, conforms to well known specifications and is publicly documented.
There's also multiple implementations behind the API.
And that's an acceptable trade-off for a different sized company. Google arguably has the biggest centralised codebase in the world, and simply has different requirements.
As other have said, most of the overhead is from attaining readability, not the requirement itself.
FWIW, these can be the same person - if the have appropriate readabilities. The problem is that it's not easy to get readability in the first place, so occasionally teams have to look for people outside.