The point is all the other things: total number of lines of code, permissions and security, memory management, drivers, process mgmt, it all changes.
23,652 karma · joined December 5, 2014
Member of Technical Staff, AI @ Verda https://verda.com/
some src @ https://github.com/rdaum/
The point is all the other things: total number of lines of code, permissions and security, memory management, drivers, process mgmt, it all changes.
You could make the argument that Rust w/ its memory safety is a candidate, but w/ Rust it's still entirely possible and fairly easy to break out of that. And Rust/Cargo applications have a habit of using a bazillion third party deps that you then need to keep a close eye on.
I'd wager most of the services running on the interwebs are web servers, database servers, inference servers etc that don't change over their lifetime really. They're just doing the same thing all day long every day.
If you're doing stuff like what I'm doing for work right now, which is, yeah, multiplexing potentially oodles of user-submitted jobs, and those jobs are best expressed as distinct images or containers, then yes, managing start times is absolutely imperative in improving utilization/occupancy and therefore reducing costs.
But I'm not convinced that's a typical scenario, not typical enough to drive enough time and money investment in this space maybe?
Also there ain't currently no real "hypervisor" for the (NVIDIA) GPU. Not practically anyways. And that's arguably where we need it the most. Or at least I do, for Day Job(tm).
So unikernels and microvms may have to lean on other arguments for adoption: security and simplicity-to-reason-about might be those...
The point that makes this different from an OS is that there's no shared service, no syscalls to do that stuff -- just subroutine calls -- and no timesharing (except at the hypervisor level). It's just a single runtime running on hypervisor direct against the virtualized hardware.
Because, yeah, all this work has happened in hardware in the last 30 years to make that possible, but we still treat the operating system as the best unit of resource sharing. When in fact it's kind of a jack of all trades master of none. If you're booting a whole linux kernel -- with its giant framework built to co-tenant a pile of applications and users -- just to run one process, there's definitely something to look at there. Even if the unikernel space itself is relatively immature.
You don't need to emphasize the "vibe coded every time you need them" thing. That's not what anybody was being talked about in the article. The "vibe coding" piece is pointing out that the missing pieces in the ecosystem can be more rapidly filled in now because of agentic tooling.
But that does nothing to make up for the terrible investment community. Getting started here requires already being started.
When I briefly worked for a Toronto startup, it was like all of them went to the same private boy's schools together as kids. It was a status club.
I jumped ship to an American startup and made almost double the money dealt with 0% of the bullshit and they were bought by Google the next year.
And if you could put the words "Bay Area" or "Stanford" or "San Francisco" next to your name... different story.
The VCs are not buying the idea or the tech, they're investing in the people. And they invest in a formula that has already worked for them before to make big coin. Prop somebody up, let them hire like crazy, and then get them get acquired, and then cash out. They don't care if it fails if they can make it succeed 1/200 times.
Canadian investors want you to have already succeeded before they help you succeed a tiny bit more.
Many of us have spent our adult and teenage lives learning an arcane magic that we took pride and joy and status in. Only to find now it's not so magic anymore. Or not in the way we thought.
I often see parts of my own code as art. Especially when I was younger, I guess.
But I also saw lots of it as: making a living. And there's fluidity between the two.
They're right "programming isn't special" -- it's not the magic you thought it was. It never was. It just appeared magic because others couldn't do it.
You can still have that magic in pockets. But you shouldn't expect to be venerated for it. You never should have.
I've been doing it for 40+ years at this point. I'm happy to let the machines take over a lot of the grunt work so I can get one with making beautiful interesting systems. I can make all things I wanted to make now.
Art is special. Programming... no, get over yourself. You can see it that way. Not everyone else has to. And playing Butlerian Jihad isn't going to dam the flood.
> Deno people probably just want a paycheck after they spent years seeking glory and money on something that other people used but didn't pay them a cent for.
My take: Opensource-Infrastructure-as-startup-but-also-charity is a thing that is going to die along with ZIRP. I don't know why VCs ever sniffed around things like this in the first place. The younger generation that followed this business model with liberal "take my stuff" licenses and sneered at GPL etc are learning the hard way that making a nice cool thing and getting noticed is not going to earn you a good living. (And other people will make millions off your passionate work.)
On LambdaMOO (and LambdaCore) whisper was for in-room communication and "page" sent a message to someone privately anywhere on the MOO. In reality nobody used whisper. I never knew there was a form of page that didn't carry a message.
Things like your "mutter" were easy to code up in MOO, and I recall people doing things like this, but it being seriously seriously frowned upon.
BTW you might be interested in my project https://github.com/timbran-project/moor
People crying about being "censored" -- their comments are still visible if you really want to see them -- that's not censorship. Just not a mandatory granted audience -- for saying shitty things about someone that just passed away... garners little sympathy from me.
And then putting that aside, the linked twitter thread people keep regurgitating has been shown by other people to contain a number of outright falsehoods.
So do we really need to have this conversation here? And why? Is this the right forum and time for these people to have it out with their grievances? I really think not.
The thing I've taken away most from my multidecade career is that the hardest part is getting any group of people all marching in the same direction, of their own volition. Everyone's motivations always differ. And leadership that just tries to force one direction almost always fails to consider enough viewpoints. And the alternatives, a deliberate rhizomatic chaos, or cutthroat competition, can be entirely demoralizing.
Frankly, it's usually just gatekeeping (or just being threatened) hiding behind some moral system they just assume you should share with them.
They've also done so many pivots on AI, all of them weakly and annoyingly done. They couldn't even pull of FiTM copilot well, they were super late on it and it had all sort of bugs.
They could have just taken the loss and written an amazing GUI coding agent that integrated well with their IDE -- amazing integrations with their refactorings, etc. -- but that played well in other people's ecosystems but they refused and tried to own the whole pipe. Or something. They just confused me.
Their latest attempt is to allow you to connect to and run other people's agent harnesses inside the IDE and it works well enough but it wasn't enough to grab me since I (like you) use herdr on another machine to do the coding.
I've been using their products since ~IDEA 3.x. Almost my entire 25+ year career really. My fingers are wedded to their keystrokes.
Commenter is self-promoting their "graph DB" related product.
"Yeah, well, you know, that's just, like, your opinion, man"
In my own experiments I confirmed the same thing. Just using explicit free lists / allocator techniques was far more performant.
And actually-existing LeanStore on github doesn't use it, anyways. And strangely never has (looking through git history). Even though the paper (2018) describes it. Maybe Leis or Alhamsi can explain.
Curious if Umbra and the CedarDB stuff that came from it do use this approach, too. I seem to recall the Umbra talk speaks about using it.
As a lazy "eventually reclaim when I've got free cycles" technique maybe ok? But revealing that the actual LeanStore C++ code never does it.
But this is about humans malevolently using AI as a tool, not about AI autonomously doing "its own thing" (ahem David S Pumpkins) against "humanity."
It is instead already existing anti-social elements within human civilization harnessing machinery to accomplish their own selfish and destructive aims, regardless of the broader cost. Which is nothing new -- it's the story of all the horrors of the 20th century, as well.
Ask yourself who benefits from ideological attempts to hide the human driving the process from the agent doing its work for them.
If we imbue these machines with apparent autonomy, this is nothing more than an attempt to hide the man behind the curtain.
That's a perhaps overly optimistic view, but feels like one worth aiming for.
In reality we're so far from consciousness and independent goal-directedness in AI -- let alone any kind of energy and real computational efficiency... I agree with LeCun in broad strokes. I think he's overly dismissive of LLMs perhaps but I do think he's right that talk of "wiping out humanity" is theatre for people playing corporate power games.
There's likely all kinds of internal competition and disagreements and dysfunctions.
So there's that.
But in the last instance, revenues win. OpenAI and Anthropic have to fight for new revenue sources while Google already has a firehose. The motivations are fundamentally different.
Google gains very little by having us use their models for coding. It doesn't help them in their core mission ("to organize the world's information and make it universally accessible and useful ^W^W^W^W^W^W[and turn it into ad revenue]"), nor would it be anything close to substantial revenue compared to the ads revenue firehose they already have.
They will push AI in a direction that serves their existing goals and service the coding agent model only as is necessary.
Yes, he was talking about safety, but IMHO they're likely already IMHO pushing the boundaries of cartel type behaviour. And they will use safety as the cover to make it happen.
I suspect we'll see serious price fixing and the DOJ do nothing about it because of the inroads these people have with the Trump regime.
Whether that survives contact with Chinese open weight models is hard to say.
Huge misstep releasing it.
Will see if this remedies things.