Hacker Newsnew | past | comments | ask | show | jobs | submit | vdupras's commentslogin

That's some nice guillotine energy going on here on this unflagged topic. You surprise me, HN.

Silver lining: can you imagine how dirt cheap RAM will be after that bubble has popped? Oh my...

RAM producers aren't adding more capacity on the non-HBM side of things, so we shouldn't see a dramatic drop in pricing if AI HBM memory demand drops.

If we end up with metric tons of unused HBM memory lying around, I'm sure that someone will design a general purpose computer using them, or design a HBM-to-DDR interface.

It won't. Demand is being pushed forward. That means that longer this situation take longer it will take for prices to recover to same levels.

If you delay your iPhone upgrade because of RAM prices, you're not going to buy two at once because you were delayed. So push, forward, push forward, sure, but to a point.

No manufacturer is increasing supply though. RAM, SSD, HDD - they just reallocated their existing supply to AI.

Your home systems can slot in HBM? Doubt that.

This is a simplistic view of why the prices are the way they are.

This comment raises an interesting question: Would Serenity OS have brought Andreas the same kind of serenity had it been developed with AI? Open candid question.

I like the idea that people are either coders or builders. So AI can help fulfill your desire to build, create, bring things into reality. But it can't satisfy you if you like programming for its own sake. SerenityOS was not a practical project, it was clearly done for the enjoyment of programming itself.

The project's use of AI now echoes that - it's not being used to create new features, it's used for practical, boring drudge work of translating between two languages. So still very much on brand.


I don't think so because if I remember it correctly, Andreas suffered from alcoholism and serenity prayer helped him to go on the right path and iirc he honored that and created an os named serenityos.

God grant me the serenity

to accept the things I cannot change;

courage to change the things I can;

and wisdom to know the difference.

(courage to change the things I can;):- I think that this line must've given Andreas the strength, the passion to make the project reality.

but if AI made the change. Would the line be changed to courage to prompt an all powerful entity to change the things I asked it to.

Would that give courage? Would that inspire confidence in oneself?

I have personally made many projects with LLM's (honestly I must admit that I am a teenager and so I have been sort of using it from the start)

and personally, I feel like there are some points of curiosity that I can be prideful of in my projects but there is still a sense of emptiness and I think I am not the only one who observes it as such.

I think in the world of AI hype, it takes true courage & passion to write by hand.

Obviously one tries to argue that AI is the next bytecode but that is false because of the non deterministic nature of AI but even that being said, I think I personally feel as if the people who write assembly are definitely likely to be more passionate of their craft than Nodejs (and I would consider myself a nodejs guy and there's still passion but still)

Coding was definitely a form of art/expression/sense-of-meaning for Mr Andreas during a time of struggle. To automate that might strip him of the joy derived from stroking brush on an empty canvas.

Honestly, I really don't know about AI the more I think about it so I will not pretend that I know a thing/two about AI. This message is just my opinion in the moment. Opinions change with time but my opinion right now is that coding by hand definitely is more meaningful than not if the purpose of the project is to derive meaning.


Your reasoning is sound, but is already covered by Collapse OS' manifesto. It refers to two stages of collapse, Collapse OS being for the second.

As long as we have working modern machines, self-contained modern open source OSes, NetBSD being one, are good choices.

One problem there is with such system is their overall complexity. Sure, you can use them, and they're pretty flexible for the user. However, when necessity forces you to crack the kernel open, the learning curve is pretty big.

For example, let's imagine a computer with a broken SATA controller. How would NetBSD behave on it? Hard to say, NetBSD developers don't develop with that target machine in mind. Usually, when you have such a machine, you replace it or repair it. But what if you can't? Maybe you'll have to play in the kernel to manage to do something with that machine, route around it. Maybe it will work, but maybe you'll be stuck, and maybe that in that particular situation, it's going to have tragic consequences.

And that's kind of what Dusk OS (http://duskos.org/) is about.


Exactly, DuskOS is for maintaining a somewhat degraded level of civilization and perhaps rebuilding, while salvaged machines are still common. CollapseOS is there if things get even worse, to retain a minimal level of computing capability during the transition to whatever comes next. It’s hard to imagine the need for CollapseOS while things are still working, but in some horrible future where it’s the only system keeping the water system running, people will appreciate it.

The additional value in Collapse OS is that — as the hardware capable of running even Dusk OS (let alone a more complicated 32+-bit operating system) continues to break down and dwindle in supply — you still have an option such that you can reasonably-comfortably use those more constrained systems for simple tasks and free up the complicated hardware for complicated tasks. You don't need a multicore 64-bit CPU to keep a typical water system running; an 8-bit microcontroller is typically enough, and having a software stack already ready to go (including an ease of adapting to whatever specific hardware might be wired to that microcontroller's pins) is a pretty big deal even long before the point where we're shooting each other over the last Z80s and PICs.

  > sloptimists
