JonathanBeuys

Ok, let's say 25% growth over 10 years. That is a factor of 9.

9*$50B = $450B yearly revenue.

What could be the margin Alphabet makes from that? Last quarter, Alphabet had $100B revenue and $35B net income. So 35% margin.

$450Bx0.35 = $158B

What is $158B in annual profit worth? Currently Alphabet's p/e is about 30. If we take that, it would be $158Bx30 = $4740B. So around $5T.

If we are heading towards the creation of $5T in value via cloud revenue, investing $100B per year to build it seems not particularly high to me.

Is cloud usage really high?

Look at all the stuff people do. Almost none of it is automated via software. Look at people on construcion sites, cashiers, cleaning stuff, cab drivers ... all of it is done manually. I am writing this manually, even though I would prefer to just say it while doing the dishes. But there is no good voice interface for browsers yet. And hey, why do I even do the dishes?

I would say we haven't even started automating the world via software.

10 years of 30% growth just means we will spend 14x more on software in 10 years than we do now. Considering we have not even really started using software for automating work, I would be surprised if we stay below that.

I would think that no matter what the percentage of AI in the revenue is - mankind keeps automating their work via software. And so far, we automated only very little. We probably can keep increasing it at 30% pa for 10 years. That would mean we just automate 14x more than we do now. In 10 years, that seems not even fast to me.

Do I understand your logic correctly that after 14 years of 30% growth another year is extremely unlikely and after 14.99 years it is almost impossible?

My logic is that we only have to take the next 10 years into account when calculating the probability.

And lots of things grew 30% or more for 10 years.

Bitcoin's market cap grew over 70% pa for 10 over years now.

Amazon's revenue grew over 60% pa for over 10 years in their early days.

I can think of many numbers, but would have to check: global solar installations, smartphone usage are examples that come to mind.

Which additional details would you like to see?

According to Perplexity because instead of going through 20 earnings reports myself, I outsourced the task to Perplexity and then manually checked a few of the numbers to be reasonably sure they were correct.

The way I understand the gunicord documentation, this has the same effect as if you set up a script which listens for file changes and restarts the server (or workers) every time a file changes.

That's way less efficient compare to how PHP handles it.

I don't want processes to be killed and new ones to be started every time I change a file.

PHP does it the right way: Only when a request that touches outdated code hits the server is that outdated code reparsed. As long as you just edit files, it uses up no resources at all.

If it does not access the opcache, against what is it checking the last modified date?

True. I see a "Zend OPcache" section in my phpinfo().

It says:

    Cache hits   4746528
    Cache misses   38875

Both values go up every time I execute phpinfo().

I wonder why. Shouldn't "Cache misses" only go up when a source file is changed?

When a framework "supports auto-restart", that usually means it has its own webserver for development and the auto-restart is supported when you use that.

I don't like having a different webserver in development and production.

Imports are also updated the moment you update the imported file.

I'm not sure if PHP stores any compiled binary or byte-code at all. Maybe it compiles it all on each request. It's super fast though, even with tons of imports.

My guess would be that it keeps compiled versions of each file in memory and on each request, it walks down the whole import path. And when it encounters a changed import, it compiles only that one.

Would be cool if someone with more knowledge could shed a light on what is actually happening.

You talk about performance, but I think that is another point for PHP. In my experience, PHP handles the same requests faster.

Yes, I could build everything from scratch myself in Python and have the same statelessnes as in PHP. But parsing headers, creating headers etc feels like it should be handled by a framework. In PHP, it is build right in.

And if I would build it, it would talk to the webserver via CGI. But I think CGI is slow. For PHP, you have mod-php which is super fast.

Even though I prefer Python over PHP, for web projects, I'm probably down with PHP forever. Because it so nicely supports stateless request handling without long running processes.

In PHP, you can just throw a php file on a webserver and it works. To update, you just update the file. You don't have to restart anything.

On the dev machine, you can just have Vim in one window and Firefox in the other, change code, hit F5, and you see what you did.

I don't like having to run a code watching process which then recompiles the whole codebase every time I save a file.

HTTPS is still a pain in the ass, even in 2024.

If letsencrypt would offer wildcard certificates with their url based authentification as they offer for non-wildcard certificates, it would be ok.

But having to tinker with the DNS infrastructure for each project which wants to use domain wide HTTPS is so much hassle.