* oh sorry we lied, we are going to make a profit-capped company.
* Ummm, we gonna up our cap.
* f it! we're gonna be for profit company, after MSFT gets their cut, rest in line.
* sorry MSFT, we need more Saudi money so you may not get the best prefernce.
* principles? yeah we have some marketing principles! Stock gotta go brrrrr tho! You cannot talk about it. Something something tell people what they want to hear.
If someone is building a new cloud, worth learning a few lessons from Cloudflare.
Perhaps the VM idea is old. The unit is a worker encapsulated in some deployable container.
In the world of Cloudflare workers - especially durable objects that are guaranteed to have one of them running in the world with a tightly bound database.
The way I think of apps has changed.
My take is devs want a way to say “run this code, persist this info, microsecond latency, never go down, scale within this $ budget”
It’s crazy how good a deal $5/mo cloudflare standard plan is.
Obviously many startups raise millions and they gotta spend millions.
However the new age of scale to zero, wake up in millisecond, process the request and go back to sleep is a new paradigm.
Vs old school of over provision for max capacity you will ever need.
Google has a similar, scale to zero container story but their cold startup time is in seconds. Too slow.
>By far the most important aspect is that we need to keep the new codebase as compatible as possible, both in terms of semantics and in terms of code structure. We expect to maintain both codebases for quite some time going forward. Languages that allow for a structurally similar codebase offer a significant boon for anyone making code changes because we can easily port changes between the two codebases. In contrast, languages that require fundamental rethinking of memory management, mutation, data structuring, polymorphism, laziness, etc., might be a better fit for a ground-up rewrite, but we're undertaking this more as a port that maintains the existing behavior and critical optimizations we've built into the language. Idiomatic Go strongly resembles the existing coding patterns of the TypeScript codebase, which makes this porting effort much more tractable.
TLDR: Typescript -> Go is much easier than Typescript -> Rust/Zig/$OTHERNATIVELANG
I could understand the portal before. Now it’s a gazillion things bolted on.
Enshittification is well in force.
I’d trust the huperscalers a lot more with their workers/lambda like infra to run routine jobs calling LLM APIs or deterministic code instead of Anthropic.
Anthropic is a phenomenal paid model but they have a poor reliability record.
I don’t care much if Claude code hiccups when generating code. But after the code is generated I want it to run with multiple 9s under certain latencies every single time.
That’s the messiness. 77 million voted for a slightly worse life. Higher food and gas prices. Less jobs. Higher rents.
All in the name of “immigrants are root cause problems”
The average person really has one choice “red” or “blue” and there isn’t much reason other than my group votes a certain way so I vote that way.
Trump came to power because he tapped into people’s anger.
I don’t see a world where this gets better. Social media and news propagates fear and hatred like wildfire. Algos massively boost up anything that improves engagement. Engagement improves adclicks.
So we may actually end up destroying the empire for a bunch of adclicks.
* oh sorry we lied, we are going to make a profit-capped company.
* Ummm, we gonna up our cap.
* f it! we're gonna be for profit company, after MSFT gets their cut, rest in line.
* sorry MSFT, we need more Saudi money so you may not get the best prefernce.
* principles? yeah we have some marketing principles! Stock gotta go brrrrr tho! You cannot talk about it. Something something tell people what they want to hear.
reply