That's a good one! Did you just come up with it? I've never seen it before.

it was in this link included in this same story https://johan.hal.se/wrote/2026/02/03/the-sideprocalypse/

18 relevant results in 0.96s, from Kagi.

We truly are in the age of incompetence. Isn't Apple supposed to have budgets big enough to hire the brightest minds of the world? And this is all they can come up with? Then the emperor has no clothes and they're a bunch of overpaid bozos.

  > Being able to code doesn't make you better than the "plebs" who are creating massive value with a vibe coded tool.
  > [...] I noticed AI could really code better than me [...]
AI code output is generally considered mediocre (in the sense of "on the median"). If it codes better than you, it might be that your code output is generally below average.

Might it be the case that you don't grasp how good one can get with computers and thus not realize that one could be much better than you are at programming them? Did you consider for a moment the possibility that you were missing something?


Notice how I said "coding", not "programming". Coding to me is "should I do an early return or use an if/else? Should I extract that variable into a function to make it cleaner?". It's about focusing on the trivialities that come with insisting on meticulously hand typing and reviewing every line instead of focusing on software quality, design and user needs.

If we want to make that distinction, then we should also acknowledge that "vibecoding" is a misnomer and should be called "vibeprogramming", because it delegates the whole act of programming to the LLM, leaving you with fleshing out the specs (which is not programming).

If that is so, then your whole comment is inconsistent and akin to "I do all my poetry with LLMs now and I don't see what people have against it: it's often better than me at punctuation!"


Soooo many times in my career I've had to come back and "extract that variable into a function" that I just do it right away by force of habit.

Point is, this isn't trivial, it is the kind of thing that ends up saving work over the long haul.

Or include this in my agent 'rules' files.

GOOD EXAMPLE

query=f""" SELECT foo FROM {sometable} WHERE {condition} """ answer=spark.sql(query).toPandas()

BAD EXAMPLE

answer=spark.sql(f""" SELECT foo FROM {sometable} WHERE {condition} """).toPandas()


> software quality

If you think software quality isn't tied to readable (clean) code...


And yet, the only reasonable action to take is to flag this topic and move along with the "humanity has always found a way out, technology will save us. Remember, we were supposed to drown in horse manure!"

Why? Because candidly looking at those risks as a society means deep collective existential dread, which automatically means an immediate civilizational collapse.

So I'm guessing some of our elite is actually ignorant and the other part is willfully shutting the hell up on this subject to let our civilization run on fumes a few more years.

It's unfortunate because a rapid civilizational collapse could give humanity as a species a better chance of survival.


> It's unfortunate because a rapid civilizational collapse could give humanity as a species a better chance of survival.

How's that?


An effective way to cut carbon emissions before feedback loops are triggered


Oh my, this is a slap in the face for me too. For me, GTA is the first one. The other ones (III and following) are GTA with 3D and a story line slapped on top. I must have a dislike for 3D because I've tried again the original GTA a few years ago and liked it a lot more than GTA III+. It's just fun without complication.


20k years ago, humans hadn't invented agriculture. Our whole civilization has existed in one particular geological time, an exceptional one. There is absolutely no indication that it's flexible enough to be transposed in another, and particularly not at that speed of transition, which is, in geological time, exceptionally fast.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: