JonathanBeuys
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.
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.
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.
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.
https://x.com/JonathanBeuys/status/1984882268817519036
That is revenue from real world usage of their datacenters. Usage their customers would not pay for if it did not have a positive ROI.
A pretty stable growth of 30% per year for the last 5 years. At a current level of about $50B per year.
What is the value of it, if it continues like this for another decade? Revenue would be at roughly $1T/year then.
In the face of this real usage and the growth of it, spending tens of billions of dollars on building out infrastructure looks ok to me.
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.
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?
I don't like having a different webserver in development and production.
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.
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.
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.
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.
You would also have to get hold of my machine and get past it's security mechanisms.
You can put as many layers on top of what you call "obscurity". But at the bottom it's still just a simple string that holds the power to authenticate you.
And "multi-factor authentication" does not help with the situation "User is allowed to use this script, so they are also allowed to use that website. Let's open it for them.".
Regarding storing them in plain text: That's not much different from ssh keys. When someone can read your ssh key, they can log in as you.
If you know a better way to automatically log a user into a website, let us know!
In the end, every security mechanism is "plain text". Even ssh keys. When someone gains access to your ssh key, which is just an ascii string, they can log in as you.
https://name:[email protected]
1: When you bookmark them, it shows the auth part when you hover the bookmark with the mouse.
2: When you open them from the command line
firefox https://name:[email protected]
And then ctrl+click links on the site, it opens the new tab and shows the auth part in the tab title as long as the link loads. It seems the "current url" in Firefox code is stored with the auth part, and it passes that part on to local links.These issues make it insecure to use auth urls because as soon as someone looks over your shoulder (or there is a camera like in many cafes), you are p0wned.
I wish we had a better way to log into a website from the command line, like ssh keys. But for now, we are stuck with what we have. And Firefox makes it insecure to use it. So for now, I continue to use Chromium.
sudo -u desktopuser XDG_RUNTIME_DIR=/run/user/1000 firefox
Sorry for messing it up the first time I tried!Man, you solved it!!
Thanks a 1000 times!
The task at hand is to open it in firefox with the desktop user.
I use a script in a root terminal to control a lot of my workflow. One thing is that I start browser windows from it when needed. I start them with
sudo -u desktopuser chromium example.com
Because sudo -u desktopuser firefox example.com
does not work.I thought that is relevant to the question "Why bother with Chrome".
desktopuser of course is the normal user which would also start Firefox if I did it via the Desktop gui.
I just want to launch a new browser window.
This does not work:
sudo -u normaluser firefox example.com
So I do: sudo -u normaluser chromium example.com
I thought that was relevant to the question "Why bother with Chrome".It seems to be some magic Firefox puts somewhere (In the environment?) that prevents it to launch a new window from a fresh terminal that is not inherited from the same parent that launched the first window.
You cannot start FF from the Desktop and then start new windows from a shell.
Unless that shell was directly started from the desktop.
So it must have something to do with the environment or process tree.