onlyrealcuzzo
That's API-list prices. They have an 80% margin over COGS.
Cost per equivalent output is dropping 10x every 18 months -> so in 3-ish years, if the trend continues, that will be $3k per employee.
Not bad. A lot of companies are already spending about that much or more on IT per employee.
Especially since that $3k bakes in an 80% margin. It's about $600 per year if you DIY at scale - which is about $50 per month - but at the $3k price, hardly anyone is going to.
In the West old-age dependency ratio (retirees per working-age adult) is climbing roughly 0.5 to 0.7 percentage points per year.
We've got to get 0.7% more productive for employees to keep the same quality of life (unless retirees get screwed, and since they vote and make up a huge portion of the voting block, I wouldn't count on that happening).
Further, more and more of the population has to transition into into elder care.
Unless we hit 3%+ GDP growth, us workers are probably going to see declines in quality of life (and we're probably not going to get those levels of growth)...
The US may reach the 100% Boy Name Ronin-ification anywhere between 2057 or 10,327 AD.
There is an unbelievably enormous difference in 100% vs 47% -> and when you look at the 2nd derivative this is REALLY REALLY REALLY bad.
I mean, the growth is astounding and incredible. It does not bode particularly well for a ~$2T valuation.
That would make Netflix like 30-50% more expensive.
Is it even a clear problem to figure out which business pays what?
Second sentence is empirically a complete lie.
Search volume is still growing, despite analysts asking on every call what Google is going to do about falling volume, and Google continuing to re-iterate: Search volume is still growing, as are clicks on ads.
I get it that everyone hates paying as much for clicks as they do now. You can hate it all you want. You can claim Google is lying about search volume and ads, but that would be massive securities fraud...
Haters gonna hate. It doesn't mean the king is dead.
Cloud is on pace to be bigger than Search/Ads next year...
Do you really think Search/Ads is going to lose 100% of its revenue by next year to flip that difference?
Anthropic has been doing this with Mythos for quite some time...
And yet nobody has time to do anything except to tell everyone they don't have time to do anything.
It's nice that they have Terra which seems to fill a void that's been needed since Sol 6 focused on cost (at the expense of quality), Sol 6.1 got a huge boost in quality, but became unusably slow unless you paid Astra prices - at which point, why not just use Astra?
Now at least we have a viable other option again.
Something that I'm interested in: How fast is the compilation speed on large programs compared to Zig, C, Go?
My ideal language is safer than Rust (no deadlocks / livelocks, no stack overflow from recursion), is optimized for cache locality, but compiles faster than Zig.
This seems like it's close to 2/3.
How fast is the compilation speed on large programs compared to Zig, C, Go?
My ideal language is safer than Rust (no deadlocks / livelocks, no stack overflow from recursion) but compiles faster than Zig.
At least in the case of ChatGPT - it was (and mostly still is) objectively optimized for engagement. Since ChatGPT was leading the way, and much distilling has occurred, there are at least partial remnants of that problem everywhere.
The Chinese models may or may not really care about this at all, but they're doing a lot of distilling, so they're getting it whether they want it or not.
The American models for the most part care about engagement - some a lot more than others.
MiniMax -> Qwen -> DeepSeek (pro) -> Gemini (Carbon) -> Fable (to beat Carbon) -> Astra (to be slightly worse than Fable but cheaper).
I doubt we'll see any major US release besides Grok in the next 3 weeks.
Would be nice if we got a Terra that's competitive with Gemini Flash and DeepSeek Flash.
The fun part is, we're already at the point where we are seeing something frontier-ish almost every single week.
The really fun part will be when they all start adding System 1-3 natively (IMO) - which I think will be the next release cycle.
``` jank is C++ jank can include any C++ source, link to any C or C++ library, and it uses the C++ type system. jank even compiles to C++! ```
I'd recommend saying that it lowers to C++ earlier, as I imagine most people are interested in that aspect of how it works.
```jank is Clojure on top of C++``` -> `on top of` could mean many things. I'd recommend just saying it transpiles to C++. Then, the pros and cons that come from that flow naturally.
``` Use your favorite nREPL editor plugin. jank contains an LLVM-based JIT runtime to compile C++ code on the fly. ```
This is true for anything written in `jank`, right? But presumably not for your C++ dependencies? Like if you have `jank` code which depends on data managed in a different C++ library.
It would seem there are a lot of concurrency and parallelism implications to this. It would be nice if you spelled that out.
``` jank builds upon Clojure Keep your existing code; unlock the native world. ```
Are there any limits here? You might want to make that clear if not. Unless explicitly stated, my assumption is that it won't always work (and therefore is mostly irrelevant). Though, in this case, it might actually always work - so that would really be worth a few extra words!
It seems good enough for median earners. After taxes and health insurance, it's basically even.
Perhaps not self-sustainable you mean that unless something changes, it's not going to be able to keep paying out at current rates.
Well, I got news for you - that's what is happening for almost all government-run pension programs across the world on this model. Pay as you go does't work when you keep the same payment, and have 10x a higher ratio of recipients to payees.
This isn't unique to Social Security or the US. It's just a mathematical fact of the system.
You cannot have 99% of people contribute `x` and 1% of people receive `y`, and then switch that to 70% contribute and 30% receive, without either increasing `x` or reducing `y`.
You could have planned ahead for this long ago, and seen that the ratio was going to change and increased `x` over time accordingly or planned to reduce `y` over time accordingly. But we didn't, and mostly no one else has either.
My main critique - which I'm sure you're aware of - is that the hardest part of doing this is predicting what your workload is actually going to be like. That's what Go does so well. It can get almost anything right without you needing to hand-tune it.
While I have you - are y'all planning to implement FSMs and thunks (for recursion) at any time in the near future?
This is something Go is unlikely to ever do unless it becomes a Go2 language.
I don't know enough about your runtime to know if it's remotely feasible given the choices you've made.
Most companies don't offer pensions anymore. Some companies don't even offer 401ks at all, and a significant portion of the ones that do don't do any employer contribution matching.
I'm not up to date, but the scheduling engine was far behind Go in terms of parallelism. Crystal was always quite good at concurrency.
But Go is popular because it's so good at parallelism (and relatively safe with a garbage collector).
I know Crystal has been working on this for the last few releases, but I'd be surprised if it's matching Go on parallelism.
Go's runtime is quite the engineering feat.
It can often outperform hand-optimized Rust in worst-case parallel workloads (p99), despite Rust having a number of pretty huge advantages...
Toward the tail end of the pandemic, well after vaccines and the average person even remotely cared about it, I stayed in a small studio apartment.
The cleaning fee was $200.
The host gave me a list of at least 30 things I needed to do, including vacuum the floors & washing all the dishes and returning them to their exact initial positions - along with photos of where everything should go, exactly, along with a list of fines as high as $100 PER ITEM for each infraction the cleaning crew could find.
I have never stayed in an AirBNB since outside of hosting a large group, and I never will again.
They've banned this now.
What about all the hosts using AI to pretend guests trashed their place?
No thanks.
Hotels are just fine. I hope all these get-rich-quick scumbag AirBNB speculators get wiped out by high interest rates and lose every penny they have so that people who actually need housing can afford it, and people who actually know how to run a hospitality business can keep doing that correctly.
So, if like most people, your working to live instead living to work - your employer is doing a terrible job incentivizing you to do more than the bare minimum.
We all know you are far better off doing almost nothing and then all your time trying to get promoted for it, than trying to get promoted by actually doing a good job and thinking you'll get promoted based on merit.
You do have to be worried that it's possibly installing trojan horses on your computer while compiling code, or any other number of unwanted side effects.
But you can and should be able to have integration testing in place to know that a compiler - at a minimum - actually works.
That seems like a glass is half empty attitude.
For one, the problem is solved. You should be glad. That's what you wanted...
Typically every solved problem opens more doors than it shuts.
We're pretty far from knowing it all.
It's like someone saying the field of Math died when we got calculators and computers and spreadsheets to make it easier to do calculations.
Now you can use AI to help you.
Sure, if you refuse to use it, then you're screwed. That's a you choice. Not inevitable.
The only things in life that are certain is change and death.
Not any different than some Amish person being annoyed that s/he can't contribute to the field of Math because it's too hard to do all the calculations by hand on paper...
You can spend your whole life crying that one day we'll all die, or you can enjoy the time you have.