vhawk19.eth is trying to be active on x

Loose thoughts on the future of abstractions: At first glance, it seems evident that shared abstractions (stdlibs, frameworks, libraries) will still be beneficial in a world of agents. Centralized and shared knowledge, lower costs (no tokens needed) are just two reasons for why this is good. But, looking back at the last ten years, it's clear that a lot of frameworks and libraries were made due to (to simplify) personal preference: framework X is Y but in language Foo which has same runtime characteristics as Bar but I like it better, or framework X was born out of frustration with syntax of Y, or framework X uses TOML instead of YAML and is container-native or ... <insert favorite thing here>. Meaning: a lot of abstractions in the last twenty years were made for reasons that no longer seem valid. That makes me think that there will be less need for more abstractions (as we've known them!) in the future. But if you look around, you'll see that there's a thousand new things being created every day. I think that's a temporary phase. There are other, deeper (for lack of a better term) abstractions though that still seem valid: abstractions that introduce a different way to compute. Think: type systems, Lisps, CUDA, unikernels, IaC, k8s. (That's not a final and super confident list, more a general pointing in a direction. I'm unsure here.) I do think that in the future people will still create new abstractions of this latter type. Sharing those is still valuable, because they go along with a platform or a product. But the former type -- different languages that just switch syntax, frameworks that fix one grievance, util-like stdlibs -- for that I can see a future in which we're just endlessly remixing and "vendoring" existing abstractions. And just to say this out loud: I do think a lot of code-level abstractions (MVC, composition over inheritance, avoid-god-objects, classes vs. modules) don't matter in the future, because they're born out of the ability of humans to understand and maintain code. Even if new abstractions in this realm might make sense in the future, I think the barrier for them to spread is now incredibly high. Example: friend reported that in his company they're trying to introduce a new pattern because "adding a new country to our system requires changing all of these places in this 1500-line long class" -- who gives a shit about that anymore? Oh and another thing: I think the "is it in the training data?" concern is way overblown by now. Intelligence generalizes to a certain degree and the latest models have 0 problems writing in a language or framework that you just made up. Try it.

Most important stuff inference vendors offer: 1. Access to GPUs (hard to get!) 2. Infra abstraction so it's easier to operate 3. Privacy of data and security Usually, a breach would be very bad. BUT GPUs are so scarce today that customers don't have all that many options...

We solved the handle squatting issue once and for all. Use your organization's domain as a handle!

we are entering a renaissance in programming language and runtime research, and a golden age of software testing and verification it’s time to rewrite all software

@archgen_ is building skyscrapers for semiconductor chips Shrinking transistors is getting harder. Stacking them makes heat harder to manage. We’re building the tools to design chips in three dimensions. We stack transistors vertically, shorten connections, and optimize timing and heat together. Our foundational model for thermal simulation, predicts temperature roughly 5,000× faster than conventional EDA tools. Our placement engine ranked #1 in HRT’s macro-placement challenge We’re working with some of the largest fabs in the world to tape out our first chip in April 2027 archgenlabs.com

we spent less than $25k on all of noice marketing through its life millions of startup/protocols have 100x-1000x more resources but don’t try hard enough happy to help