yup, bezos said "we will be able to beat the cost of terrestrial data centers in space in the next couple of decades". presumably this means they'll need huge ass radiators, so its all about bringing down launch costs since they'll need to increase mass.
they should just acquire one of the many agent code harnesses. Something like opencode works just as well as claude-code and has only been around half of the time.
I used opencode happily for a while before switching to copilot cli. Been a minute , but I don't detect a major quality difference since they added Plan mode. Seems pretty solid, and first party if that matters to your org.
true on the naming, but i think geometric/clifford algebra has its own mysterious aura precisely because it can be framed as "suppressed" or "overlooked".. plus it genuinely does have elegant mathematical structure backing up the hype
funny thing is quaternions had that exact same energy in the computer graphics community for years. after ken shoemake introduced them to CG in 1985, there was a long period of "why are we using euler angles like cavemen when this exists??". now quaternions are well known tooling for people in graphics and the mystique has worn off at least in that community.
>EDIT: More interestingly, I find an issue, what do I even DO? If it's not related to integrations or your underlying data, the black box just gave nonsensical output. What would I do to resolve it?
Lots of stuff you could do. Adjust the system prompt, add guardrails/filters (catching mistakes and then asking the LLM loop again), improve the RAG (assuming they have one), fine tune (if necessary), etc.
Deep SSMs, including the entire S4 to Mamba saga, are a very interesting alternative to transformers. In some of my genomics use cases, Mamba has been easier to train and scale over large context windows, compared to transformers.
solid analysis but i think you're missing the logical endpoint here: this doesn't end with companies "relearning scarcity"... it ends with the permanent contractor-ification of various types of work at these tech companies (not just tech roles, but other types of roles at these companies). already, contractor-to-employee ratio has gotten higher and higher at these companies in recent years and I expect this to continue.
ZIRP (especially the "double tap" ZIRP in 2021/2022) created this monster (bootcamp devs getting hired, big tech devs making "day in the life of" tiktok vids).
contractors give:
instant scale up/down without layoff optics
no benefits overhead
no severance obligations
easy performance management (just don't renew)
this mirrors what other industries typically do after large restructuring waves ... manufacturing got temp agencies and staffing firms as permanent fixtures post-rust belt collapse. tech is just catching up to the same playbook.
A dataframe API allows you to write code in Python, with native syntax highlighting and your LSP can complete it, in one analysis file. Inlined SQL is not as nice, and has weird ergonomics.
UDFs in most dataframe libraries tend to feel better than writing udfs for a sql engine as well.
Polars specifically has lazy mode which enables a query optimizer, so you get predicate push down and all the goodies if SQL, with extra control/primitives (sane pivoting, group_by_dynamic, etc)
I do use ibis on top of duckdb sometimes, but the UDF situation persists and the way they organize their docs is very difficult to use.
because method chaining in Polars is much more composable and ergonomic than SQL once the pipeline gets complex which makes it superior in an exploratory "data wrangling" environment.
i'd say the crypto angle is only one factor. as is usual in the real world, effects are multifactorial.
clawdbot also rode the wave of claude-code being popular (perhaps due to underlying models getting better making agents more useful). a lot of "personal agents" were made in 2024 and early 2025 which seem to be before the underlying models/ecosystems were as mature.
no doubt we're still very early in this wave. i'm sure google and apple will release their offerings. they are the 800lb gorillas in all this.
it's amazing how far we've come in 20 years. i was a (very minor) contributor to khtml/konqueror (before apple got involved w/ webkit) in the early 2000s, and back then it was such a labor intensive process to even create a halfway working engine. like, months of work just to get basic rendering somewhat correct on a very small portion of the web (which was obv much smaller)
in addition to agentic coding, i think for this specific task having css-spec/html-spec/web-platform-tests as machine readable test suites helps a LOT. the agent can actually validate against real specs.
back in the day, despite having gecko as an open source reference, in practice the "standards" were whatever IE was doing. so you'd spend weeks implementing something only to discover every site was coded for IE's quirks lmao. for all of their other faults, google/apple and other contributors helped bring in discipline to that.
> i think for this specific task having css-spec/html-spec/web-platform-tests as machine readable test suites helps a LOT
You know, I placed the specs in the repository with that goal (even sneaked in a repo that needs compiling before being usable), but as far as I can see, the agent never actually peeked into that directory nor read anything from them in the end.
It'll be easier to see once I made all the agent sessions public, and I might be wrong (I didn't observe the agent at all times), but seems the agent never used though.
oh interesting, so it just... didn't use them? lol. i guess the model's training data already has enough web knowledge baked in that it could wing it. curious if explicitly prompting it to reference the specs would change the output quality or time to solution.
very excited to see the agentic sessions when you release them.. that kind of transparency is super valuable for the community. i can see "build a browser from scratch" becoming a popular challenge as people explore the limits of agentic coding and try to figure out best practices for workflows/prompting. like the new "build a ray tracer" or say nanogtp but for agents.
reply